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 |
|---|---|---|---|---|
Support for ETSI SOL003 v3.3.1 Or-Vnfm Interface from ONAP to external VNF Manager(s) |
| Yes | ||
Support for Create, Instantiate, Query of a VNF or a prototype CNF using an external VNF Manager | SOL003 Adapter needs to support Create, Instantiate, Query of VNF or a prototype CNF using an external VNF Manager
| Yes | ||
Support for Grant request from an external VNF Manager | SOL003 Adapter needs to support Grant requests from an external VNF Manager
| Yes | ||
Support for ModifyVnfInfo using an external VNF Manager | SOL003 Adapter needs to support for ModifyVnfInfo using an external VNF Manager | Yes | ||
Support for receiving VNF Life Cycle Notifications (LCN) from a VNF Manager | SOL003 Adapter needs to receive VNF Life Cycle Notifications from a VNF Manager | Yes |
SOL003 Adapter Architecture for Guilin
The diagram depicts SOL003 VNFM Adapter Architecture.
- SOL003 Adapter continues to be an SO microservice component, and exposes its NBI to any SOL003 Adapter client in ONAP
- SOL003 Adapter is registered to MSB.
- Operator registers VNFM and VIM to ESR in AAI.
- SOL003 Adapter exposes its NBI to any SOL003 Adapter client in ONAP
- Interfaces will be refactored to be generic to allow access by other ONAP components.
- The NBI will be enhanced for additional SOL003 operation support
- SDC distributes SDC packages including the vendor original SOL004 (VNF and PNF) and SOL007 (NS) packages
- SO (SDC Controller) passes the SDC CSAR ID to ETSI Catalog Manager to invoke storage
- ETSI Catalog Manager queries for SDC CSAR with the SDC CSAR id & store SOL004/SOL007 package.
- SO (BPMN) and the SOL003 Adapter client locates SOL003 Adapter.
- SO (BPMN) and the SOL003 Adapter client invokes SOL003 Adapter.
- SOL003 Adapter retrieves VNF package from Catalog Manager.
- SOL003 Adapter gets available VNFM locations (endpoints) and gets VIM and VNF Info.
- SOL003 Adapter selects a VNFM, based on a VNFM locating mechanism.
- SOL003 Adapter and SVNFM supports SOL003 VNF LCM, granting and package management operations.
- SOL003 Adapter supports HPA-based Granting, leveraging OOF.
- SOL003 Adapter updates vServer, status and VNF association in AAI
- SOL003 Adapter and SVNFM support authentication and authorization (AAF, and vendor AA mechanism)
- 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