Fedora do not bundle Microsoft’s core Truetype fonts for licensing reasons. Normallly I do not care, personally I prefer Liberation fonts anyway. However, today I needed Verdana.

Traditionally, the way to install these on RPM based distributions has been:

1. Grab the RPM spec file
2. Build an RPM from the spec file
3. Install RPM using the rpm command.

All well and good, however there are a couple of problems.

• Using RPM directly is frowned upon

Nowadays, Yum does various bits of house keeping in addition to RPM, so this can lead to the rpm and yum databases getting their knickers in a twist.

With a superb buzzword laden title like that, then I reckon massive traffic boost is inevitable.

Puppet is my favourite Configuration Management tool. This is not a post to try and persuade anyone not to use Ansible, Chef or any other. What I want to do is show I build Puppet based infrastuctures in such away that it meets all the basic tenets of DevOps/Agile/buzzword-of-the-month.

What to we need:

• CentOS 6 - RHEL/CentOS is pretty much the defacto enterprise distro. This will easily translate to Debian/Ubuntu or anything else.
• Puppet 3 - I like a traditional Master/Agent set up, if you prefer master-less good for you. This is my blog, my rules.
• Git
• Dynamic Environments
• PuppetDB
• Hiera
• Jenkins

All the config is stored in Git, with Jenkins watching it.

This used to be quite complex, but now is astoundingly simple. Now there is a new project call realmd. It is in recent version of Debian (Jessie and Sid) and Ubuntu (since 13.04). For Red Hat types, it is RHEL7 and Fedora (since 18).

If you're on Debian/Ubuntu, install with:

apt-get install realmd

For RHEL/Fedora:

sudo yum install realmd

Now you can go ahead and join the domain:

sudo realm join --user=<admin-user> example.com

That is it, you can check this by running sudo realm list, which will give you something like:

A break from computing today and into the world of nutrition. Cyclists love to talk about nutrition as the nature of our sport makes it a major consideration. I do not really know of any other sport where your fuel gives out before the rest of your body.

This means that cycling nutrition is big business, and expensive. A typical box of energy bars will cost about 1 euro a bar from a big box pusher, more from your LBS. To that end (as I like baking) I decided to make my own.

The current project (as of this week) has me moving away from Openstack for a while. For the next couple of months I will be immersing myself in monitor, metrics and logging. Naturally, this being a shiney new environment, this involves a significant amount of VMware time.

I have inherited an Icinga install running on Ubuntu Server, so I will be needing to run CLI commands to create checks. Simply runnning the installer does not work, as the vmware-cli package is a mixture of 32 and 64 bit commands.

For the last few weeks I have been consulting on a private cloud project for a local company. Unsurprisingly this has been based around the typical Openstack setup.

• Nova - KVM
• Neutron - Openvswitch
• Cinder - LVM
• Glance - local files

My architecture is nothing out of the ordinary. A pair of hosts each with 2 networks that look something like this:

All this is configured using Red Hat RDO. I had done all this under both Grizzly and, using RDO, it was 30 minutes to set up.

It’s been a while since I last posted anything, but it is time to. I’ve been playing around a lot with various tools for gathering information about my environment recently. One of the most important tools for storing that information is decent logging. Syslog is proven and solid, but a little creaky. For storing everything it is fine, but getting anything out is not so great.

Logstash is an awesome tool written by Jordan Sissel that is used to “collect logs, parse them, and store them for later use (like, for searching)”. It has an excellent howto, but I have one problem with it: the use of a tar file rather than packages. This easily worked around though, as Elasticsearch have it in their Yum repository.

Ages ago (it seems) I posted a howto on configure NFS using Puppet and Hiera. I have been using this happily for several months and adding a new share was is as simple as adding a line to a YAML file. I was never completely happy with it though, especially after I decided to deploy The Foreman in my lab.

The reason I was never satisfied is because The Foreman makes a really good ENC. I wanted to use this, so I have modified my module to use an ENC rather than Hiera directly.

Yesterday saw probably the biggest FLOSS news in recent times. Certainly the biggest news of 2014 so far :-) By some freak of overloaded RSS readers, I missed the announcement, but I did see this:

Day 1 at the new job. Important stuff first.. Where do I get my Red Hat ?

— Karanbir Singh 🐧 (@KaranOrg) January 8, 2014

It did not take long to dig up this and this, where Red Hat and CentOS respectively announce that they have joined forces. Some things from the announcement struck me:

I had a request on Reddit to share a document I wrote about connect Red Hat Enterprise Linux with Active Directory. The original document I wrote is confidential, but I said I would write it up.

This works for both Server 2008(R2) and 2012. If I recall correctly it will also work with 2003, but may need to minor terminology changes on the Windows side. From the Linux side, it should be fine with RHEL 6 and similar (CentOS and Scientific Linux). It should also apply to Fedora, but your mileage may vary.