This post is also available in: Japanese
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).
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.”
- 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.
Guest Blogger Disclaimer:
The views, opinions and positions expressed within these guest posts are those of the author alone and do not represent those of SDNCentral.com and SDNCentral, LLC. The accuracy, completeness and validity of any statements made within this article are not guaranteed. We accept no liability for any errors, omissions or representations. The copyright of this content belongs to the author and any liability with regards to infringement of intellectual property rights remains with them.
Checkout more from our Guest Bloggers:
- SDN And The Forgotten Data Plane – Is My Flow Equal To Your Flow? (5/11/2013)
- OpenDaylight Project: The Speed Promise By Kelly Herrell (5/10/2013)
- SDN: Software Defined Everything: Infrastructure Integration Will Never Be The Same (5/6/2013)
- A Taxonomy For SDN Solutions (5/4/2013)
- SDN: Are You Sure You Want Applications To Program The Network? (5/1/2013)