Over the past year I’ve been using a home lab for quick, hands-on testing of OpenStack and Rackspace Private Cloud, and a number of people have requested information on the setup. Throughout the next few blog posts I will explain what I’ve got. This serves two purposes: 1) documentation of my own setup as well as 2) hopefully providing information that other people find useful – and not everything is about OpenStack.
This first post is about the tech involved and how it is set up. In subsequent posts I’ll go into further detail and then detail the installation of Rackspace Private Cloud.
Let’s first take a look at the servers I’m using:
The N40L is an incredibly cheap, 4 SATA Bay (+ CDROM Bay), low-power server with supplied 250Gb SATA. It’s a single CPU AMD Turion II processor with two cores that supports Hardware-VT. It has been superseded by the HP MicroServer N45L and often found with cash-back deals, meaning these usually come in under $215/£130.
There seems to be some caution when choosing memory for these things, with the documentation reporting they support up to 8Gb. I’ve read about people successfully running 16Gb, and through my own trial I grabbed the cheapest memory I could get and found it worked.
When choosing the PCI-X NICs and other cards, be aware that you need to use low-profile ones. The NICs I added to mine are low-profile, but the metal backing plate isn’t. A quick email to TP-Link customer services will get you some low-profile backing plates free of charge.
Networked Attached Storage
I have two QNAP NAS devices. One functions as my main network storage (nas / 192.168.1.1) with two drives in, running DHCP for my home subnet, DNS for all connected devices and Proxy (primarily used to compensate for the slow 6Mbps to 7Mbps ADSL speed I get when installing packages on my servers). The second (nas2 / 192.168.1.2) acts as a TFTP server and proxy for my servers, as well as providing a replication/backup for my primary NAS. The reason I run a proxy and TFTP next to my servers, rather than on the main NAS, is the wireless link I have between my servers and my router. Although WiFi speeds are OK, it’s a much more efficient setup (and I have two floors between my servers and WiFi router). Powerline adapters? I tried them, but due to my home having an RCD (Residual Current Device), it made Powerline adapters useless.
Essentially, I have two parts to my network –separated by two floors of a house and connected using WiFi bridging – all on a 192.168.1.0/24 subnet. I have unmanaged switches connecting the servers and NAS so there’s nothing here that’s highly exciting, but it’s presented here for clarity and completeness (and useful if you think you’ll need to WiFi bridge two parts of your network together)
(I think I should get sponsorship from TP-Link for this post!)
Overall, it looks like this (click for bigger version). Hopefully, having this detailed background info will aid you in setting up your own OpenStack environment big or small.
In the next post I’ll cover QNAP Dnsmasq Configuration providing DHCP, DNS and TFTP for my network, which allows me to PXE boot my N40L servers to kick Ubuntu and Rackspace Private Cloud.