How SDN Has Changed In 12 Months

SDN Strategy Map 2013 - Click to embiggen.

Early last year I drew a strategy map of all the elements in a Software Defined Ecosystem for a client. I drew another one a couple of weeks back to explain how the current vendor focus on controllers, and specifically, OpenDaylight is changing the nature of the market. The comparison is striking.

VCE chooses Cisco ACI as SDN Strategy Instead of VMware NSX

vce-sdn-strategy-game-on-gamble-595-opt.png

I doubt that anyone bought a Vblock because it was a market leading networking strategy. I’ve been a supporter of VCE but today I’m doubtful that choosing Cisco ACI is good strategy for their customers. My view is that most customers buy VCE Vblocks as a VMware platform. What VCE offers is a services package of fully supported storage, compute and networking that removes customer risk around VMware deployments while reselling EMC & Cisco hardware.

OpenFlow, HP Sentinel and Security SDN

HP-Sentinel-1.png

HP Sentinel is an SDN Security application that combines a reputation database, HP VAN Controller and OpenFlow to build a Campus security solution. Here is a quick overview of the process and how you can mix existing security technology with standards-based OpenFlow/SDN to provide a useful campus security tool. This product is expected to reach the market later this year.

Blessay: Categorising SDN Network Solutions and Architectures for Understanding

SDN Strategy Map (Click for Larger Image)

I’ve been digging deeper into the SDN architectures over the last few days and there may be a pattern starting to emerge. I’m currently figuring that there are four broad classes of SDN technology that you can fairly neatly classify the current products from vendors. I’m classifying SDN Solutions into three categories of Micro, Centi and Kilo as well as classifying physical devices for SDN systems into three classes of Breve, Medius and Magnus.(Yeah, OK, I’m not good at names.)