You know, the more you consider the strategic importance of the OpenDaylight project to the vendors involved, the more it becomes apparent: Daylight is defensively strategic to those who seek to marginalize the impact of SDNs in general, and of OpenFlow in particular.
OpenDaylight was formed by Cisco and IBM and stocked with other data center server and hardware vendors ostensibly to develop an open source OpenFlow controller. The intent, according to OpenDaylight founders, is to encourage an ecosystem of SDN application developers.
But when you consider the implications of SDNs and OpenFlow, and that this group is spilling over with network hardware vendors likely to be affected by them, the application ecosystem story morphs into something more urgent from a business perspective. Rather than taking the offense in encouraging an application ecosystem, OpenDaylight is a defensive maneuver to dampen the potential of OpenFlow and SDNs to usher in a "white-box" upheaval of network infrastructure as a virtualized commodity founded on merchant silicon-based switches all speaking one standard language - OpenFlow - to take software-executed directives from a controller decoupled from the switch forwarding plane.
[SOFTWARE-DEFINED WHAT?: Move over SDN; startup looking to go where only Cisco, VMware tread]
It's obvious that OpenDaylight seeks to wrest the "standards-based" OpenFlow controller designation from any other entity or company. Any OpenFlow controller that does not adhere to the OpenDaylight architecture
The Cisco Subnet blog is written by Network World managing editor Jim Duffy Visit the Cisco Subnet home page daily and while you are there, subscribe to the Cisco Alert e-mail newsletter, which includes news and views generated by the Cisco Subnet community as well as Cisco-related stories on Network World and elsewhere on the Web.
Follow Jim Duffy on Twitter