Content Comparison

• Resource commitment:

  • Ericsson: primary contact: Byung-Woo Jun

• Usecase Lead:

  • Ericsson: Byung-Woo Jun

• TSC Contact:

  • Ericsson: Stephen terrill

• Participating ONAP Projects:

  • Implementation: SO, AAI, SDC (not in Dublin)

...

• • Leverage ETSI standards for VNF LCM in SO

  • Build SO VNFM Adapter

    • Use SOL003 APIs (2.5.1) for VNF LCM

    • Support operations such as create, instantiate, grant, terminate/, delete, LCN subscription and LCN

    • Support of Delete VNF is a stretch goal in Dublin

  • Enhance SO BPMN workflows & recipes

    • VNF-level Building Block workflows, leveraging VNFM Adapter 

    • Passing VNF LCM requests to VNFM using VNFM Adapter

• Note: the followings are candidates for the El Alto release.

  • Provide VNF package management for VNFM

  • Policy-based VNF scaling thru VNFM Adapter

  • Support of remaining SOL003 APIs
  • VNF Package handling (Download & Parse VNF Package)
    • Get package files from the SDC repository thru SO
    • Provide VNF package(s), VNFDs and Artifacts to VNFM
    • SO Catalog DB enhancement for SOL001/SOL004 is identified as future release work

...

• • 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
    • Grant request to SO VNFM Adapter, as a client
    • Life cycle notification
    • Terminate/Delete
  • 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
  • Due to SDC SOL004 package support issues in Dublin, manual onboarding VNF Packages are needed for SVNFM. 
  • 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

...

• SOL001/SOL004 Standard Conformance

  • VNF Package

    • A VNF Package is a compressed file that contains the following:
      • One VNF descriptor (VNFD)
      • One or more Software Image files
      • Zero or more manifest files
      • Other files

    • Package structure is SOL004 2.5.1 compliant.

    • Note: SDC in Dublin has limitations and restrictions on SOL004 support:
      • SDC does not allow custom directories such as Images, Scripts, Licenses and HOT in the root directory.
      • SDC requires MainServiceTemplate.mf and MainServiceTemplate.yaml in the root directory
      • As a result, in Dublin, the vendor VNF package should follow SDC onboarding rules. These SDC restrictions and limitations plan to be removed in the El Alto release. 

  • Cloud Service Archive (CSAR) format

    • It is a packaging construct defined in SOL004 2.5.1, identified by a .csar suffix on the package file. In SOL004, there are two package options; one with TOSCA-Metadata, one without TOSCA-Metadata directories: 

      • The CSAR file does not contain TOSCA-Metadata directory, the descriptor yaml file is in the root directory of the CSAR.

      • The CSAR file contains TOSCA-Metadata directory, the TOSCA meta file in this directory contains the location and name of the descriptor file denoted by Entry-Definitions

    • In ONAP, the second option (with TOSCA-Metadata) is supported.
    • Note: in SDC El Alto, if the VNF package with certificate and/or signature will be packaged as a zip file. The csar format continues to be used for the package without certificate and/or signature. The zip file without certificate and/or signature will be considered as an HEAT-based package.

  • VNFD

    • It is specified by the SOL001 2.5.1.

    • Note 1: that the input and get_input function would be used by a TOSCA orchestrator at run time to access the selected input parameter. If the deployment is not done by a TOSCA orchestrator, the inputs and get_input function may not be needed. The VNFD design should follow the vendor SVNFM orchestration capabilities. 
    • Note 2: in Dublin, SDC will convert SOL001 VNFD to SDC AID DM, but it is not complete. More mapping design discussions are necessary in El Alto.

...

...