I legitimately have no idea what infrastructure provisioning tool to use anymore. I normally defaulted to Saltstack Masterless and Chef via Packer. What "simple" tool is left anymore for me to create my immutable AMIs that aren't bound by some license?
CINC Is Not Chef
51–57 of 57 posts
Re: CINC Is Not Chef
#52Re: CINC Is Not Chef
#53I haven't encountered any Chef code in almost ten years. For the stragglers not yet primarily on Kubernetes and Terraform, I see Ansible and some extra Terraform. Maybe I see some Salt here and there. These are just my anecdotes, for sure, but (also anecdotal) I rarely hear of other "ops" type people using Chef, and most of the ones I know never got more than just their feet wet with Chef (the SaltStack beta was out…
It's not great, but it works I guess. I do wish we were on SaltStack or Ansible instead.
Re: CINC Is Not Chef
#54What is Chef? This website fails to answer that.
To quote the first line of the website: > A Free-as-in-Beer distribution of the open source software of Chef Software Inc. See goals for details, or follow our blog for updates on the project.
(Only then did I originally post my question to Hackernews. I can read. The info just is not there.)
Re: CINC Is Not Chef
#55I'm dumb and can't figure out wtf this is.
Chef is an infrastructure as code configuration system. The binaries are now proprietary. This is a FOSS replacement.
It's basically the same model as Red Hat. Except Chef never had the market penetration and brand recognition as a trusted source that Red Hat has.
Signed, someone who worked for Chef for almost 13 years.
Re: CINC Is Not Chef
#56I haven't encountered any Chef code in almost ten years. For the stragglers not yet primarily on Kubernetes and Terraform, I see Ansible and some extra Terraform. Maybe I see some Salt here and there. These are just my anecdotes, for sure, but (also anecdotal) I rarely hear of other "ops" type people using Chef, and most of the ones I know never got more than just their feet wet with Chef (the SaltStack beta was out…
I committed some Chef code into production today, at a FAANG no less. It's not great, but it works I guess. I do wish we were on SaltStack or Ansible instead.
Re: CINC Is Not Chef
#57I legitimately have no idea what infrastructure provisioning tool to use anymore. I normally defaulted to Saltstack Masterless and Chef via Packer. What "simple" tool is left anymore for me to create my immutable AMIs that aren't bound by some license?
For creating AMIs? Probably Ansible or something similar. Chef is great for ongoing management of servers, but not so good for a one-shot config run like you would do if you're creating AMIs.