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.
When we started OpenStack, the goal was to form a community of like-minded companies and contributors to push for an open alternative to proprietary cloud software. We saw open source as a platform to foster swift innovation and to give customers more choice.
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.
I am frequently asked by analysts, users, the media and even other vendors about the production readiness of OpenStack, to which I affirm in the positive. There are also often questions about the differences between the various OpenStack distributions and offerings. I answer whenever possible by drawing the distinction between OpenStack as the open source project and as the products and services available to help make it a production-ready cloud platform. If you are unclear about the difference between an open source project and a product, I hope this blog post serves as a useful primer. I will highlight the concept of OpenStack as a service offering (yes, Cloud-as-a Service is a thing) to the concepts of project and product, using our Rackspace Private Cloud (RPC) as the canonical example for both a product and a service. To help illustrate the distinctions, I will discuss the differences between the three offerings by examining three categories:
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.
In part 1 of this series, I provided a basic overview of the OpenStack block storage service project, called Cinder, and highlighted how it is implemented with commodity hardware as well as third-party storage solutions. In this post, I will review some reference architectures and design principles for building OpenStack Cinder solutions using both commodity-off-the-shelf (COTS) hardware as well as third-party storage solutions. The content is based on experience gathered from various OpenStack-powered Rackspace Private Cloud (RPC) deployments.