OpenFlow is SDN, SDN is Not Only OpenFlow

OpenFlow is SDN, SDN is Not Only OpenFlow

A brief summary of the roots of Software Defined Networking (SDN), our predictions for the future of application layer emphasis, and a proposal to create a broader “big tent” definition.  Here are the highlights of our thinking:

Software Defined Networking and the Long Road to SDN’s Overnight Popularity

With its acquisition of Nicira, VMware has “done it again”; they have take a space and made it an “overnight success”.  The first time they did this was when EMC floated the IPO of VMware in 2007.  A company that sowed the seeds and did the spade work for x86 virtualization over the coarse of a back-breaking 9 years, made itself and the topic of computer virtualization, an “overnight success” to those who hadn’t been watching, learning and participating over the course of those years.

SDN solves the architecture and configuration issues of today 

We use this image to illustrate the control issues by layer. The key benefit of SDN is the application-layer control. The access, networking and security features can be controlled by application users because the needs and concerns of the cloud service provider are distinctly different than the needs and concerns of the cloud service user (the application topology deployed to the cloud and its owner).

SDN Layer Cake

The 7 Properties in the Evolution of SDN

The founders of Nicira, now part of VMware, wrote one of the original pieces surrounding the SDN concept, the Seven Properties of Network Virtualization.   They set quite a high hurdle by declaring, “network virtualization, if done correctly, should be able to run any workload that is compatible with existing networks, over any type of hardware at any location. The following list of seven properties must be in place to gain these benefits.  Without them, it is not possible to unlock the true potential of cloud.”

The 7 properties,  in summary, that news-creating Nicira founders, Open Networking Foundation folks and CohesiveFT agree on are:

  • Independence from network hardware
  • Faithful reproduction of the physical network service model
  • Follow operational model of compute virtualization
  • Compatible with any hypervisor platform
  • Secure isolation between virtual networks, the physical network, and the control plane
  • Cloud performance and scale
  • Programmatic network provisioning and control

“Big Tent” Thinking and the The Future of SDN

OpenFlow gain a foothold in the physical and virtual infrastructure layers and the multi-tenancy models mature, then OpenFlow conversations should be taking place between the provider-controlled layer and the application-controlled layer. CohesiveFT holds that we should continue and expand on the 7 properties and use “big tent” thinking to capture the momentum of SDN and virtualization.

CohesiveFT presented on this topic and our Whitepaper at the SDN Summit in London this past November. For the full PDF of the whitepaper, check out our website.

Check out more from Contributors on SDNCentral:

CONTRIBUTED ARTICLE DISCLAIMER:

Statements and opinions expressed in articles, reviews and other materials herein are those of the authors; the editors and publishers. 

While every care has been taken in the selection of this information and reasonable attempts are made to present up-to-date and accurate information, SDNCentral cannot guarantee that inaccuracies will not occur. SDNCentral will not be held responsible for any claim, loss, damage or inconvenience caused as a result of any information within this site, or any information accessed through this site.

The content of any third party web site which you link to from the SDNCentral site are entirely out of the control of SDNCentral, and you proceed at your own risk. These links are provided purely for your convenience. They do not imply SDNCentral’s endorsement or association. The copyright and any other intellectual property right any third party content belongs to the author and/or other applicable third party.

Leave a Reply