We’re glad to announce that we’ve published our set of EC2 scripts on GitHub! The repository contains current versions of the code described in our previous two blog posts on EC2.

We wanted to trend our puppetmaster to give us an idea of the amount of nodes and the time it takes to compile a catalog. Searching on the web didn’t yield the results we needed, so we made our own.

We wanted to give some of our customers the ability to restart some of their own services on their development environment. To be able to do this we made a puppet module.

We published our internally developed puppet modules.

In order to make use of Amazon EC2 to its full potential, it is important that we can quickly spawn Debian installations that are automatically configured using Puppet. We accomplish this by creating our own Kumina-branded Amazon Machine Image (AMI).

An explanation on how we build our modules. Fairly high level.

By default facter returns the free and total memory and swap of a machine only in GB or MB. To remedy this we rewrote the memory.rb bundled with Puppet to return the numbers in bytes.

A couple of tips to keep in mind when running a puppetd on the puppetmaster.