[chef] Re: Re: Puppet vs Chef

[Joel Merrick < >]

On Wed, Jan 13, 2010 at 5:18 PM, Adam Jacob < "> > wrote:

On Wed, Jan 13, 2010 at 6:32 AM, John Arundel
< "> > wrote:
> It may be taking my life in my hands, especially as I'm known to
> favour Puppet, but I thought I'd share this blog post with you:
>
> http://bitfieldconsulting.com/puppet-vs-chef
>
> The subtitle is '10 reasons why Puppet wins', but I should really add
> '...for now'. The 10 areas that I've mentioned are things which I
> really think Chef could make progress in, and make it a more
> compelling choice for devs and sysadmins looking at introducing
> configuration management. I'm a pragmatist, not a dogmatist, and while
> I think Puppet is still on top, I'm happy to see alternatives
> springing up and innovation happening. Monopolies are generally bad,
> at least for their customers.
>
> I'd be very interested to get your comments, especially if you are an
> enthusiastic Chef fan and want to say why.

John, thanks for being such a stalwart member of the bourgeoning
configuration management community we all share.  I hope you stick
around and meet some of the folks who work with, and use, Chef every
day.

I posted some comments on your blog, which I hope you'll find useful.

If there is anything I, or the chef community, can do to help you
understand how Chef works, let me know.

Nice post, good points made there Adam.

I'm a relative Chef newbie, but I came across Puppet and Chef at the same time.

I have got to honestly say that the internal DSL of Puppet turned me off (just in the same way cfengine did) and that's one of the main reasons we decided to stick with Chef.

I can't say anything about scaling or developer base etc.. but I will say that the community has been first rate when it's come to resolving issues I've had. One of the best open-source communities I've come across actually.

Docs are nice though ;)

Joel

-- 
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'