I finally got a chance to look at Chef and I must agree with Michael.
If I wanted to go this way, I would push forth with Cfengine. The big
advantage with Chef over Cfengine is that I can hack it in Ruby
instead of C.
The DSL in Puppet still holds trumps for me in terms of usability and
the comm
Oh, I quite agree with you. It's why I stopped investigating Chef.
Just to be clear, the order of operation thing isn't like cfengine's
multiple passes; it is more like recipes are executed in the order
defined, and if you need to "depend" on something, you include the
other recipe.
On Thu, Mar
I'm with Luke on the whole Order-of-operations thing he had posted on
his blog at some point (I think in the history of puppet). I just think
it's a better design, and one of the main reasons why I didn't choose
cfengine to whip my inherited infrastructure into line. May have been
easier to st
> I have the same confusion, but the initial publication of Chef was
> made with many claims that it was just easier for them to start again
> than to try to understand Puppet's code base or to try to participate
> as developers. Of course, this is a development truism: It's *always*
> ea
