The Open Network Automation Platform (ONAP) Project has announced the availability of its first platform release, ONAP Amsterdam, which delivers a unified architecture for end-to-end, closed-loop network automation.
The Amsterdam release includes code from open source ECOMP and OPEN-O to provide design-time and run-time environments within a single, policy-driven service orchestration platform. Common, vendor-agnostic models allow users to quickly design and implement new services using best-of-breed components, even within existing brownfield environments. Real-time inventory and analytics support monitoring, end-to-end troubleshooting, and closed-loop feedback to ensure SLAs as well as rapid optimization of service design and implementations.
Additionally, ONAP is able to manage and orchestrate both virtualized and physical network functions.
The platform has been explicitly architected to address current real-world challenges in operating Tier-1 networks. Amsterdam provides verified blueprints for two initial use cases:
- VoLTE – by virtualizing the the core network, ONAP is used to design, deploy, monitor and manage the lifecycle of a complex end-to-end VoLTE service.
- Residential vCPE – With ONAP, all services are provided in-network, which means CSPs can add new services rapidly and on-demand to their residential customers to create new revenue streams and counter competitors.
More use cases will be developed and tested in future releases.
“Amsterdam represents significant progress for both the ONAP community and the greater open source networking ecosystem at large,” said Arpit Joshipura, general manager of Networking and Orchestration at The Linux Foundation. “By bringing together member resources, Amsterdam is the first step toward realization of a globally shared architecture and implementation for network automation, based on open source and open standards.”
“In six short months, the community has rallied together to produce a platform that transforms the service delivery lifecycle via closed-loop automation,” said Mazin Gilbert, ONAP Technical Steering Committee (TSC) chair, and vice president of advanced technology at AT&T Labs.
Meanwhile, ONAP is already beginning plans for the second ONAP release, “Beijing.” Scheduled for release in summer 2018, Beijing will include “S3P” (scale, stability, security and performance) enhancements, more use cases to support today’s service provider needs, key 5G features, and inter- cloud connectivity. Interest from large enterprises will likely further shape the platform and use cases in future releases.
ONAP will continue to evolve harmonization with SDOs and other open source projects, with a focus on aligning APIs/information models as well as B/OSS integration.
More details on Amsterdam – including download information, white papers, solutions briefs and videos – are available here. Comments from members, including those who contributed technically to Amsterdam, can be found here.