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.
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.
One of the most difficult aspects of migrating existing IT applications to the cloud is setting up appropriate storage for those applications. In fact, one of the questions I am frequently asked by our customers is how to set up Rackspace Private Cloud Software to enable their business take advantage of enterprise storage. This dilemma historically has not been easy to solve, since current cloud storage solutions require either re-writing applications to use object storage or using new technologies like NoSQL databases.