The Open Network Automation Platform, a Linux Foundation project, has released ONAP Amsterdam, an open-source platform to enable network automation for carriers and service providers.
ONAP Amsterdam includes open-source software for orchestration and automation, as well as verified blueprints for two use cases. Carriers and service providers can download and deploy Amsterdam to automate their networks. Integrators and vendors can also build products and services around Amsterdam.
Amsterdam is built around two original code bases: ECOMP and Open-O. These code bases have been refactored to be modular and model-driven, with cloud-like orchestration and closed-loop automation.
Regarding closed-loop automation, Amsterdam is designed to collect and monitor network and system events related to performance, bandwidth consumption, and so on, and then automatically respond to certain conditions.
For instance, if additional VMs are required to support a service, Amsterdam can provision them automatically.
The Linux Foundation calls Amsterdam a platform, not a product, because carriers, providers, and integrators can run it wholesale, or modify it to fit their needs.
“The value proposition is that all these pieces should work together and integrate from the start,” said Arpit Joshipura, General Manager of Network and Orchestration at The Linux Foundation.
ONAP Amsterdam can manage both physical and virtual network functions (VNFs). And ONAP has published an SDK to enable third parties to develop VNFs that can run in the Amsterdam environment.
“All VNF vendors can innovate on functionality. The ONAP SDK manages the boring stuff,” said Joshipura.
A virtual function controller within Amsterdam has abstractions to communicate with and manage the VNFs. “There’s a design tool, a catalog and setup. The VNF gets pushed into runtime, integrated into lifecycle management, and off you go,” he said.
Starting With Carriers
The ONAP Amsterdam release focuses closely on carrier requirements, and that was the intention from the beginning.
The release includes blueprints for two carrier use cases: Voice Over LTE (VoLTE) and Residential vCPE, the later of which is intended to enable carriers and providers to roll out new services to customers more quickly.
However, Joshipura says carriers are also looking at running Amsterdam within their own internal IT shops that support traditional business functions, and that subsequent version of ONAP will target enterprise use cases.
“The next release will have more of a focus on classical enterprise verticals,” he said.