Content Comparison

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

...

• SO VNFM Adapter Requirements for Dublin

• • New A new SO sub-component, following ONAP Microservice Architecture

  • A Generic VNFM Adapter, supporting SOL003-compliant SVNFMs

  • Support of SOL003 APIs for VNFM LCM
    • VNF Package management (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 under discussion, for future release
    • Invoking SVNFM based on SOL003 VNF LCM APIs as a client

      • use https://forge.etsi.org/gitlab/nfv/SOL002-SOL003/2.5.1/master/src/SOL003/VNFLifecycleManagement swagger to generate a client

      • support Create VNF, Instantiate VNF, Query VNF operations as a client

      • collect data for SOL003 API parameters from SDNC, A&AI and OOF

    • Granting, based on ETSI VNFLifecycleOperationGranting

      • use https://forge.etsi.org/gitlab/nfv/SOL002-SOL003/tree/master/src/SOL003/VNFLifecycleOperationGranting swagger to generate grant services

      • Grant decisions based on the data from OOF and/or VIM registration

    • Subscription to SVNFM for getting notifications
      • STARTING, PROCESSING, COMPLETED
  • SVNFM selection based on configuration values that are configured during VNF on-boarding and VNFM registration. Two methods are considered:
    • Correlation between VNF NF Type and VNFM Type (Nokia method)
    • Utilizing VNFD vnfm_info:type, VNFM registration values: VNFM type, Cloud region, vendor

...

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

...

• • The following diagram depicts the component architecture.
  • The VNFM Adapter will be a SO sub-component; packaged as a docker and running in a container.
  • VNFM will register into A&AI ESR and VNFM Adapter will locate a proper VNFM based on VNF NF Type or others.
  • Communications between the VNFM Adapter and SVNFM will be SOL003 API-based.
  • Communications between the SO BPMN Infra VNFM Adapter REST Client and the VNFM Adapter NBI will be SO-specific; i.e., it does not follow ETSI standards at this time.
  • SO SDC Controller receives SOL001/SOL004-based CSAR from SDC, and stores the CSAR reference URLs to TOSCA_CSAR database table. 
    • Note: there could be two CSAR files: one for the original CSAR and one for ONAP-compliant CSAR
    • It is assumed that SDC keeps the original vendor VNF packages in their repository, and VNFM Adapter retrieves the original vendor CSAR files from the repository.
  • New VNF-level workflows that use VNFM Adapter will be implemented, and these new workflows will be invoked from the (Network) Service-level workflows based on VNF type and other criteria.
  • Unlike the existing SO VNF/VF-Module workflows, the new VNF-level/VF-Module-level workflows will NOT interact with OpenStack directly. The workflows will delegate the VNF LCM requests to VNFM Adapter, and VNFM Adapter will delegate the requests to VNFM further. Then, VNFM will interact with VIM directly. In Dublin release, the direct mode of resource management will be supported as depicted above.

...

• • Use Cases
  • VNFM Adapter Design
  • SOL001/SOL004 Support & Design
  • SO BPMN Infra & VNFM Adapter Run-time Scenario
  • SOL003 API Support
  • SO VNFM Adapter SOL003 API Support Design
  • VNFM Adapter VNF Package Management
  • SDNC Assignment Management
  • VNFM Adapter Locating SVNFM
  • VNF Life-cycle Granting
  • VNFM Adapter Homing Decision for VNF Granting
  • VNF and VF-Module Deduction

• Use Cases

• • TBDChoose a use case for demonstrating the VNFM Adapter capabilities

• VNFM Adapter Design

  
  

  

  • • SO VNFM Adapter component (a sub component of SO; docker image and container manged)
    • North Bound Interface (NBI)
      • RESTful APIs that support createVnf, instantiateVnf, queryVnf, grantVnf
      • 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
      • SDNC and A&AI access to collect assignment and VimConnectionInfo
      • Access 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
    • SOL003Lcn APIs
      • Support VnfIdentifierCreationNotification, VnfIdentifierDeletionNotification, VnfLcmOperationOccurrenceNotification

...