I swear by Puppet. It's the right tool for the task, designed from the ground up to do what it does best. That plus it is super-flexible, readable, extensible, and has a dope community.
That's my un-professional, not-so-well written $.02. On Tue, Jan 27, 2009 at 11:10 AM, Larry Ludwig <larry...@gmail.com> wrote: > > > > On Jan 27, 9:47 am, Evan Hisey <ehi...@gmail.com> wrote: > > On Tue, Jan 27, 2009 at 8:04 AM, Jonathan Share <jon.sh...@gmail.com> > wrote: > > > > > 2009/1/27 tomcat <akocu...@mun.ca>: > > > > >> Hi, Gang.. > > > > >> The Subject: line says it all. My organisation is looking at > > >> selecting a configuration management > > >> system. Any comments about why you chose Puppet over other options > > >> would be very helpful to us. > > > > Well, there are basicly 4 options really in this area. > > > > 1) roll-your-own > > 2) cfengine > > 3) puppet > > and now 4) Chef > > Don't forget Capistrano which some use for administration (I think > it's better suited for app deployment) > > The reasons why we chose Puppet > - Language is easy to understand, read and learn > - Self healing in the sense if something is borked it will try to make > it the state you specify > - Template options are pretty flexible. > - Language is abstract for the resources you choose (makes it easier > to implement multiple OSes) > > Hope this helps. > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
