We've deployed cfengine in our 4000+ node environment solely for the reason that cfengine will work with both Linux and Solaris. One of our requirements was having only one configuration management tool to manage all machine types. (Wanting to actually cut down on time spent managing nodes!)
There was a bit of work to be done in the beginning defining the server class types and what we actually wanted to manage between each type. Once that was defined, classes created and tested, it's been smooth sailing bootstrapping all new nodes and cleaning up previously deployed ones. It's not agent-less, but we don't find that to be too much of a burden. We're slowly working towards the goal of throwing one plain OS image (either linux or solaris) out on the network, and then having cfengine perform all the package work, config, etc. to bring that image into compliance. This will eventually replace nearly all of our kickstart/jumpstart infrastructure. CFengine has saved us a lot of headache so far. I'd recommend it for heterogeneous environments. On Tue, Nov 13, 2012 at 2:53 PM, Hendrik Schaink <[email protected]>wrote: > I have done a little experimenting with Puppet Enterprise v2, however, > I find their (various) ways of setting up manifests plenty confusing. > Even after buying e-books ProPuppet and GettingStarted did I find myself > challenged by manifests. There appears not just one or two ways but many > different ways of creating and maintaining the manifests. OTOH I would > definitely be interested in learning more ... > > HTH, Hendrik > > > On 13/11/12 02:32 PM, Gustin Johnson wrote: > > Does anyone have any experiences with puppet, cfengine, chef, and/or > > bcfg2? Any recommendations in this space? If so why? > > >
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
