Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

...

To manage vendor-provided VNFs and VIMs, ONAP wants to leverage the vendor-supplied VNFMs. For that, ONAP SO in Dublin added a plug-in capability for SVNFMs and interfaces with the plugged SVNFMs through SOL003 API standards, along with SOL004 VNF packages which include SOL001 VNFD. The SOL003 Adapter in Dublin supported the SOL003 Create, Instantiate, Terminate and Delete operations with Granting, Subscription and Notification. In the Guilin release, the additional SOL003 operations will be supported as follows. For the SOL004 and SOL001 support, see the ETSI Package Management section (ETSI Package Management).

  • Package Management for SVNFM
  • Granting Enhancement with HPA
  • Query
  • Modify (TBD)
  • Policy-based Scaling (Stretch goal)
  • Security between the Adapter and VNFMs
  • Additional operations will be determined

...

Feature

Description

SOL003 VNFM Adapter NBI Enhancement

SOL003 VNFM Adapter exposes its NBI to any VNFM Adapter Client. 

  • VNFM Adapter will be part of SO microservices, but the adapter can be invoked thru MSB.
  • It is a stepping stone for GNFC to leverage the VNFM Adapter
  • Supports additional NBI operations for the additional SOL003-based SBI
  • Support secured communication protocol and authentication and authorization via AAF
SOL003 Adapter Package Management Support

SOL003 Adapter package management support based on SOL003 APIs

  • Handle SOL003-based VNF package requests from SVNFMs
  • Query VNF packages from the ONAP-ETSI Catalog Manager
  • Provide VNF packages to SVNFMs
Granting EnhancementGranting is enhanced to support HPA by leveraging OOF
Additional of SOL003 operations 

Support of additional SOL003 operations, such as Grant enhancement, Query, Modify, Scale, Operation Status, FM, PM, Heal, VNF Indicator, Retry, Rollback, Failing, Cancelling, Resource Quota Available Notification

  • operation selections and priorities will be determined 
Mapping between SOL001 VNFD and SDC AID DM

The VNFM Adapter needs to handle mapping between SOL001 VNFD and SDC AID DM

  • Not all VNFD needs to be transformed to the SDC AID DM
  • The Adapter will map the model as much as it needs
  • Mapping to the VF-Module is questionable at this time 
Policy-based Scaling

Policy-based Scaling with VNF Indicator and VES event handling

  • Currently, SOL001 specifications does not support the VNF indicator configuration. As a result, VNFD-based VNF indicator is not supported; i.e., auto scaling is not yet supported
  • Mapping between VF-Module and ScalingAspect+Data is under discussion. Several VNF vendors indicated that they don't want to handle the VF-Module level.
Secured communication and authentication and authorization support by SOL003 Adapter

Secured communication and authentication and authorization support

  • HTTPS protocol
  • Authentication and Authorization support via AAF

Epic and User Story

Support of ETSI SOL003 v2.7.1 Or-Vnfm Interface from ONAP to external VNF Manager(s)Yes 

Epic

User Story

Description

In Guilin Plan?JIRASize
Support of ETSI SOL003 v2.7.1 Or-Vnfm Interface from ONAP to external VNF Manager(s)
SOL003 Adapter maintenance Enhancements
SOL003 Adapter maintenance EnhancementsYes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3208



Refactor SOL003 Adapter to organize its modules based on functions

Refactor SOL003 Adapter to organize its modules based on functions

  • LCM
  • Package Management
  • Notification
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2771



SOL003 Adapter gets package info from ETSI Catalog ManagerSOL003 Adapter gets package info from ETSI Catalog ManagerYes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3207








Support of ETSI SOL003 v2.7.1 Or-Vnfm Interface from ONAP to external VNF Manager(s)










Support of ETSI SOL003 v2.7.1 Or-Vnfm Interface from ONAP to external VNF Manager(s)

Executive Summary - Provide an interface adapter from ONAP Service Orchestrator to external VNF Manager(s) using  ETSI SOL003 v2.7.1 (Link to ETSI SOL003 v2.7.1compliant Interface 

  • Support for Create, Instantiate, Query of a VNF using an external VNF Manager

  • Support for Grant request from an external VNF Manager

  • Support for ModifyVnfInfo using an external Manager

  • Support for VNF Heal

  • Support for VNF Scale (out, in, level)

  • Support for Grant with Incremental resource allocation and HPA support using OOF

  • Support for received VNF Life Cycle Notifications (LCN) from a VNF Manager and translation into DCAE Events

  • Oauth2 based authentication support between ONAP and VNFM(s)

Business Impact - Enables operators and service providers to use vendor provided or internally developed ETSI compliant VNF Manager(s).  Industry compatibility.

Business Markets - All operators and service providers that are using ETSI SOL003 compliant VNF Managers

Funding/Financial Impacts - Reduction in operations expense from using industry standard Interfaces.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2695


SOL003  Adapter NBI Enhancement

Expose the Adapter NBI to any SOL003 Adapter client in ONAP

Yes
No

Image ModifiedSO-2407 - SOL003 Adapter NBI Enhancement OPEN


  • Create (Create/Instantiate)
  • Create (Create/Instantiate)
Yes
No

Image ModifiedSO-2408 - SOL003 Adapter NBI - Create (Create/Instantiate) OPEN


  • Delete (Terminate/Delete)
  • Delete (Terminate/Delete)
Yes
No

Image ModifiedSO-2409 - SOL003 Adapter NBI - Delete (Terminate/Delete) OPEN


  • Query
  • Query
Yes
No

Image ModifiedSO-2410 - SOL003 Adapter NBI - Query OPEN


  • Get Operation Status
  • Get Operation Status
Yes
No

Image ModifiedSO-2411 - SOL003 Adapter NBI - Get Operation Status OPEN


  • Modify
  • Modify
Yes
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2706


  • Heal
  • Heal VNF (triggered by SOL003 Adapter, not auto-healing)
Yes
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2707


  • Scaling (Stretch goal)
  • Scaling (Stretch goal)
Yes
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2708


SOL003 Adapter Grant Enhancement that supports HPA by leveraging OOF VNF Granting that supports HPA by leveraging OOF
Yes
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2422


SOL003 Adapter Enhancement for VNF QueryTo invoke VNF Query
Yes
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1636


SOL003 Adapter Enhancement for VNF Operation Status To invoke Operation Status
Yes
No

Image ModifiedSO-2423 - SOL003 Adapter - VNF Operation Status OPEN

SOL003 Adapter Enhancement for VNF ModifyTo invoke VNF ModifyYes Jira LegacyserverSystem JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keySO-2704


SOL003 Adapter Enhancement for VNF
Heal
ModifyTo invoke VNF
Heal
ModifyNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-

2701

2704


SOL003 Adapter Enhancement for VNF
Scaling (Stretch goal)to support Policy-based VNF Scaling support; Interface to DCAE for VES event
HealTo invoke VNF HealNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-

2705Authentication and authorization support between between SOL003 Adapter and SVNFMAuthentication and authorization support between between SOL003 Adapter and SVNFMYes 

2701

Secured communication support between SOL003 Adapter and SVNFMSecured communication between SOL003 Adapter and SVNFMYes (minimum)

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2424


SOL003 Adapter Enhancement for VNF Scaling (Stretch goal)to support Policy-based VNF Scaling support; Interface to DCAE for VES eventNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-

2425

2705


SO BPPN Workflows & Java for SOL003 Operations

SO BPMN Workflows & Java for SOL003 Operations by leveraging the SOL003 Adapter NBIs

No

Image ModifiedSO-2466 - SO BPMN Workflows and Java for SOL003 operations OPEN


  • Enhance Create/Instantiate Workflows & Associated Java code
  • Enhance Create/Instantiate Workflows & Associated Java code
    • Modify the existing workflow to separate Create and Instantiate tasks
    • Invoke the modified SOL003 Adapter NBIs
No

Image ModifiedSO-2467 - Enhance Create/Instantiate Workflows & Associated Java code OPEN


  • Enhance Terminate/Delete Workflows & Associated Java code
  • Enhance Terminate/Delete Workflows & Associated Java code
    • Modify the existing workflow to separate Terminate and Delete tasks
    • Invoke the modified SOL003 Adapter NBIs
No

Image ModifiedSO-2468 - Enhance Terminate/Delete Workflows & Associated Java code OPEN


  • Create Query VNF Workflows & Associated Java code
  • Create Query VNF Workflows & Associated Java code
    • Invoke the modified SOL003 Adapter Query VNF NBI
Yes
No

Image ModifiedSO-2469 - Create Query VNF Workflows & Associated Java code OPEN


  • Create Get Operation Status Workflows & Associated Java code
  • Create Get Operation Status Workflows & Associated Java code
    • Invoke the modified SOL003 Adapter Get Operation Status NBI
    • This operation could be used by the Instantiation and Termination of VNF; in this case, its workflow could be omitted
Yes
No

Image ModifiedSO-2470 - Create Get Operation Status Workflows & Associated Java

code OPENModifyInfo VNF

code OPEN


  • ModifyInfo VNF Workflows & Java code
  • ModifyInfo Workflows & Associated Java code
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2709


  • Heal Workflows & Java code
ModifyInfo
  • Heal Workflows &
Associated Java codeYes
  • Java ode
    • Scaling out
    • Scaling in
    • Scaling to level
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-

2709

2710

Heal Workflows Yes

  • Scaling workflows & Java code
  • Heal Workflows & Java ode
    • Scaling out
    • Scaling in
    • Scaling to level
  • Scaling workflows & Java code
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2711


CSIT enhancement for testing SOL003 Adapter enhancementCSIT enhancement for testing SOL003 Adapter enhancementNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-

2710
  • Scaling workflows & Java code
  • Scaling workflows & Java code
Yes

2295


Documentation for SOL003 Adapter enhancement featuresDocumentation for SOL003 Adapter enhancement featuresNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-

2711CSIT enhancement for testing SOL003 Adapter enhancementCSIT enhancement for testing SOL003 Adapter enhancementYes

Image RemovedSO-2295 - CSIT of SOL003 ETSI Alignment for Frankfurt OPEN

Documentation for SOL003 Adapter enhancement featuresDocumentation for SOL003 Adapter enhancement featuresYes

2429


SOL003 Adapter VNFM location enhancement

Enhance SOL003 Adapter VNFM location

  • SOL003 Adapter selects the VNFM to use on the first request and create a relationship between the VNFM and the VNF in AAI. for the case, the VNFM is deleted or changed, SOL003 Adapter needs to a re-synch mechanism for VNFM location
  • It is an exception handling for VNFM instances 
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-

2429

2778


SOL003 Adapter Architecture for Guilin

The diagram depicts SOL003 VNFM Adapter Architecture. TBD...


Gliffy
macroId36d80c09-1a48-4b44-958a-708dd5be09e9
nameSOL003 Adapter Architecture for Guilin
pagePin2



  1. SOL003 Adapter continues to be an SO microservice component, and exposes its NBI to any SOL003 Adapter client in ONAP
  2. SOL003 Adapter is registered to MSB.
  3. Operator registers VNFM and VIM to ESR in AAI.
  4. SOL003 Adapter exposes its NBI to any SOL003 Adapter client in ONAP
    1. Interfaces will be refactored to be generic to allow access by other ONAP components.
    2. The NBI will be enhanced for additional SOL003 operation support
  5. SDC distributes SDC packages including the vendor original SOL004 (VNF and PNF) and SOL007 (NS) packages 
  6. SO (SDC Controller) passes the SDC CSAR ID to ETSI Catalog Manager to invoke storage
  7. ETSI Catalog Manager queries for SDC CSAR with the SDC CSAR id & store SOL004/SOL007 package.
  8. SO (BPMN) and the SOL003 Adapter client locates SOL003 Adapter.
  9. SO (BPMN) and the SOL003 Adapter client invokes SOL003 Adapter.
  10. SOL003 Adapter retrieves VNF package from Catalog Manager.
  11. SOL003 Adapter gets available VNFM locations (endpoints) and gets VIM and VNF Info.
  12. SOL003 Adapter selects a VNFM, based on a VNFM locating mechanism.
  13. SOL003 Adapter and SVNFM supports SOL003 VNF LCM, granting and package management operations.
  14. SOL003 Adapter supports HPA-based Granting, leveraging OOF.
  15. SOL003 Adapter updates vServer, status and VNF association in AAI
  16. SOL003 Adapter and SVNFM support authentication and authorization (AAF, and vendor AA mechanism) 
  17. For integration testing, the VNFM Simulator is used.

...

For HPA requirements, see Specifying HPA Capability Requirements using TOSCA-based VNF Descriptors

<TBD>


ONAP Component Interactions for HPA

source: Policy and Information sources for HAS


Homing policies may come from vendor, service architect and ONAP Operator/Administrator.

...