Would SDN, by any other name, still smell as sweet?
Perhaps I’m in the minority that is still frustrated by this, but as a marketing person who is tasked with explaining technology and solutions to customers and prospects, I feel hamstrung by a lack of a widely agreed upon definition of what is and is not “SDN” still. This usually comes up in discussions about our new Application Centric Infrastructure (ACI), and how it compares to traditional SDN concepts, as well as alternative approaches, such as overlay networks advocated by VMware.
The topic came up again this with a NetworkWorld article in which the head of VMware’s network virtualization business is now saying, “SDN will never happen” (our rebuttal). Well, what is happening, if it’s not SDN? Or just because the technology has evolved, do we need to create a new term just because some early assumptions the industry made have changed? As we start out a new year, I thought it a good time to try and reframe the definition, and look at how the trends in SDN may be shaping up to extend the concept into new areas.
Why do customers need SDN?
By early 2012, there was so much hype and expectations around Software Defined Networking, focused on the ability to “program” the network, that real customer use cases and the killer SDN app was lost in the conversation. But what slowly emerged, that is driving all the investment, pilots and product designs is a much better way to manage the data center and cloud network, and to automate IT tasks so that the infrastructure could respond dynamically to rapidly changing business conditions and requirements. The “intelligence” to make all that happen is moving from the network devices and device management consoles, to centralized policy-management platforms, orchestration tools and cloud-managers.
What’s caused the biggest evolution in SDN is the realization that very few organizations really have the desire, skills and incentives to write a new class of applications to a published API to program the network. These users are outlying use cases compared to the vast majority of organizations just looking to automate IT tasks, accelerate application deployment, make their cloud networks more flexible, and better align their IT infrastructure with business requirements. The focus has shifted from SDN being an open API/controller platform, to a platform capable of hosting a myriad of orchestration and IT workflow automation solutions that drive customers to their end goal. To that end, ACI is meeting all those objectives, and in more advanced and innovative ways than earlier SDN approaches.
1.VMware pricing model is fundamentally flawed, which is raising OpEx costs, and affecting network design decisions and scale.
VMware is charging customers per-port, per-VM, and increases the cost of networking by 2x or more, while providing lower functionality, increasing operations expense, and forcing you to adopt a different network architecture. ACI delivers more functionality with zero VM tax.
For VMware, our customers consistently report pricing starting at $50 or more per VM per month. In competitive engagements, pricing rapidly declines to $15 per VM per month, then lower depending on the negotiation. Customers do not like the per port pricing, the same as they do not like per VM pricing. All of those models get expensive and alter your designs and scale considerations.
2. Claims that ACI is a proprietary platform or policy model belies the fact that many aspects of VMware’s architecture require vendor lock-in, on top of the premium pricing model.
VMware claims that ACI is proprietary. Yet customers have to get their OVS from VMware not the open switch download, under open source license. Currently, VMware is the only hypervisor platform that locks customers into a proprietary controller -- RedHat, KVM, and Hyper-V all provide open access. ACI contributions are showing up in OpenStack, IETF drafts, and through VXLAN extensions, and is providing the most open implementation in the industry -- API’s, data model, and integration with 3rd party controllers. Federating NSX with 3rd party controllers, such as HP, is different that providing open, bi-directional programmability.
3. Openness is really measured by the breadth of infrastructures, OS platforms, orchestration models, etc., that are supported by the policy model, and ACI is rapidly outdistancing NSX in this area.
ACI supports any hypervisor, any encapsulation (VXLAN, NVGRE, VLAN, and even STT), any physical platform, storage, physical compute, layer 4 through 7, WAN, with full flexibility of any workload anywhere, with full policy, performance, and visibility in hardware. ACI supports Open vSwitch and allows a 3rd party controller to program ACI hardware components. Investment protection is built in supporting existing platforms, and within the Nexus 9000 products enabling you to run enhanced NXOS and ACI mode with a software upgrade.
Throughout 2013, I’ve had the opportunity to meet with services provider leaders from around the globe. Whether they are large or small, focused on consumer services or business, or engaged in video or mobility, their ambitions are very much in line with our strategy: To help them monetize and optimize their networks, while accelerating their ability to deliver their services.
Monetize: From innovative new managed security services, to video, cloud and new machine driven (M2M) services to enable the Internet of Everything (IoE), there are a number of new incremental revenue opportunities for service providers which sit at the very center of these trends estimated at over $2.9 Trillion over the next 10 years.
Optimize: Delivery of these new services has to be less than the cost to deploy and operate them. At the end of the day, the SP is a business, and, as all businesses, they need to be profitable. New ways to deliver these services as economically as possible are key to their success.
Accelerate: In this dynamic marketplace, service providers need to move quickly to seize these new opportunities. Gone are the days when service rollouts can take months or quarters Instead, they need to operate at “web speed” shortening the time to provision new services from months to minutes and do it in a cost-effective way. Read More »
Last week I was in London for the Gartner Data Center Conference. As always there was a wide range of interesting topics being discussed, all very useful. Working in Cisco Data Center Services, I am interested in many data center topics, however this year I was interested to hear perspectives on SDN, how the market is evolving, and how the attendees -- including many senior IT practitioners -- are considering SDN adoption.
London’s Big Ben at Night
From a Cisco perspective, we were showcasing the recently launched Application Centric Infrastructure (ACI), which generated a lot of interest. There is growing awareness among our customers that ACI could do for networks and applications what the Cisco UCS has done for the server market (with UCS server profiles in the latter proving a good analogy to help customers understand the potential of ACI).
So what were some of my key takeaways from the SDN discussion I heard here? And what were the questions that in my view are still not being discussed sufficiently across the industry?
It’s hard to believe but it’s ten months since I first blogged on Cisco Domain TenSM, which is Cisco Service’s framework to guide you on your path to data center and cloud transformation. I’ve now covered all ten domains of this concise and powerful model. I’ll now collect all articles -- including my most Cisco Domain Ten article around the breadth of SDN adoption challenges -- into this one article as a useful summary. So forgive the brevity and please do dive into the links/URLs for more information if indeed you missed these articles first time. And if you’ve read every article and watched our VoDs, please do let me know what you thought of the series -- oh, and thanks!
Going back, now, I started in December 2012, with our launch of Cisco Domain Ten, where I set the focus for my series of articles as cloud transformation. Let me summarize each article with (and for those that know me you’ll know this is a struggle ) just one sentence with the key message from each blog/domain.