Description

One of the PuppetLabs guys is trying to enforce best practices on administering Puppet modules, by using base modules and build services and roles on top of them. That way we can re-use external / third-party modules from forge.puppetlabs.com, ideally without touching them at all. He names that "the Lego approach". Full article.

The goal of this Hack Week project is to gather a few third-party modules, and test them for SLE and openSUSE. That way we can have a number of base modules, that are ready for constructing services and roles on top of them. Most of the good modules are written by PuppetLabs or their operations team. The problem is that most of the modules on forge have minimal to no openSUSE support, due to the fact that PuppetLabs operations are using Debian in their boxes. The good part though is that PuppetLabs is very cooperative in accepting patches, so ideally we will need to work on those modules and submit our patches upstream.

List of Puppet modules for hacking:

• https://github.com/puppetlabs-operations/puppet-puppet: Module to deploy and manage the Puppet Master and the Puppet Agents. It should (in theory) support various installation scenarios for the master: standalone service, apache+passenger, nginx+unicorn.
• https://github.com/puppetlabs-operations/puppet-unicorn
• https://github.com/puppetlabs-operations/puppet-nginx
• (More to be added)

Related material

• Script to deploy Puppet Master
• Script to deploy Puppet Agent
• There are already two SLE11SP2 and two openSUSE 12.3 VMs set up, along with a Debian VM to check the behavior of the upstream modules.
• zypprepo Puppet module
• r10k: A general purpose toolset for deploying Puppet environments and modules