Puppet is fully packaged for ubuntu 12.04, with both server and client version 2.7. Here is the list of packages for a Puppet client install:
_* Opt admin puppet Centralized configuration management - agent startup and compatibility scripts _* Opt admin puppet-commo Centralized configuration management _* Opt interpre ruby1.8 Interpreter of object-oriented scripting language Ruby 1.8 _* Opt interpre ruby Transitional package for ruby1.8 __ Opt universe puppet-el syntax highlighting for puppet manifests in emacs __ Opt universe vim-puppet syntax highlighting for puppet manifests in vim __ Opt admin etckeeper store /etc in git, mercurial, bzr or darcs _* Opt libs libruby Transitional package for libruby1.8 _* Opt interpre libshadow-ru Interface of shadow password for Ruby 1.8 _* Opt libs libaugeas-ru Augeas bindings for the Ruby language _* Opt admin facter collect and display facts about the system _* Opt devel debconf-util debconf utilities __ Opt universe ruby-selinux Ruby bindings to SELinux shared libraries __ Opt universe libselinux-r Transitional package for ruby-selinux __ Opt interpre librrd-ruby1 time-series data storage and display system (Ruby 1.8 interface) _* Opt libs libruby1.8 Libraries necessary to run Ruby 1.8 __ Opt interpre ruby1.8-exam Examples for Ruby 1.8 __ Opt universe ri1.8 Ruby Interactive reference (for Ruby 1.8) __ Opt universe ri Transitional package for ri1.8 __ Opt devel ruby-dev Transitional package for ruby1.8-dev __ Opt devel ruby1.8-dev Header files for compiling extension modules for the Ruby 1.8 _* Opt libs libaugeas0 Augeas configuration editing library and API __ Opt universe ruby-json JSON library for Ruby _* Opt libs libreadline5 GNU readline and history libraries, run-time libraries _* Opt misc augeas-lense Set of lenses needed by libaugeas0 to parse config files __ Opt admin augeas-tools Augeas command line tools __ Opt doc augeas-doc Augeas lenses documentation HTH, Hendrik On 14/11/12 02:49 PM, Gustin Johnson wrote: > It looks like CFEngine for now. What put me over the top was twofold: > > First it is already packaged with Ubuntu, which neither Chef nor Puppet > seem to be. > > Second, it seems some people have done some interesting things with > CFEngine in front of Kickstart and libvirt/kvm. > > We'll see how this all goes. > > > On Tue, Nov 13, 2012 at 5:36 PM, Gustin Johnson <[email protected] > <mailto:[email protected]>> wrote: > > Almost all of the machines are recent Ubuntu (12.04, with > the possibility of the occasional 10.04). I am currently leaning > towards cfengine. As a bonus I know that we can extend cfengine to > manage Windows machines as well. This is not really a requirement > at the office since we also have SCCM, but the test lab (my > department's as well as my own) do not. > > By the sounds of it, this might make for a good presentation in the > new year, not that I am in any danger of having too much time on my > hands :) > > I will let you know how it goes. > > > On Tue, Nov 13, 2012 at 3:21 PM, Andrew Ludwar > <[email protected] <mailto:[email protected]>> wrote: > > 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] <mailto:[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
