Extensive virtual network infrastructure and a wide range of diverse applications and services that may be part of the NFV, require their unified management and orchestration, which is the MANO component.
MANO component layers
The MANO component can be divided into three layers, each of which is in charge of managing others part of the framework. In a particular implementation, however, one of the applications they represent of the MANO component, can manage even more layers.
The Virtualized Infrastructure Manager is a layer that manages computing resources, storage and network resources. Several VIM instances may be implemented throughout the infrastructure. VIM fulfills in particular the following two main tasks:
∙ Resource management:
This includes managing repositories of software and hypervisors, dynamically allocating computing, memory and network resources, and managing power consumption.
∙ Managing actions:
Includes tasks associated with collecting data about errors, performance, and memory usage sources and their subsequent analysis, the results of which are used for optimization performance.
What is virtual network function
Virtual Network Functions Manager is an entity managing individual NFVs. Mostly focuses on disaster recovery, configuration management, billing, performance management, and security. A summary of these responsibilities is often referred to by the abbreviation FCAPS (Fault, Configuration, Accounting, Performance and Security Management. The VNFM is also responsible for performing activities related to VNF life cycle management.
While the VNF Manager takes care of managing VNFs, the NFV Orchestrator has at worries about the management of services that concern most VNF quantities. Using NFVO can be created end-to-end services that use most VNFs.
Since NFVO provides very extensive and often complete infrastructure management, to control systems that manage a smaller portion of the infrastructure. For example, if you start from the orchestrator required large quantities of VNF, they are only gradually function called by VIM and VNFM to take specific steps required to run of these VNFs, and is then triggered.
In addition to the virtual network infrastructure components, the NFVO can also manage other systems, such as virtual server instances, data storage, or backups. The orchestra also often provides an application programming interface with which it can be controlled by OSS and BSS.
Network service orchestration
Tacker is an official OpenStack cloud virtualization platform project that ensures VNFM and NFVO. It is developed as open source software and is designed primarily for Opentack, but it can also be used in other similar platforms. It complies with the ETSI software creation standards for the MANO component in the NFV framework. It is best to understand how the tackler works from the sketch its architecture shown in Figure no. 3.3