OpenStack Ocata Nova Cells Set to Improve Cloud Scalability

Among the biggest things to land in the OpenStack Ocata cloud platform release this week is the Cells v2 code, which will help enable more scale and manageability in the core Nova compute project.

Nova is one of the two original projects (along with Swift storage) that helped launch OpenStack in June 2010. The original Nova code, which was written by NASA, enables the management of virtualized server resources.


With Cells, multiple Nova compute nodes can be aggregated and managed intelligently by a single Nova API. OpenStack Ocata Cells were first introduced in the OpenStack Grizzly release in 2013.

Cells was updated to version 2 (Cell v2) in October 2015 with the OpenStack Liberty release. With Cells v2 the promise was to have a generic approach that enables OpenStack to scale across data centers. While Cells v2 has been in OpenStack for over a year now, with the new Ocata release, it now becomes more usable and stable for production deployments.

FAQ
Q
Is Red Hat going to introduce an OpenStack-based product?
A
Yes, Red Hat is planning to introduce an enterprise distribution of OpenStack. However, we are not announcing any specific product plans right now.
Q
Why is Red Hat joining the OpenStack Foundation as a Platinum Member?
A
Joining OpenStack was not a prerequisite for working with OpenStack in open source. Previously, Red Hat chose to focus on working on open source development with the OpenStack community. Now that OpenStack is moving to a foundation, Red Hat felt that this new governance structure would provide a good framework for enhancing open source collaboration around OpenStack.
Q
What is OpenStack?
A
OpenStack is an open source project for building private and public IaaS clouds. It includes three core projects around compute, object storage, and image service, as well as other related projects.
Q
How do I run a specific OpenStack release?
A
DevStack master tracks the upstream master of all the projects. If you would like to run a stable branch of OpenStack, you should use the corresponding stable branch of DevStack as well. For instance the stable/ocata version of DevStack will already default to all the projects running at stable/ocata levels.
Q
How can I document the environment that DevStack is using?
A
DevStack includes a script (tools/info.sh) that gathers the versions of the relevant installed apt packages, pip packages and git repos. This is a good way to verify what Python modules are installed.