At the OpenDaylight (ODL) Summit, we got news about the development of its controller infrastructure. It’s important to remember several things about ODL:
- It has a set of northbound APIs through a variety of methods such as REST. An example project is the Virtual Tenant Network, which NEC has contributed to ODL. The apps that are created to use the NB API directly deliver the value of the SDN system to end-users.
- A set of southbound plug-ins enables interactions to data plane elements via different devices or protocols, such as Open vSwitch, or OpenFlow. This is the part that makes the system work with the real-world of devices.
- There’s lots of infrastructure code in the middle, that is mostly hidden from end-users, but technically defines ODL’s architecture.
- ODL isn’t a product per-se, but a set of projects under one umbrella. There are common components, of course, but many other elements are optional, due to the modular architecture. It’s possible for an end-user to download pieces of this open source project and construct their own ODL controller, but many choose to rely on a distribution that packages it for you. These create different flavors of ODL.