Dublin is the fourth release of the Linux Foundation ONAP project. It furthers ONAP’s evolution as the focal point for industry alignment around management and orchestration of the open networking stack, architecture, standards, and more. The release experienced increased end user adoption and commercial ecosystem support, the rollout of a VNF compliance and verification initiative as part of the OPNFV Verification Program (OVP), along with major functional and nonfunctional improvements.
During the Dublin release cycle, new production deployments were announced by AT&T around consumer mobility services, and by Orange to monitor the quality of network management system access in several European countries. China Mobile, China Telecom, Deutsche Telekom, Reliance Jio, Turk Telecom, Bringcom, Swisscom, KDDI, and TIM conducted testing, PoCs, or trials that in several cases will result in production deployments by Q4’19. On the vendor side, Aarna Networks, Amdocs, Huawei, and ZTE announced a pure-play ONAP distribution or products based on ONAP. In addition, new demos and support services were made available by Accenture, Ampere, Arris, Ciena, iconectiv, Netsia, Ribbon, Rift, Pantheon, Wipro, Ericsson, Nokia, and Tech Mahindra.
A new residential connectivity blueprint called Broadband Service (BBS) was introduced in Dublin that demonstrated multi-gigabit residential connectivity over PON using ONAP. The multi-release 5G blueprint had a number of key enhancements as well. There were improvements in PNF support, performance management, fault management (PM, FM) monitoring, homing using the physical cell ID (PCI) and progress on modeling to support end-to-end network slicing in subsequent releases. Finally, the CCVPN blueprint added dynamic addition of services and bandwidth on demand.
During the Dublin release cycle, the OPNFV Verification Program (OVP) was expanded to include VNF verification with ONAP (VVP+VNFSDK projects). For operator specific requirements, a Vendor Software Product (VSP) compliance check feature has also been added in SDC. Additionally, ONAP has been collaborating with ETSI NFV ISG, ETSI ZSM ISG, TM Forum, MEF, and 3GPP on providing a reference architecture for their standards development, illustrating the significance of ONAP both as a reference architecture and reference code for an automation platform. Specifically, in this release the new TM Forum Business Operating System (BOS) initiative described how ONAP will be used in its reference implementation, SO and VF-C are aligned with ETSI SOL003 (NFVO to VNFM) interface. Leveraging the VNF description (SOL001) and the 5G blueprint continues to collaborate with 3GPP on items such as performance management data collection.
The Dublin release is also packed with functional and non-functional enhancements. The design time components includes a new version of the Controller Design Studio (CDS) for model driven configuration and lifecycle management of VNFs, internationalization and localization support in the Portal framework, and basic PNF package validation. The runtime software includes orchestration support for cloud native network functions (CNF) through support for k8s cloud regions, with support for Azure and StarlingX cloud regions as well. The Policy project has several changes changes that allow service providers to create new policies, TOSCA policies, and policy types outside the development cycle of ONAP. The Dublin release has support for multisite applications in DMaaP. The DCAE module also includes new collectors, event processors, and analytics microservices. Next, the OOM project includes improved security, enhanced health monitoring, and initial support for multisite k8s clusters. ONAP also includes the MUSIC project that provides state replication, consistency management and state ownership across geo-distributed sites for ONAP projects. Finally, non-functional improvements include an initial effort around code footprint reduction, numerous security changes, additional logging, expanded documentation, and stability enhancements.