Versions Compared

Old Version 2

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version Current

changes.mady.by.user Byung-Woo Jun

Saved on

Key

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


Table of Contents

Requirements & Use Cases

The following requirements are defined in the Honolulu release - functional requirements proposed list.

Support for ETSI SOL003 v3.3.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 v3.3.1 compliant Interface  with CNF enhancements
    • Support for Create, Instantiate, Query of a VNF or a prototype CNF using an external VNF Manager
    • Support for Grant request from an external VNF Manager
    • Support for ModifyVnfInfo using an external VNF Manager
    • Support for receiving VNF Life Cycle Notifications (LCN) from a VNF Manager
  • 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.

Feature Descriptions

Feature

Description







Epic and User Story

Epic

User Story

Description

Honolulu Plan?

JIRA

Size (L/M/S)

Support for ETSI SOL003 v3.3.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 v3.3.1 compliant Interface  with CNF enhancements
    • Support for Create, Instantiate, Query of a VNF or a prototype CNF using an external VNF Manager
    • Support for Grant request from an external VNF Manager
    • Support for ModifyVnfInfo using an external VNF Manager
    • Support for receiving VNF Life Cycle Notifications (LCN) from a VNF Manager
  • 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.

Yes

Support

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



Enhance for Create, Instantiate, Query of a VNF or a prototype CNF using an external VNF Manager

SOL003 Adapter needs to support 3.3.1 Create, Instantiate, Query of VNF or a prototype CNF using an external VNF Manager

  • SOL003 Adapter should be also able to support ETSI 2.7.1 SOL003 APIs - one level backward compatibility needs to be supported
Yes
Support

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



Enhance for Grant request from an external VNF Manager

SOL003 Adapter needs to support 3.3.1 Grant requests from an external VNF Manager

  • SOL003 Adapter should be also able to support ETSI 2.7.1 SOL003 Grant APIs - one level backward compatibility needs to be supported
Yes

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



Support for ModifyVnfInfo using an external VNF Manager

SOL003 Adapter needs to support for 3.3.1 ModifyVnfInfo using an external VNF Manager

Yes
  • SOL003 Adapter should be also able to support ETSI 2.7.1 SOL003 ModifyVnfInfo APIs - one level backward compatibility needs to be supported
No


Support for receiving VNF Life Cycle Notifications (LCN) from a VNF Manager

SOL003 Adapter needs to receive 3.3.1 VNF Life Cycle Notifications from a VNF Manager

  • SOL003 Adapter should be also able to support ETSI 2.7.1 SOL003 VNF Life Cycle Notifications APIs - one level backward compatibility needs to be supported
Yes

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




SOL003 Adapter Architecture for

...

Honolulu

The diagram depicts SOL003 VNFM Adapter Architecture.


Gliffy
nameSOL003 Adapter Architecture for Honolulu
pagePin1

 




  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.


SOL003 Operations

The following SOL003 operations will be supported:

  • Create VNF/CNF
  • Instantiate VNF/CNF
  • Terminate VNF/CNF
  • Delete VNF/CNF
  • Grant enhancement
  • Query of VNF
  • Scaling (stretch goal)
  • Modify
  • Operation Status