Versions Compared

Version Old Version 3 New Version 4
Changes made by

Yan Yang

Yan Yang

Saved on

Key

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

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 ComponentThere is no scope and architecture changes for VF-C in Dublin release.  

For a more detailed overview - https://wiki.onap.org/pages/viewpage.action?pageId=3247130


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/UUI 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.

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

...

 Functional enhancements

      1. VF-C enhancement and new  features:

      2. Python upgrade from python2 to python3

      3. JDK upgrade evaluate and migrate (Depend on the commit resource)

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

      5. Improve GVNFM Driver as SOL003 adapter      6. Provide 2. Implement python-based Dmaap library to subscribe other components  topics

      73. Supporting LCM Operation rollback(Stretch goal)

      8. Add 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)

    23. Supporting use cases identified by ONAP and integration:  vCPE

    34. Supporting Functional Requirements identified:

       ETSI Alignment ： migrate VF-C catalog to modeling etsicatalog

       E2E Network Slicing: (supporting NSSMF,Stretch goal depend on the commit resource )

New or modified interfaces

Update Remove Catalog interfaces from VF-C Northbound APIs to align SOL005. currently interfaces

If they are modified, are the backwards compatible?

       Yes, almost APIs required parameters has been supported by previous version，the alignment will add more optional parameter support which can comply with previous APIs. 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

      Package management APIs( VNF/PNF/NS package create/upload/delete/update ....), such as 
     api/vnfpkgm/v1/vnf_packages

     api/vnfpkgm/v1/subscriptions

Reference to the interfaces

VF-C R4 R5 API Swagger yaml

What are the system limits

...

  1. Use case support

        Use Case: Residential Broadband vCPE (Approved)

  2. Functional Requirements support 

           

...

      b. LCM(instantiate/terminate/heal/scaling) for NS and Vendor VNFs

            c. FCAPS for vendor VNFs

            d. LCM(instantiate/terminate) for open source VNFs

            e. Minimum VF-C components supporting above functionalities:

            f. NSLCM/GVNFM/Workflow/Vimproxy/EMS driver/vendor VNFM driver

Platform Maturity Targets

...

ETSI Alignment Support Image AddedREQ-101 - ETSI Alignment Support 

Platform Maturity Targets

  • Document current upgrade component strategy(TSC must have)  Image AddedVFC-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  Image AddedVFC-1574 - SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must havve) OPEN
  • SECCOM Password removal from OOM HELM charts(TSC must have)  Image AddedVFC-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  Image AddedVFC-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 Dublin Frankfurt release