Aleksey> Paul Heinlein:  I'm delighted my intro to CFEngine 3 talk was
Aleksey> so useful to you.  Thanks!  :) As John Stoffel mentioned,
Aleksey> CFEngine has a very wide range of supported operating
Aleksey> systems, since it's just a small C binary with a few of
Aleksey> libraries.  That also makes it well suited for small
Aleksey> (Internet of Things) devices, which we are going to see much
Aleksey> more of soon.  And they will need to be managed and updated. 

Aleksey> <blatant plug>

Aleksey> John, with regard to CFEngine's learning curve -- we have a
Aleksey> training February in SoCal (http://
Aleksey> cfengine.eventbrite.com). We could also give your team a
Aleksey> private class at your site.  LOPSA discounts available.

Aleksey> </blatant plug>

This has been my single biggest reason for wanting to go with cfengine
(2 or 3, probably 3 now) at my site, because of the need (perceived or
otherwise) to support older legacy systems.  But maybe that's not the
route I should take these days.

In my case, I'm just looking to make things simpler to deploy and
manage, esp the core setup that in the past I've just written scripts
and used SSH/RSH to push out the changes to subsets of hosts.  This
has worked, but hasn't scaled and hasn't been great to passing onto
the other members of the team so that we have a unified and consistent
setup.

I need to just get off my butt and implement something and start
doing /etc/resolv.conf, /etc/ntpd.conf, etc in a quick manner to get
things moving.  But at the same time, I want to make it easy for my
other team members to use and more importantly, contribute to the
success of this.  And that selling point is really hard to get over,
esp when they're not interested.  

Looking over the Blueprint and other tools mentioned here has been
interesting.  And the discussion of where the tipping point makes
sense has also been good.  I probably just need to find the motivation
to do this for my home systems first, and then be able to roll it out
with version control as well for the $WORK setup.

John
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to