ARC VFC Component Description – Guilin (R7) Release

Owned by Chaker Al-Hakim
Last updated: Aug 11, 2020 by Yuanhong Deng
3 min read
Page Status: Updated for R7 - Aug, 11, 2020
Component Status: Pending  ArchCom Review

1. High Level Component Definition and Architectural Relationships 



ONAP VF-C leverages ETSI NFV MANO architecture and information model as a reference, and implements full life cycle management and FCAPS of VNF and NS.

  • support NS and VNF lifecycle management based on ONAP modelling and workflows

  • support integration with multiple VNFMs via drivers, which includes vendors/specific VNFM (S-VNFM) and generic VNFM (G-VNFM)

  • support integration with multiple VNFs via providing an ONAP generic VNFM (G-VNFM)

  • support integration with multiple VIMS via Multi-Cloud, which includes open source and commercial VIMs

  • support microservice architecture and model driven resource orchestration and management

2. VFC-C API definitions

VFC provides the following interfaces:

Interface Name

Interface Definition

 Interface Capabilities

Interface Name

Interface Definition

 Interface Capabilities

VFCE-1

Portal/OSS Interface

An interface to allow for NS Lifecycle Management(ETSI SOL-005)

The NS/VNF package management function has been removed to modeling etsicatalog in Frankfurt release

VFCE-2

Service Orchestrator / Policy Interface

An interface to allow Service Orchestrator and Policy request NS Lifecycle Management ( ETSI SOL-005 )

The current VFC API documents can be found at:

https://docs.onap.org/projects/onap-vfc-nfvo-lcm/en/latest/platform/APIs/index.html

https://docs.onap.org/projects/onap-vfc-nfvo-lcm/en/latest/platform/consumedapis.html 

VFC consumes the following interfaces:

Interface Name

Interface Definition

 Interface Capabilities

API Spec (Swagger)

Interface Name

Interface Definition

 Interface Capabilities

API Spec (Swagger)

AAIE-1

Inventory Service Interface

 An interface to create, update, query, and delete resource information and relationships

AAI REST API Documentation

MSBE-1

Micro Service Bus Interface

An interface for registration and discovery with the ONAP Micro Service Bus.

Microservice Bus API Documentation

etsicatalogAPIE1~4

Modelling Tosca Parser Interfaces and catalog interfaces

An interface for the Tosca Parser from Modelling project to parse the NS and VNF Descriptors.

Etsicatalog API Document

MCE-6

MultiCloud Interface

An interface for Virtual Network Resource Management and Vim assignment

MultiCloud API Document 

DCAE-1

DCAE Interface

An interface to share FM/PM data for VNF FCAPS from the VNFs via the EMS Driver to VES Collector

DCAE API Document

OOFE-1

OOF Interface

An interface to get the VNF placement

OOF API Document



3. Component Description:

This shows all VF-C components, where each component is a standalone microservice. These microservices include:

  • Network Service Lifecycle Manager (nslcm ) which is the core component of VF-C NFVO, mainly responsible for network service management.

  • Specific Virtualised Network Function Manager (S-VNFM) Driver. VF-C currently has three vendor’s Specific VNFM drivera, including Nokia, Huawei, ZTE drivers, where each driver is a microservice. (Nokia dirver removed from R7 release)

  • Generic Virtualised Network Function Manager (G-VNFM) Drivers. VF-C can now have two generic VNFM drivers, the gvnfm driver and juju vnfm driver. (juju dirver removed from R7 release)

  • GVNFM provides the ONAP Generic Virtualised Network Function Manager capabilities.  GVNFM is composed of three microservices: vfc-vnflcm, vfc-vnfmgr and vfc-vnfres. The core microservice vfc-vnflcm is responsible for VNF life cycle management.

  • Workflow is comprised of 2 microservices, the vfc-workflow that provides the workflow management services and the vfc-workflow-engine which is the activiti workflow engine microservice. ( vfc-workflow-engine removed from R7 release)

  • Catalog is used for package management, including NS/VNF/PNF package management. (removed from R6 release and migrated to Modeling project)

  • Resource Manager is used for the management of the instances that are created by VF-C and is also responsible for resource granting operations.(removed from R7 release)

  • Multivim-proxy, provide interfaces to forward virtual resource requests to MultiCloud for resource checking ( Vim Assignment ) and Network resource creation. (removed from R7 release)

  • EMS Driver is used for VNF performance and alarm data collection and report to DCAE via the VES collector.(removed from R7 release)

4. known system limitations

Now the component Redundancy and scaling depends on Kubernetes.

5. Used Models

VFC use the following models:

  • TOSCA  - VNF Descriptor/NS Descriptor  ETSI NFV SOL001  v2.4.1 & v2.5.1  

6. System Deployment Architecture

VFC consists of 15 container microservices:

  • vfc-nslcm - Network Service Lifecycle Management microservice

  • vfc-vnflcm - The G-VNFM VNF Lifecycle Management microservice

  • vfc-vnfmgr - The G-VNFM VNF Manager microservice

  • vfc-vnfres - The G-VNFM resource management microservice

  • vfc-huawei-vnfm-driver - The Huawei S-VNFM driver

  • vfc-zte-vnfm-driver - The ZTE S-VNFM driver

  • vfc-db - The VF-C DB service

  • vfc-generic-vnfm-driver - The G-VNFM driver

The following 7 container microservices discoped from Guilin release:

  • vfc-workflow - The Workflow Manager microservice

  • vfc-workflow-engine - The activiti workflow engine microservice

  • vfc-juju-vnfm-driver - The juju G-VNFM driver

  • vfc-nokia-vnfm-driver/vfc-nokia-v2vnfm-driver - The Nokia S-VNFM driver ( current 2 versions )

  • vfc-multivim-proxy - The microservice for interfacing with MultiCloud project

  • vfc-ems-driver - The Element Management System interfaces

  • vfc-resmgr - The Resource Manager microservice

7. New Release Capabilities

  • To be completed based upon VF-C Dublin release notes

8. References

  1.  VF-C Installation & User Guide: https://docs.onap.org/en/latest/submodules/vfc/nfvo/lcm.git/docs/platform/installation/index.html