Content Comparison

• SO-ETSI-VNFM Adapter for Dublin Presentation slide deck at ONAP Paris 2019

...

• • Vendor SVNFM must be "SOL003-compliant"
  • Providing SOL003 APIs for VNFM LCM, based on ETSI VNFLifecycleManagement
    • Use https://forge.etsi.org/gitlab/nfv/SOL002-SOL003/2.5.1/master/src/SOL003/VNFLifecycleManagement swagger for providing services
    • Create
    • Instantiate
    • Query
    • Grant request to SO VNFM Adapter, as a client
    • Life cycle notification
  • Registration itself to ONAP (thru A&AI ESR) - Name, Type, Vendor, Version, URL, VIM, Username and Password
  • Providing Subscription Services for Life-cycle Management Notifications
  • Support of the "Direct Mode" of Resource Management only
    • After receiving a grant permission, the VNFM sends requests for resources directly to VIM
    • Invoking MultiCloud from VNFM is under discussion, but not for Dublin
    • The "Indirect Mode" of Resource Management is being discussed, but not for Dublin

...

• User Stories

  • TBD

• Use Cases

• • Choose a use case for demonstrating the VNFM Adapter capabilities
  • Under investigation (will determine soon)

...

• CSAR Import, Store and Retrieve Sequences 

  • SDC stores the original vendor VNF package along with the transformed ONAP-compliant package.
  • SO uses SDC-transformed CSAR packages and VNFM Adapter uses the original Vendor CSAR package.

• 
  
  1. SO SDC Controller gets a SOL004 VNF package with an SOL001 VNFD
     1. SDC could generate two output: one ONAP-compliant CSAR and one original CSAR (maybe the first file includes the second one)
     2. SO will use the ONAP-compliant CSAR
     3. VNFM Adapter will use original CSAR
  2. SO SDC Controller stores a VNF CSAR file reference to the SO Catalog DB (e.g., TOSCA_CSAR database table)
  3. VNFM Adapter gets a CSAR package URL from the SO TOSCA_CSAR database table
  4. VNFM Adapter gets an original CSAR package file from the SDC repository
     1. It is assumed that the Adapter retrieves the original vendor provided CSAR package from SDC repository directory before it passes the package to SVNFM, where SVNFM handles the original CSAR. For that, SDC copy the full original package.
     2. There would be two CSAR packages for a service: one original package, one SDC transformed package.
     3. VNFM Adapter passes the original CSAR package to SVNFM because the SVNFM is outside of ONAP and is designed to handle the vendor CSAR package.

...

• SO BPMN VNF Workflow

  • TBD

• SO BPMN VF-Module Workflow

  • TBD

• VNFM Adapter Client 

  • TBD

• SDNC Assignment

• 
  
  • TBDPreload Assignment...

• VNFM Adapter VNF Package Management (Stretch Goal; under investigation)

...

• • Current method (Green Dots)
    • VnfLCM::locateVnfm(GenericVnf vnf)
    • Get a vnfm list from AAI ESR
    • Find a matched Vnfm, where vnfmInfo.getType() == vnf.getNfType
  • New method (Orange Dots)
    • Under development (TBD)

• SOL003 Lifecycle Management (LCM) Support and Design

• • SOL003 Interfaces between VNFM Adapter (Client) and SVNFM (Provider)

...