Page History

...

• Associated JIRA tickets
  • JIRA ONAPARC-310 

    Jira
    server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key ONAPARC-310

      (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 subcomponent, following ONAP Microservice Architecture

  • Generic VNFM Adapter, supporting SOL003-compliant SVNFMs

  • Support SOL003 APIs for VNFM LCM
    • VNF Package management (Download & Parse VNF Package)
      • Get package files from the SDC repository thru SO
      • 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 create a client

      • support Create, Instantiate, Query operations

      • 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 create grant services

      • Grant decisions based on the data from OOF 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

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

...