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.
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.
One OpenStack project that seems to get less attention than others, such as Nova and Neutron, is the Cinder block storage service project. I though it may be helpful if I wrote a series of blog posts that dive into the Cinder project. I’ll start, in this post, by walking through the basics. But first, let’s put Cinder in proper context by taking a look at the available storage options in OpenStack.