ETSI Open Source MANO Plans First Release Within Two Months
By The Open Source MANO (OSM) group is a project hosted by the European Telecommunications Standards Institute (ETSI). Its goal is developing an open source NFV management and orchestration software stack aligned with ETSI NFV. So far, it has been relatively slow going for the project, which has focused on gathering support from big names in the industry. Due to recent events, however, this pace is set to accelerate drastically.
The reason for optimism is that the ESTI OSM group has completed its inaugural meeting at ETSI in Sophia Antipolis, France. At the meeting it laid the technical and community engagement foundations for its 2016 roadmap. The collaborative session covered a lot of topics, including the initial OSM architecture, the election of community leaders, and project governance. As a result, Francisco-Javier Ramón Salguero of Telefonica was elected as chairman of the group, Pål Gronsund of Telenor and Andy Reid of BT were both elected as vice chairs.
The real bombshell, though, was the revealing of ETSI OSM’s roadmap, which will see the launch of the project’s Release 0 within the next two months. This release will integrate and document the code base from Telefonica, RIFT.io, Canonical and others. From that point on, new OSM releases are scheduled for every six months, with the project drawing upon best-in-class open source workflows and tools to ensure rapid development and delivery.
To support its goals of production-ready code, the OSM has formed an End User Advisory Group to provide essential guidance to overcome the challenges in functional requirements of the code, as well as those that may arise in real world integration with existing systems. This group will consist of “leading global operators” with the experience needed to offer such guidance.
“As many other groups have covered broad deployment use cases like vEPC or vCPE; we will consider much more specific use cases illustrating topics such as resource orchestration, interworking of inventory management, or more specific deployment related scenarios, for instance,” said Andy Reid, ETSI OSM vice chair. “Moreover, the requirements will be suitably described to ensure that they map to the most practical and cost effective solutions possible.”
Edited by Peter Bernstein