VF-C Frankfurt Architecture Review

Owned by Yan Yang
Last updated: Nov 26, 2019
3 min read

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 E release:

VF-C catalog migrate to modeling etsicatalog repo which has reported in Architecture meeting 2019-10-15

Modeling project has created etsicatalog repo to intent to provide common ETSI catalog service, VF-C catalog migrates to modeling can help reduce duplication of work and promote unified architecture.

Migration plan:

  • VF-C catalog migrates to modeling etsicatalog repo and merges with modeling existing etsicatalog parser service and package management service.
  • To ensure compatibility, the APIs provided keep the same after migration , VF-C promises to update their interfaces call if needed.
  •  In F release, new requirements will be implemented in modeling etsicatalog , VF-C catalog is no longer maintained.

For more component description -  ARC VFC Component Description – Frankfurt

New component capabilities for Frankfurt, i.e. the functional enhancements

      

 Functional enhancements

      1. VF-C integrate with CLI to improve VF-C Usability

      2. Implement python-based Dmaap library to subscribe other components  topics

      3. Supporting LCM Operation rollback(Stretch goal)

      4. 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

Remove Catalog interfaces from VF-C currently interfaces

If they are modified, are the backwards compatible?

       Remove the catalog interface will not affect the existing APIs, so they are backwards compatible

Interface naming

       VF-C supports the following APIs:

  1.  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

VF-C Frankfurt API Update

What are the system limits

Now the component Redundancy and scaling depends on Kubernetes.

Involved use cases, architectural capabilities or functional requirements

  1. Use case support

        Use Case: Residential Broadband vCPE (Approved)

  2. 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 Frankfurt release