By Nick Anderson -
> Date: Thu, 4 Apr 2013 21:09:56 -0700
> From: Aleksey Tsalolikhin > To: "studiosysadmins-discuss@studiosysadmins.com"
>> Subject: Re: [SSA-Discuss] Puppet, cfengine or something else?
>> Hi, Steve. What is important to you about your configuration management
> tool? What do you need and want?
Aleksey asked me what was important about my configuration management tool a few
years ago. At the time I was using puppet. There were things I liked about
puppet (large active community, easy to do easy things like installing a
package or making sure a service was running, declarative syntax). There were
also things I didn't like (lots of dependencies, fiddlyness getting the right
ruby/openssl/puppet combination across multiple distro versions, not really out
of the box with webrick).
My answer to Aleksey was that my tool should be light weight, simple, not have
a big dependency chain, low resource consumption. My systems don't exist so
that I can have a management tool, management shouldn't be a significant footprint
on the system. I had only briefly looked at CFEngine previously, the syntax
seemed obtuse, the community seemed to be quiet, and there did not seem to be a
lot of generic policy sharing going on. I ended up deciding that CFEngine was
the only thing that met my core requirements. It's just a single package
install. It's fast, and I can work on the reusable policy pieces and help build
that community. I've gotten to know the community. It's quieter than the puppet
or chef crowds, but everyone is quite friendly and helpful. Community sharing
is also increasing with the launch of the design center [1].
I am happy with my decision to move from puppet to CFEngine 3.
I think it takes some time for CFEngine to sink in. Learning CFEngine 3 is a
great book to start with[2]. In addition to Alekseys on-site trainings I
hear there might be a correspondence course in the near future.
[1] http://cfengine.com/cfengine-design-center/sketches
[2] http://shop.oreilly.com/product/0636920022022.do
To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe
↧