Versions Compared

Old Version 3

changes.mady.by.user Yan Yang

Saved on

compared with

New Version 4

changes.mady.by.user Yan Yang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The current VFC API documents can be found at:

https://docsonap.onapreadthedocs.orgio/en/latest/submodules/vfc/nfvo/lcm.git/docs/platform/APIs/index.html (catalog  APIs will be removed from the page)

VFC consumes the following interfaces:

...

3. Component Description:

Image RemovedImage Added

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.
  • Catalog is used for package management, including NS/VNF/PNF package management.
  • Resource Manager is used for the management of the instances that are created by VF-C and is also responsible for resource granting operations.
  • 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.
  • Generic Virtualised Network Function Manager (G-VNFM) Drivers. VF-C can now have two generic VNFM drivers, the gvnfm driver and juju vnfm driver.
  • 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.
  • Multivim-proxy, provide interfaces to forward virtual resource requests to MultiCloud for resource checking ( Vim Assignment ) and Network resource creation.
  • EMS Driver is used for VNF performance and alarm data collection and report to DCAE via the VES collector.
  • 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.

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 v 0.6.0, NS Descriptor ETSI NFV IFA014 v2.4.1 SOL001  v2.4.1 & v2.5.1  

6. System Deployment Architecture

VFC consists of 16 15 container microservices:

  • vfc-nslcm - Network Service Lifecycle Management microservicevfc-catalog - The Catalog microservice

  • vfc-resmgr - The Resource Manager microservice

  • vfc-workflow - The Workflow Manager microservice
  • vfc-workflow-engine - The activiti workflow engine microservice
  • vfc-generic-vnfm-driver - The G-VNFM driver
  • vfc-juju-vnfm-driver - The juju G-VNFM driver
  • vfc-huawei-vnfm-driver - The Huawei S-VNFM driver
  • vfc-zte-vnfm-driver - The ZTE S-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-db - The VF-C DB service
  • 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

...