Were you aware that with Cloud Monitoring you could monitor any of your servers? No, really, any server, anywhere! It does not matter if they’re hosted on the Rackspace Public Cloud, if they’re Rackspace Dedicated Servers, if they’re in your data centers, or even another providers’ data centers. This means you can even monitor the servers already running on your existing Rackspace Private Cloud!
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.
More companies are turning towards a blended infrastructure to power their applications and to take advantage of cost savings, flexibility and security. That’s why Rackspace offers a true hybrid cloud portfolio: a mix of dedicated hardware, public cloud and the Rackspace Private Cloud.
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.