A Visual Introduction to Chef
mynameiskate.com
A Visual Introduction to Chef
1–10 of 21 posts
Re: A Visual Introduction to Chef
#2What's the current sentiment on Chef vs. Puppet these days?
Re: A Visual Introduction to Chef
#3I would like to read this, but unfortunately there's a database involved in serving the pages. Remember, kids: text and images were served happily on the 'net long before MySQL existed.
Re: A Visual Introduction to Chef
#4What's the current sentiment on Chef vs. Puppet these days?
They're both straightjackets. Chef is easier to cut your way out of and then use as a normal jacket
Re: A Visual Introduction to Chef
#5I would like to read this, but unfortunately there's a database involved in serving the pages. Remember, kids: text and images were served happily on the 'net long before MySQL existed.
You can just take a look at the diagram, which is hosted at Gliffy: http://www.gliffy.com/publish/2886461/
Re: A Visual Introduction to Chef
#6What's the current sentiment on Chef vs. Puppet these days?
They're both straightjackets. Chef is easier to cut your way out of and then use as a normal jacket
Obvious troll is obvious.
As I've said in the past, the consensus is simply "use a CM system," especially if you have to maintain these machines for a while (or if you have 50+ machines to take care of.) It's much better than dealing with various shell scripts or whatever else.
Re: A Visual Introduction to Chef
#7What's the current sentiment on Chef vs. Puppet these days?
Chef is a nice idea written by people who don't understand Unix. (evidence? check out popen in their source, try to figure out why subprocesses occasionally get SIGPIPE, and then grep to see where it's used and count the file handle leaks. I've had to reimplement that six or seven times and theirs was the one with the most subtle errors. Yes, I'll submit a patch when I have time, which at the current rate the day job is pushing me will happen shortly before hell freezes over) I like the design but the implementation scares me.
Puppet is the more mature technology of the two, but (so I'm told) there's an important limitation in that there is no way to automatically e.g. reload the web server if its config file changes. Both these systems have some issues with information flowing in only one direction.
Re: A Visual Introduction to Chef
#8What's the current sentiment on Chef vs. Puppet these days?
Chef seems to be gaining much more traction, at least from my memory of blog posts, tweets, conference talks, and comments in the past 6-8 months. Completely unscientific, but take from it what you will.
Re: A Visual Introduction to Chef
#9Superb! I've recently started with Chef and the learning curve is very high, especially if you're like me and haven't touched Ruby before.
Re: A Visual Introduction to Chef
#10What's the current sentiment on Chef vs. Puppet these days?
Puppet has invented a new language with its own syntax.
Chef has invented a new object system and execution model within Ruby.
Neither's approach is particularly good in this respect, but the latter is less onerous.