Ohad Levy, 09/03/2010 | Source: The Foreman: Blogs
Hello All,
Its been a while since last release.. so I'm happy to announce the next stable release of Foreman (0.1-4).
Main new features include:R.I. Pienaar, 03/03/2010 | Source: R.I.Pienaar - www.devco.net
I've had some good feedback on my previous post about the puppet localconfig parser, have implemented the requested features so here's a new version.
First the ability to limit what resources are being printed:
# parselocalconfig.rb --limit package Classes included on this node: fqdn common::linux Resources managed by puppet on this node: package{redhat-lsb: } defined in common/modules/puppet/manifests/init.pp:15
You should only see package resources. You
[ Read more... ]Nico, 02/03/2010 | Source: cd ~
I’ve been lazy at maintaining my servers recently and decided to start playing with puppet reports. First I started with something simple that helps me to find on which machines my manifests have some failure.
So here’s a quick and dirty code that goes through Puppet’s reportdir and points out neglected machines.
#!/usr/bin/env ruby require 'puppet' require 'find' require 'yaml' require 'optparse' Puppet[:config] =
R.I. Pienaar, 26/02/2010 | Source: R.I.Pienaar - www.devco.net
Last year I wrote a tool to parse the localconfig.yaml from Puppet 0.24 and display a list of resources and classes. This script failed when 0.25 came out, I've updated it for 0.25 support.
The yaml cache has some added features in 0.25 so now I can also show the list of tags on a node, output would be:
[ Read more... ]# parselocalconfig.rb /var/lib/puppet/client_yaml/catalog/fqdn.yaml Classes included on this node: fqdn common::linux <snip> Tags for this node: fqdn
Nico, 26/02/2010 | Source: cd ~
On my Solaris machines at $WORK I use iMil’s pkgin to install additional software. But until today, I add to do it by hand, on every machine… Not really what I like to do after a little more than a year using puppet. So I wrote a provider to manage packages with pkgin. It was very informative on puppet internals and I learned more about my favorite config management system.
Enough talking, here is the file : pkgin.rb
Example of use in a manifest :
class foo { package {
SPUG, 24/02/2010 | Source: SPUG
The western Switzerland Linux User Group (GULL) is organizing a presentation of puppet and automated system administration practices. This talk will take place on tuesday 2. March at 19.30 in Beausobre, Morges and will be in french. More details can be found on the GULL’s website.
Nico, 22/02/2010 | Source: cd ~
At $WORK I started using Nginx a while ago, first as a front end to my mongrel instances for puppet. Recently I began to use it for one of its most know features : reverse proxy (and caching too). Of course this work had to be puppetized !
This is a summary of what I’ve done :
R.I. Pienaar, 19/02/2010 | Source: R.I.Pienaar - www.devco.net
While building up complex configs with Puppet you often need to build up one file from many fragments. This is useful for files like older sysctl.conf files and maybe named.conf files.
The basic pattern is you want to manage a file, but want the contents to be very different from node to node. A fragment based system lets you register different contents into a file on different nodes. It's exactly like the conf.d directory you'd find in Apache but for daemons that does not support this construct on
[ Read more... ]kartar, 19/02/2010 | Source: Kartar.Net
Over the last year or so a bunch of presumptuous European sysadmins and developers, joined by some of their American brethren and even a couple of us antipodeans (there are others too!) have been talking about a concept called DevOps. DevOps is the merger of the realms of development and operations (and if truth be told elements of product management,QA, and *winces* even sales should be thrown into the mix too).
The Broken
So … why should we merge or bring together the two realms? Well there are
[ Read more... ]kartar, 13/02/2010 | Source: Kartar.Net
In a recent post I talked about how easy it is to generate Puppet types and providers. In that post I used the example of a very simple Subversion and Git repository type, called repo. I’d like to show another example of a type and provider, this one used to manage the contents of the /etc/shells file. This type and provider makes use of some built-in Puppet functionality that allows the simple parsing of files and the management of their contents. To do this Puppet has a provider called
