Doug Stewart on 27 Sep 2010 09:39:28 -0700 |
On Sat, Sep 25, 2010 at 4:29 PM, JP Vossen <jp@jpsdomain.org> wrote: > One minor turn-off for me was that Chef is all Ruby, where I'd prefer Perl. > :-) An odd critique, given that description, since Ruby is the lingua franca for Puppet as well. Unless you're referring to the actual manifests, which use a Ruby-like grammar of Puppet Labs' own design. That said, I've used Puppet a great deal. I liked my interactions with it (for the most part), though certain resource types that ought to exist (like firewall rules, for instance) are missing. When we were doing our tool selection, Chef had not yet hit the streets, so we were limited to cfengine and Puppet, and since cfengine had recently gone to version 3, we decided on Puppet as the easier, lower-resistance choice. In my previous environment, Puppet + Kickstart took our average RHEL installation procedure from a half hour, multi-touch affair to a basic one-touch, 5 minute affair. It's a glorious thing (when it works properly...). For those interested in Puppet, the new-ish Puppet Scaffold tool (http://github.com/jamtur01/puppet-scaffold) is well worth looking at, as it's an excellent way to get a skeleton of a configuration set up. -- -Doug @zamoose http://literalbarrage.org/blog/ ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|