VF-C Guilin Architecture Review

Owned by Yuanhong Deng
Last updated: Aug 11, 2020
2 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 F release:

Due to lacking of resource, the following components will be removed from the scope of Guilin Release:

  • vfc/nfvo/driver/ems
  • vfc/nfvo/multivimproxy
  • vfc/nfvo/resmanagement
  • vfc/nfvo/wfengine
  • vfc/nfvo/driver/sfc
  • vfc/nfvo/driver/vnfm/gvnfm/juju
  • vfc/nfvo/driver/vnfm/svnfm/nokia

For those components, Guilin release will use the same as previous release. 

For more component description -  ARC VFC Component Description – Guilin (R7) Release

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

      1. Improve Instance storage function for supporting test environment auto deploy of NFV Testing Automatic Platform

      2. Update version of Python as well as Django and djangorestframework

      3. Improve platform maturity (TSC must have items)

New or modified interfaces

None

If they are modified, are the backwards compatible?

       None

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

       https://lf-onap.atlassian.net/wiki/download/attachments/16403385/nslcm-swagger.yaml?version=1&modificationDate=1574760354000&api=v2


What are the system limits

Now the component Redundancy and scaling depends on Kubernetes.


Involved use cases, architectural capabilities or functional requirements

Requirement: Automatic Testing Requirements       

Use case: Residential Broadband vCPE (Approved)


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