Page Status: Updated for Montreal -
Component Status: Approved
Last Reviewed on:
Certified by:
1. High Level Component Definition and Architectural Relationships
- 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 | API Spec (Swagger) |
|---|---|---|---|
| https://docs.onap.org/projects/onap-vfc-nfvo-lcm/en/latest/platform/APIs/index.html | ||
| 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://onap.readthedocs.io/en/latest/submodules/vfc/nfvo/lcm.git/docs/platform/APIs/index.html
VFC consumes the following interfaces:
| 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 |
| 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:
https://docs.onap.org/projects/onap-vfc-nfvo-lcm/en/latest/platform/architecture.html
Note:
- Catalog has been migrated to Modeling/etsicatalog in F Release
- Some components including Resource Manager, Multivim Proxy, EMS Driver and Vendor EMS have been remove from Guilin Release. If necessary, you can use the version before the Frankfurt version (included)
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, but only following 8 components is in the scope of Istanbul Release:
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 release notes
8. References
- VF-C Installation & User Guide: https://docs.onap.org/en/latest/submodules/vfc/nfvo/lcm.git/docs/platform/installation/index.html