Project Overview
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 the ONAP tosca data model and workflow
- support integration with multi VNFMs via drivers, which include vendors VNFM and generic VNFM
- support integration with multi VNFs via generic VNFM, which does not provide VNFM function
- support integration with multi VIMS via Multi-VIM, which include the opensource and commercial VIMs
- support microservice architecture and model driven orchestration and management
VF-C has two main components: - NFV-O Component,
- GVNFM Component
Architecture changes from F release:
There is no architeture changes from F release.
For more component description - ARC VFC Component Description – Guilin (R7) Release
New component capabilities for Frankfurt, i.e. the functional enhancements
Functional enhancements
1. Complete Instance storage function
2. Support for test environment auto deploy of NFV Testing Automatic Platform
3. Working with Integration team to add VF-C related use case vCPE on daily CI chains
Platform enhancements
1. Upgrade all python component from python2 to python3
2. Improving platform maturity : Mariadb-Galera DB Consolidation ,security (i.e., S3P items)
3. TSC must have items
Document current upgrade component strategy(TSC must have)
VFC-1576 - Document current upgrade component strategy(TSC must have) OPEN- SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must have) - plan to solve the most of the security issues, but also depends on the commit resource VFC-1574 - SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must havve) OPEN
- SECCOM Password removal from OOM HELM charts(TSC must have) VFC-1575 - SECCOM Password removal from OOM HELM charts(TSC must havve) OPEN
- SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution VFC-1577 - SECCOM HTTPS communication vs. HTTP(TSC must havve) OPEN
New or modified interfaces
None
If they are modified, are the backwards compatible?
None
Interface naming
VF-C supports the following APIs:
- NSLCM APIs (Create/Instantiate/terminate/delete/scale/heal....), such as
api/nslcm/v1/ns
api/nslcm/v1/ns/(?P<ns_instance_id>[0-9a-zA-Z_-]+)/instantiate
api/nslcm/v1/subscriptions
api/nslcm/v1/ns_lcm_op_occs
Reference to the interfaces
What are the system limits
Now the component Redundancy and scaling depends on Kubernetes.
Involved use cases, architectural capabilities or functional requirements
Use case support
Use Case: Residential Broadband vCPE (Approved)Functional Requirements support
ETSI Alignment Support 
REQ-101 - ETSI Alignment Support
Platform Maturity Targets
Document current upgrade component strategy(TSC must have)
VFC-1576 - Document current upgrade component strategy(TSC must have) OPEN- SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must have) - plan to solve the most of the security issues, but also depends on the commit resource VFC-1574 - SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must havve) OPEN
- SECCOM Password removal from OOM HELM charts(TSC must have) VFC-1575 - SECCOM Password removal from OOM HELM charts(TSC must havve) OPEN
- SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution VFC-1577 - SECCOM HTTPS communication vs. HTTP(TSC must havve) OPEN
Listing of new or impacted models used by the project (for information only)
Support for service/VNF DM and align with the above data model proposed by the modelling subcommittee in Guilin release