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.

How we solved a problem with the machine hitting max mmap count.

By default, instances created on Amazon EC2 will have a randomly assigned IPv4 address, which is why we’ve written a script to automatically create DNS entries in PowerDNS for instances managed through EC2.

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).

Quick fix for the squeeze-backport expired Release file, if you use your own apt proxy.

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

We, along with some customers, have our authoritative DNS setup with 1 PowerDNS master(which is unreachable over the internet), running poweradmin, and 2 BIND9 slaves(which are ns1 and ns2). This setup works great, but there is a bug in (older versions of) PowerAdmin and one in BIND that together can cause some havoc.