You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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

  • Associated JIRA tickets

    • JIRA ONAPARC-310  ONAPARC-310 - Getting issue details... STATUS   (SO Adapter which uses SOL003 to connect to S/G VNFM)


  • SO-ETSI Alignment Use Cases for 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, query, etc.

    • Enhance SO BPMN workflows & recipes

      • VNF-level workflows, leveraging VNFM Adapter 

      • Passing VNF LCM requests to VNFM using VNFM Adaptor

    • Policy based VNF scale out thru VNFM Adapter (Stretch Goal)

      • VNFM Adapter interfaces for VES event

      • Policy Framework for scaling decisions

      • SO workflows for VNF Scale out

    • VNF-Level Assignment modeling in SDNC and A&AI (open issue)

    • VNF Application Configuration thru VNFM Adapter and VNFM (open issue)


  • SO VNFM Adapter Requirements for Dublin


    • New SO sub-component, following ONAP Microservice Architecture

    • Generic VNFM Adapter, supporting SOL003-compliant SVNFMs

    • Support SOL003 APIs for VNFM LCM
    • 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


  • SVNFM Requirements for Dublin


    • Vendor SVNFM must be "SOL003-compliant"
    • Providing SOL003 APIs for VNFM LCM, based on ETSI VNFLifecycleManagement
    • 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
      • The "Indirect Mode" of Resource Management is being discussed, but not for Dublin


  • Component Architecture


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


  • Design Scope for Dublin


    • Use Cases
    • SOL001/SOL004 Support
    • SOL003 API Support
    • SO VNFM Adapter SOL003 API Support Design
    • VNFM Adapter VNF Package Management
    • SO BPMN Infra & VNFM Adapter Runtime
    • 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


    • TBD


  • SOL001/SOL004 Support


    1. SO SDC Controller gets a SOL004 VNF package with an SOL001 VNFD
    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

Note: SO future release could consider SOL001/SOL004 internal representation in its Catalog DB, or using the Run-time Catalog DB


  • SO VNFM Adapter SOL003 API Support 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
    • 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


  • VNFM Adapter - SVNFM SOL003 Interfaces

    • Create VNF
      -HTTP Method Type: POST
      -VNFM Endpoint: /vnf_instances/
      -Request Payload: CreateVnfRequest
      -Response Header: 201 success
      -Response Body: VnfInstance

    •  Instantiate VNF
      -HTTP Method Type: POST
      -VNFM Endpoint: /vnf_instances/{vnfInstanceId}/instantiate
      -Request Payload: InstantiateVNFRequest
      -Response Header: 202 success
      -Response Body: not applicable

    • Grant VNF Request
      -HTTP Method Type: POST
      -VNFM Endpoint: /grants
      -Request Payload: GrantRequest
      -Response Header: 201 success
      -Response Body: not applicable

    • Scale VNF

      HTTP Method Type: POST

      VNFM Endpoint: /vnf_instances/{vnfInstanceId}/scale

      Request Payload: ScaleRequest

      Response Header: 202 accepted

      Response Body: not applicable

  • Dublin Requirements
    • Build SO VNFM Adapter
      • Use SOL003 APIs for VNFM communication
      • Support operations such as create, instantiate, scale, etc.
      • Support SOL001 VNFD and SOL004 Package
    • Enhance SO BPMN workflows & recipes
      • Pass VNF LCM requests to VNFM using Adapter
    • Modeling and A&AI Updates maybe required
      • Some of this work may already be implemented
  • SO VNFM Adapter Requirements for Dublin
    • New SO subcomponent, following ONAP Microservice Architecture
    • Generic VNFM Adapter, supporting SOL003-compliant SVNFMs
    • Support SOL003 APIs
  • Design
    • ...
  • Impacted ONAP components
    • SO 
      • SO Catalog DB for SOL001/SOL004 support
      • BPMN Workflows and Recipes
      • VNFM Adapter
    • SDC 
      • Support SOL001/SOL004
    • SDNC
      • VNF-level Network Assignment, instead of VF-Module
    • A&AI
      • VNF-level Inventory Update
      • VNFM location
    • Policy
      • Scale-Out support for ETSI-based scaling
    • Modeling
      • Support SOL001/SOL004
  • Open Items
    • VNF vs. VF-Modules Modeling
  • No labels