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)

...

• • 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
  • 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

...

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

  • 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. There are two package options. The second option is supported.

    • 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

  • VNFD

    • It is specified by the SOL001 2.5.1.

    • Note 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. 

...

• • SO VNFM Adapter component is a sub component of SO; utilizing docker image and container manged.
    • North Bound Interface (NBI)
      • RESTful APIs that support createVnf, instantiateVnf, queryVnf, grantVnf, TerminateVnf
      • Its APIs are SO specific; i.e., not SOL003-based ones
    • Business Logic layer
      • It is invoked by the NBI and provides business logic for createVnf, instantiateVnf, queryVnf, terminateVnf
      • SDNC and A&AI access to collect assignment and VimConnectionInfo
      • Accesses SdcPackageProvider for getting SOL003 package(s) and parameters
      • SdcPackageProvider
        • Supports SOL001/SOL004 package management
        • Provides getPackage, getVnfdId, getFlavorId, getVnfNodeProperty
        • Provides getPackage(s), getVnfd, getArtifactFile for SVNFM
        • Uses SDC Tosca Parser
      • GrantManager
        • Provides requestGrantForInstantiate REST API for SVNFM
        • Invokes OOF for homing decision; HPA support, and/or non-OOF decision
      • SOL003Lcn APIs
        • Supports VnfIdentifierCreationNotification, VnfIdentifierDeletionNotification, VnfLcmOperationOccurrenceNotification
    • SOL003 Communication Layer
      • It is a thin REST client layer, which sends SOL003-compliant requests to SVNFMs and receives responses/notifications from SVNFM.
      • For Grant, it provides the Grant REST endpoint for SVNFM

  
  

...