The NFV MANO framework is comprised of orchestrators, VNFMs, and VIMs that control all of the computing, networking, storage, and virtual machine resources in an NFV data center. It is responsible for managing and maintaining the data repositories, reference points, and interfaces that are used to exchange information between all the components that make up the service to ensure the ongoing orchestration of the NFVI and VNFs.
In this section, we describe specific NFV MANO products from a collection of technology vendors.
The NFVO or orchestrator is in charge of orchestrating, managing and automating the end-to-end network service that is delivered by the VNF and NFVI. Typically there is a single orchestrator that oversees the realization of the NFV service.
The VNFM or VNF managers are responsible for the VNF lifecycle, including instantiation, updates, queries, scaling and termination. Multiple VNF managers can be deployed, depending on the environment a manager may be required for each VNF or may be in charge of several VNFs. There is active debate in the community around the current situation with each vendor driving their own VNF-Ms for managing VNFs. This can result in an explosion of multiple VNF-Ms in an NFV deployment, adding to management complexity and lack of consistency in VNF lifecycle management. Carriers are pushing back and driving vendors into supporting generic VNF-Ms (multi-vendor), allowing them to avoid a situation with a one-VNF, one-VNF-M pairing.
VIMs are used to control and manage the interaction of a VNF with the underlying computing, storage and network resources under its authority. VIMs are often a part of the virtualization layer, versus a separate solution, so the way an organization supports the virtualization layer (via hypervisor, OS or application) is likely going to be the way they support VIM functionality. VIMs provide visibility into the underlying infrastructure and handle resource management, including the:
- Inventory of resources available to the NFVI
- Allocation of virtualization enablers
- Ongoing management of infrastructure resources and allocation shifts to optimize utilization and efficiency
For the NFV MANO architecture to work properly and effectively, it must be integrated with open application program interfaces (APIs) in the existing systems. The MANO layer works with templates for standard VNFs, and gives users the power to pick and choose from existing NFVI resources to deploy their platform or element.
- ADVA Optical Networking: Ensemble Orchestrator
- Amartus: Chameleon SDS
- ATTO Research: Athena
- Avaya Inc.: Avaya SDN Fx Architecture
- *Brocade: Brocade SDN Controller
- Brocade: Brocade VNF Manager
- CA Technologies: CA Virtual Network Assurance - Mega NFV Report Pt. 1: MANO and NFVI Report Categories
- Canonical: Ubuntu OpenStack
- CENX, Inc: Exanova Service Intelligence
- Ciena: Blue Planet
- *Cisco Systems: Cisco Elastic Services Controller
- *Cisco Systems: Cisco Network Services Orchestrator (NSO) enabled by Tail-f
- *Cisco Systems: Cisco Virtual Topology System (VTS)
- Ericsson Network Manager & Ericsson Cloud Manager
- Fujitsu: Virtuora Service Orchestrator
- Hewlett Packard Enterprise (HPE): HPE NFV Director
- Huawei: Huawei FusionSphere
- *Juniper Networks, Inc.: Juniper Networks Contrail
- Mega NFV Report Pt. 1: MANO and NFVI Report Categories: Affirmed Mobile Content Cloud
- Mirantis: Mirantis OpenStack
- MRV Communications: MRV Pro-Vision
- Nakina Systems: NI-CONTROLLER
- Nakina Systems: NI-FRAMEWORK
- NEC/Netcracker: NEC/Netcracker Orchestration
- Nokia: CloudBand
- Oracle Communications: Network Service Orchestration Solution
- PLUMgrid: PLUMgrid OpenStack Networking Suite
- QualiSystems: CloudShell
- RAD: ETX-2i vCPE Platform
- Telco Systems: CloudMetro 100
- VMware, Inc.: vCloud NFV Platform