OpenLSO: Going Beyond NETCONF, YANG, TOSCA
Many open source Next-gen OSS and LSO projects as well as numerous different standards will guide the development of an LSO market, simply because managing, orchestrating, and provisioning services depends on coordinating many resources and data sources. Defining an industry-wide architecture will come down to coordination among several different industry groups and standards bodies – including standards and open source tools emerging for SDN and NFV.
The MEF has taken a leadership role here, but it’s important to understand that many different standards groups are driving pieces of the standards puzzle from which operators plan to draw, not to mention the many Open Source Next-gen OSS and LSO project efforts. These include The Open Networking Foundation (ONF), Optical Interworking Forum (OIF), ETSI, IETF, Open Daylight, OpenStack, and the TM Forum, among others
Development tools and open source are expected to fill in the standards gaps, connecting these standardized systems with protocols for data exchange with other systems. When LSO was first broached, the discussion within the CSP community and the network solution providers centered around Netconf, YANG, TOSCA and YAML, which help enable the automation of orchestration tasks across wide and varied collection of virtualized and physical resources.
YANG provides a description of actual network nodes and their connections. It includes a hierarchy of data that is in turn used by Netconf. YANG was developed by the Internet Engineering Task Force (IETF), and Netconf came out of the Data Modeling Working Group. Tail-f (now part of Cisco) came to the fore by being one of the first companies to use Netconf and YANG to build real-world, multi-vendor network orchestration tools. But today, many major service-provider equipment providers including Cisco, Juniper, and Ericsson all support YANG and Netconf.