With a useful OpenStack lab up and running, it’s time to take advantage of some more advanced features. The first that I want to look at is adding the OpenStack Networking LBaaS (Load Balancer) to my Rackspace Private Cloud. This is currently a Tech Preview and unsupported feature of Rackspace Private Cloud v4.2 and is not considered for use in production at this time. To add this to RPC we simply make a change to the environment and run chef-client across the nodes.
For the last several weeks I’ve been explaining the setup of my home Rackspace Private Cloud and OpenStack lab. From the basic hardware configuration and adding compute nodes to adding high availability and using Neutron networking.
So after following the first three posts, we now have a Rackspace Private Cloud powered by OpenStack running with two Controllers (HA) and three Computes. So now what? Well the first thing we need to do is get our hands dirty with the OpenStack Networking component, Neutron, and create a network that our instances can be spun up on. For the home lab, I have dumb unmanaged switches – and I take advantage of that by creating a Flat Network that allows my instances access out through my home LAN on the 192.168.1.0/24 subnet.
In the first two posts I covered the basics: what hardware is involved and the basic network services that form the basis of my Rackspace Private Cloud install. In this post, I set up Rackspace Private Cloud to give an OpenStack environment consisting of highly available Controllers running as a pair with services such as the OpenStack APIs, Neutron, Glance and Keystone and three compute servers allowing me flexibility to do some testing.
In the first part of this series, I introduced the kit that makes up my home lab. There’s nothing unusual or special in the kit list, but it certainly is affordable and makes entry into an OpenStack world very accessible.
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.