>>>>> "Neil" == Neil Neely <[email protected]> writes:

Neil> A. Rich wrote:
>> I'm thinking that we're going to move from cfengine 2 to puppet.  This is
>> going to be a big architectural shift as well as a programming language 
>> shift.
>> There seem to be a lot of ruby books out there and one puppet book.  If I had
>> to pick, say, three books to delve into ruby and its uses for puppet, which
>> ones should I pick?
>> 
Neil> I've been using puppet for 8 months and have yet to learn
Neil> Ruby[1].  There are some aspects I haven't gotten around to yet,
Neil> so perhaps mileage varies.

Neil> I setup our environment using various online resources .  A
Neil> coworker picked up "Pulling Strings with Puppet" and it helped
Neil> him fill in gaps I hadn't gotten around to training him on yet.
Neil> So it may be useful, even if dated.

One of the issues that pulls me towards cfengine2 is that it has
minimal requirements to install and run.  If I go with Puppet, I now
need to go and compile and install ruby (admittedly into an NFS
mounted /usr/local) on Solaris 8, 9, 10, RH7.3 (don't ask), RHEL3,4
and possibly RHEL5.  And I've got to keep them all at roughly the same
level.

With cfengine, it's just libdb of some mumble mumble version.  Much
easier to work with.

Not that I'm completely happy with cfengine either, I'm starting to
think that the language and it's mindset aren't something I want to
get into if I can help it.  

But I'm still tip-toeing into all this CfgMgt aspect, since I need to
convince (by example hopefully!) my co-workers that this will be a
good thing to do.  It's not really that hard, but I want a system
which my less techically inclined SysAdmins can handle and wrap their
heads around.

Suggestions appreciated.  And pointers to where I'm completely out to
lunch also appreciated.

John

_______________________________________________
Tech mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to