On our systems at Hetzner we only have a single /64 IPv6 range, which we use to assign addresses to virtual systems, running in Xen and KVM. Because we don’t directly bridge the virtual machines to the external interface, we have written a script that synchronizes Neighbor Discovery entries to the external interface.

On the systems we configure and maintain through Puppet, we sometimes see processes running for an excessive amount of time, causing the actual synchronization of system configuration to stall. To mitigate this, we have developed a script called checkpuppet.

In addition to the kumina repository we released last Friday, we’re happy to announce the release of our nagios-plugins-kumina repository, storing our in-house developed plugins for Nagios.

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.

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.

A second OCF script, which can be used to maintain local DNS entries when using a Hetzner failover setup.