Building a private cloud

Clouds fall under different categories depending on the perspective. If we look at it from an ownership and control standpoint, they will fall under private, public, hybrid, and community cloud categories. If we take a service perspective, it could be IaaS, PaaS, or SaaS. Let's look at the basic building blocks of a private cloud and understand how commercial orchestrators fit in vis-à-vis OpenStack.

Commercial orchestrators

The following block diagram shows the different building blocks of a cloud that are normally seen in a private implementation with a commercial orchestrator:

Commercial orchestrators

A private cloud with a commercial orchestrator

As we can see, in this private cloud setup, additional blocks such as Self Service Portal, Metering & Billing, and Workflows & Connectors sit on top of an already existing virtualized environment to provision a virtual machine, a stack of virtual machines, or a virtual machine with some application installed and configured over it.

While most of the commercial orchestrators are extensible, some of them have prebuilt plugins or connectors to most commonly used enterprise toolsets.

OpenStack

OpenStack doesn't natively support integration with enterprise toolsets, but in lieu of this, it provides more standardized services. OpenStack feels and behaves more like a public cloud inside an enterprise and provides more flexibility to a user. As you can see in the following diagram, apart from VM provisioning, services such as database, image storage, and so on are also provisioned:

OpenStack

A private cloud with OpenStack

Please note that some of these services, which are provided as a part of the standard offering by OpenStack, can be also be orchestrated using commercial orchestrators. However, this will take some efforts in terms of additional automation and integration.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset