In the next 3 weeks, I’m going to (in my spare time) put together a small openstack cloud. Rather than just doing it and writing about the whole thing, I figured this would be a great series for all of my readership to follow along with (and “do”) if you have a desire.
The Common Misconception about Openstack
Let me get one thing straight with all of you reading this. Openstack is NOT virtualization; it’s orchestration. What exactly does that mean? Virtualization is the act of emulating hardware while orchestration handles virtualization and all of the management bits to make things easy to use for the common user.
Openstack is an orchestration stack. It’s about making things easy for your organization (or end user) to use. It’s about a services based architecture that will allow your customers (internal and external) to provision real usable infrastructure. It’s about efficiency and saving money and time. It’s about being smart.
Orchestration encompasses virtualization as part of the infrastructure providing access to resources commonly administered by IT. It wraps it all up in a pretty package for the non-technical end user.
Orchestration manages everything including Compute, Storage, and Network. It’s about providing a completely self-contained ecosystem for your user. It’s about convenience.
For this build, I’m going to keep it simple, but you can make it as big or small as you wish. We’re going to concentrate on provisioning network, compute, and storage. I don’t have the deep pockets of a large fortune 100 company so I unfortunately have a budget. To make this affordable for the small to medium sized business, I’m going to keep my budget for this build to $3000.00 or less. (Didn’t think that was possible? Just follow along).
I’m a father, consultant, and boyfriend. In other words, I have a busy personal life. This build from soup to nuts will take about 4 weeks if I had to guess, but it will entail all aspects of the entire project. Bear with me regarding time and the short posts. If you’re semi-technical, you should be able to follow along.
OK.. off to being a Daddy.. The next post will discuss the actual hardware selection process.