configuration management

In the previous post I wrote about an application capable of storing key-value pairs in an hierarchical way. As this application has an rest interface to request the elements I also wrote an puppet hiera backend. This backend does allow one to use the key-value pairs defined in the application to be used in puppet manifests. This plugin can be found on github https://github.com/woutervb/hiera-central_property. The installation is quite simple, using the following steps:...

This is the second article of a trilogy. The first article can be found here In the first article the installation of puppet on ubuntu was discussed. In this article we talk about making a trust between a puppet client and a puppet server. This is the crucial step that is needed in order te let an client obtain the puppet recipes for processing. The first step is installing the puppet client on a (new) server....

This blog entry is meant as a quick lookup on how to setup an initial puppet environment on linux. The goal is to have puppet installed in a client master relationship, in which the master configuration files are stored in svn. The client is, except for the initial certificate trust, completely automated. In this part the focus is on the central server setup. As a base os for the central master ubuntu (11....

It turns out to be surprisingly easy to create a basic puppet client package. The steps involved are: download ruby from the opensuse (ruby-1.8.6.p36-4.1.i586.rpm, ruby-1.8.6.p36-4.1.src.rpm, ruby-1.8.6.p36-4.1.x86_64.rpm) download facter from opensuse (facter-1.5.7-1.1.i586.rpm, facter-1.5.7-1.1.src.rpm, facter-1.5.7-1.1.x86_64.rpm) download the puppet src.rpm from opensuse (puppet-0.25.5-1.1.src.rpm) download the puppet tar from puppetlabs (2.6.7 is the current one, http://puppetlabs.com/downloads/puppet/puppet-2.6.7.tar.gz) Install the ruby & facter package for the desired architecture (i586 = 32bit, x86_64 = 64bit). Install the puppet src....