The OpenDaylight Project this month came out with a new release of its software-defined networking open source platform. This latest iteration, known as Carbon, features enhancements to address cable operator concerns, Internet of Things deployments, and metro Ethernet technology.
“We continue to see new use cases emerging for OpenDaylight, including our work with Avaya on supporting IoT,” said Inocybe Technologies CEO Mathieu Lemay. “Using OpenDaylight enabled us to develop an SDN architecture for IoT that is capable of managing and securing up to 168,000 connected devices, the largest implemented in the market today.”
Carbon, the sixth release from the OpenDaylight Project, also allows for more scalability given its greater geographic reach. That enables it to be better suited for multisite deployments. And Carbon is more robust than its predecessors given its:
- improved application performance, and fault tolerance;
- its support for cableco PCMM specs;
- its streamlined service function chaining;
- its support for southbound protocols Netconf and OpenFlow; and
- its ability to enable software applications and service orchestrators to configure and provision connectivity services in physical and virtual network elements (including MEF-defined Carrier Ethernet services).
OpenDaylight today is used to support business and consumer services used by more than 1 billion subscribers around the world. Use cases for OpenDaylight include automated service delivery; cloud and network functions virtualization (NFV); network resource optimization; network visibility and control; and research, education, and government.
CenturyLink, China Mobile, Inocybe Technologies, and Tencent are among the companies leveraging OpenDaylight’s work.
“As part of our work to achieve full network virtualization, we have created our own virtualized Broadband Network Gateway using open source components including OpenDaylight and OpenStack,” said Adam Dunstan, Vice President of SDN/NFV Engineering at CenturyLink. “We used OpenDaylight software to build our SDN access controller because of its flexibility to work with legacy operations support systems as well as newer orchestration platforms.”