- Chapter 1: NFV MANO Primer
- Chapter 2: Organizations Impacting MANO
- Chapter 3: NFV Orchestration and OSS/BSS
- Chapter 4: NFV MANO and LSO
- Chapter 5: Open Source and MANO
- Chapter 6: MANO Product Architectures
- Chapter 7: Key MANO Requirements in 2017
- Chapter 8: MANO and Service Assurance
- Chapter 9: State of MANO Deployment in 2017
- Chapter 10: Leading MANO Vendors and Products
- Chapter 11: NFV and Service Orchestration Products
- Chapter 12: Service Assurance Products
2017 NFV Report Series Part 2: Orchestrating NFV – MANO and Service Assurance is also available as a PDF Download
To realize the dream of decoupling network services from proprietary hardware, deploying networking components supported by a fully virtualized infrastructure, vendors and communication service providers (CSPs) worldwide have invested significantly in the components that make up NFV. As we describe in more detail across our three-part NFV report series, significant investment has been made across the board from the industry-standard commercial off-the-shelf (COTS) hardware, to hypervisors and the Virtualized Infastructure Managers (VIMs), to Virtual Network Functions (VNFs) and the management and orchestration (MANO) necessary to deploy these functions.
This report covers the latest in NFV MANO, the critical portion of the NFV platform that orchestrates and manages the VNFs and the NFVI to roll out NFV services. NFV MANO continues to evolve rapidly and in the last year, we’ve seen an explosion of open-source efforts in this space, including Open-O, OSM, OpenLSO, OpenBaton, Tacker and AT&T contributing their ECOMP solution to open-source. And recently, we had the major announcement of Open-O and ECOMP (OpenECOMP) coming together and merging under the auspices of the ONAP project.
At the same time, in the commercial realm, vendors from the OSS/BSS space continue their evolution in making their solutions NFV-friendly, often with a re-architecture that supports the NFV frameworks, opening up their platforms to be more modular and more API-driven. Cloud solution providers have also inserted themselves into the equation, bringing their scale and DevOps models into NFV orchestration and management especially as we migrate physical network functions first into VMs and then potentially into Containers.
Over the course of the last 12 months, many MANO solution providers have also suggested that the ETSI NFV MANO framework might be too limited and have invested resources in expanding the scope, embracing lifecyle management of network services as the end goal, instead of focusing on just orchestrating and managing individual VNFs. We’ve seen increased sophistication in creating design templates for services, and vendors adding monitoring and policy-based automation to handle scaling and failures automatically within a closed-loop system.
As well, the role of assurance in NFV roll-outs has become more prominent, with monitoring and testing becoming an integral part of NFV platforms and NFV solution roll-outs. We expect to see continued MANO evolution in 2017, especially around the harmonization of the different open source efforts, including with ONAP. And we also expect to see more integration with OSS/BSS systems as a key initiative. In some areas, we expect MANO to overlap with OSS and perhaps supplant some functions. Regardless, MANO will be a hotbed of activity in 2017 as CSPs worldwide start productizing and rolling out NFV-based services at scale.