Many tutorials are available to make your first steps like the official Getting Started with a Simple Puppet Recipe or the (french) Puppet, Administration système centralisée.

But when your puppet configuration becomes a real project, it’s great to see how the other users organize and manage it.

Many users publish their modules like the David Schmitt’s puppet complete configuration or Lab42.

We’ll try to publish our “complete” puppet project because scripts, rake tasks and tests are an important part of a good puppet project.

This project doesn’t contain private information (passwords, certificates, …), these are managed by an unpublished module.

For the moment, the interesting part is the integration of external tools : rake tasks, cucumber tests, generate scripts or the capistrano deployment (to be published).

I’ll try to describe, in future posts, these current (and future) tools.

Like the 2.0.4 ones, they are based Brightbox ubuntu packages released few hours before.

Patchs, on runtime dependency with apache2 mpm worker, have been merged.

It’s a small backport from ubuntu packages provided by Brightbox.

The installation instruction are almost the same but use the debian tryphon repository instead of brightbox one …

Phusion Passenger™ debian packages are available for etch, lenny and sid on i386 and amd64.

Update: The etch/stable packages are now available.

I forked the rubaidh’s plugin and applied the current patch created this summer for Bonnes-Ondes.

Elle aborde les points suivants :

• Une vue d’ensemble : un serveur de fichiers et ses disques durs, une station et sa carte son
• Les spécificités selon les usages : live assist et/ou diffusion automatique
• Les nécessités d’une machine de test,
• Le choix de la distribution, du packaging,
• Les différents points à étudier pour la station rivendell : carte son, jackd, gestion du reboot, interface
• Ceux autour du stockage : disques durs, mysql, nfs, backup, import, nettoyage
• Les premiers éléments à considérer dans la configuration de Rivendell
• L’importance de la supervision

Il s’agit que d’une première version. J’espère que de prochaines discussions et vos remarques viendront la compléter.

La version pdf : Rivendell, Genèse de l’installation

The official Rivendell Gallery provides a first preview of Rivendell graphic interfaces. This series is a bit limited however. A lot of potential users search a larger overview of Rivendell GUIs.

While testing the latest debian packages, I took 40 screenshots of Rivendell 1.1.1. I tried to show each Rivendell application : rdairplay, rdlibrary, rdcatch, rdlogedit, rdlogmanager …

The first objective was testing the module source packages provided with Rivendell. Between etch and intrepid, these modules can be built on several kernel versions (from 2.6.18 to 2.6.27) and waiting errors on the rivendell user mailing-list doesn”t seem a good solution

So, I looked for a way to execute module assistant into pbuilder. pbuilder has a command “execute” which takes a script, copy and execute it into the chroot. execute-module-assistant was borned.

The script installs module-assistant and executes an “auto-build” (prepare, get and build) of the specified module.
The main problem is explaining to module-assistant what are the kernel version(s) you wanted to be used. By default, it will use the .. executed kernel (uname -r) which has nothing to see with your objective.

For this reason, execute-module-assistant makes a small search in apt-cache to find installable linux headers and make module-assistant works with. As linux image names are different between debian and ubuntu, the regular expression is a bit long. We’re looking -amd64 or -686 for debian, -generic or -rt for ubuntu. The wanted architecture is specified in argument.

The last step is obtaining packages into the right directory. module-assistant uses the KPKG_DEST_DIR environment variable for that.

The result is this small command line :

pbuilder --execute [options] execute-module-assistant <module> <i386 |amd84> /path/to/put/packages

It works fine for the 2 modules, 10 platforms with 7 different kernels of the rivendell debian build.

PS: If a such tool already exists, Google didn’t find it for me :-/

Ubuntu hardy :

As there are many ubuntu hardy users, I’ve added this platform to the debian build. gpio, hpklinux and rivendell binary packages can be easily installed by adding this source :

deb http://debian.tryphon.org hardy main contrib

Ubuntu packages should be improved in a “near future” to be more compliant to the distribution policies.

Pre-compiled modules packages

With gpio-source and hpklinux-source packages, you can create the modules for your kernel. It creates sometimes few surprises according to the kernel versions.

I added to the build debian process the compilation of the gpio and hpklinux modules. According to the selected distribution (stable, … or hardy, intrepid), you will find modules for 2.6.18, 2.6.24, 2.6.26 or 2.6.27, 686, amd64 or rt kernels.

It makes life easier for everybody : user installations and developer tests. module-assistant is great tool, but pre-compiled modules are sometimes useful.

For example, hpklinux doesn’t compile with intrepid 2.6.27 kernel. A patch is pending

You can install rivendell, hpklinux and gpio packages by adding the tryphon repository in your sources.list :

deb http://debian.tryphon.org intrepid main contrib

Known limitations :

• pam_rd is disabled to workaround a pending linking problem with the ubuntu libtool 2.2.4
• I’m not very sure these packages respect all ubuntu policies : main or universe section ? ubuntu suffix to version ? some advice is welcome

Update : the source distribution was wrong in the first post (intreprrrrid). Thanks Raps for having seen it.