Editor's note: Glen Kemp is answering as an observer and is in no way affiliated with OpenStack or OpenDaylight.
What is the difference between network orchestration (OpenStack) and SDN control (OpenDaylight)?
OpenStack can be considered to be not one project but several, consisting of compute, storage and networking. All three platform components are managed by a dashboard Web application. Combined, they can provide a complete cloud network operating system.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Conversely, OpenDaylight is an SDN controller but with a number of northbound APIs that allow interaction with network application and orchestration services, such as OpenStack Neutron, and southbound APIs, such as OpenFlow, NETCONF and BGP. One goal of the project is to extend the services available and provide a de facto set of service APIs.
The projects are compatible, and OpenDaylight can be integrated with OpenStack using an OpenStack via Neutron plugin. This moves the complexity up the stack from OpenStack to OpenDaylight, completing the SDN picture.
As a series of technologies, OpenStack is relatively mature and is in use in production environments worldwide. This enables organizations to take advantage of the network orchestration features without necessarily deploying a full-blown controller-led SDN solution. The industry support for OpenDaylight is broad, and key players such as Cisco, Juniper, Citrix, HP, Microsoft and IBM are on board as Platinum members. As OpenDaylight moves beyond its version release, integration will further improve.
Network orchestration can be considered how a software defined network is deployed, while SDN control can be considered the "why." Network orchestration deals with the element management of a particular group of assets, either from open source or closed implementations. SDN control is the manager of managers and deals with maintaining consistent (as far as is feasible) policy across multiple groups of assets, be they discrete applications, a single data center or a worldwide-WAN.
Dig Deeper on OpenFlow
Related Q&A from Glen Kemp
What are the use cases and advantages of 400 Gigabit Ethernet in the modern data center?continue reading
A fabric topology may become necessary at some point, but for now, you can get away without one for your SDN overlay.continue reading
Glen Kemp breaks down the differences between Broadcom and Intel SDN chips and reference designs.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.