What was the point of decoupling OpenStack Nova and networking? Editorial Staff

What was the significance of splitting networking out of OpenStack Nova into its own API?

    Requires Free Membership to View

Not everything works better together, and this is true for networking and OpenStack Nova. Networking was previously hardcoded in a piece of Nova -- OpenStack's compute component -- in an arrangement that hindered the ability of networking and other infrastructure areas to evolve independently of one another because developers were forced to alter both compute and network features of OpenStack together.

OpenStack's contributors recognized this fact and decoupled the two technologies by breaking networking into its own set of application program interfaces, dubbed Quantum, with the September 2012 release of OpenStack Folsom, the open source project's sixth software release. This move has far-reaching significance. Quantum will inspire commercial products that will eventually address Layer 4-7 services, and these integrated products will start to play a role in the world of virtual networking.

Do you need advice? Submit your cloud computing questions for our cloud experts to answer.


This was first published in July 2013

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: