...
The following architecture depicts the "target" ETSI-aligned hierarchical orchestration.
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
ONAP NFVO Architecture for Honolulu
The following architecture depicts the ETSI-aligned hierarchical orchestration for Honolulu.
Gliffy Diagram macroId 9d8c7f55-cbf8-429e-a45f-1f6f6de8c5cd displayName ONAP SO Hierarchical Orchestration - H Implementation name ONAP SO Hierarchical Orchestration - H Implementation pagePin 4
Customization Support
The following diagram depicts the SO NFVO plugin capabilities.
...
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
SO Refactoring
Requirements & Use Cases
The following requirements are defined in the Honolulu release - functional requirements proposed list.
...
- For Honolulu release, only Epics and User Stories/Sub-Tasks with the Yellow background will be done. Rest of them will be handled in the future release (e.g., Istanbul).
- Priority:
- High:
- Enhance SO NFVO SOL005 NBI API Handler
- Conformance to ETSI 3.3.1 and function regression testing
- Enhance SO NFVO NS LCM and Workflows Management
- Conformance to ETSI 3.3.1 and function regression testingSupport of VNF VL operations
- Support for MultiCloud Adapter
- Support for NS LCM Database Management Enhancement for VL operations
- Enhance SO NFVO SOL005 NBI API Handler
- High:
- Medium:
- Support for secure communication across ETSI-Alignment components
- Low: (it is decided to postpone to Istanbul release)
- Support of SOL005 NBI LCM Subscription and Notification APIs
- Support of LCM Subscription and Notification functions
- Support for NS LCM Database management for Subscription
- Support for package notification endpoint for ETSI Catalog Manager notification
- Support for NS package subscription to ETSI Catalog Manager
- Support of VNF VL operations
- Support for MultiCloud Adapter
- Support for NS LCM Database Management Enhancement for VL operations
Epic | User Story | Sub-Task | Description | Honolulu Plan? | JIRA | Priority | Size (S/M/L/XL) | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Support for NFVO Microservice Plugin | SO NFVO needs to support ETSI NFVO functional Microservice plugin capabilities, leveraging MSB, SpringBoot and Kubernetes, for hosting NFVO function components by configuration. So, the SO NFVO can be customized in a future by operators.
Note: we are not building the Microservice service registration, aggregation, discovery and routing engine itself, but we are leveraging the engine's capability (e.g., MSB, API Fabric, Kong, or Kubernetes & service discovery) to offer configuration of NFVO Microservice components access. In Honolulu, the following will be supported
| No | |||||||||||
<requirements for each SO-NFVO Microservice>
| Support for NFVO Service Registration | Supports NFVO Micro-Service Registration for plugging in microservices
| No | ||||||||||
<requirements for finding SO-NFVO sub-microservices>
| Support for NFVO Service Discovery | Supports NFVO Micro-Service Discovery with version control
| No | ||||||||||
<requirements for communication between SO-NFVO sub-microservices>
| Support for NFVO Inter-Service Communication | Supports for NFVO Inter-Service Communication
| No | ||||||||||
Start from here for Honolulu... | |||||||||||||
Enhance SO NFVO SOL005 NBI API Handler | SO NFVO NBI API Handler needs to enhance its NBI APIs to support:
Preconditions:
SO NFVO NBI API Handler provides SOL005-compliant Restful Northbound APIs for SO/SOL005 Adapter/External RESTful client
| No |
|
Upgrade SO NFVO NBI with 3.3.1 SOL005 API Swagger | SO NFVO NBI API Handler needs to upgrade its SOL005 API swagger to 3.3.1.
|
No |
|
Enhance the |
Instantiate NS NBI | SO NFVO NBI API Handler needs to enhance its |
- Leveraging ETSI 3.3.1 swagger upgrade, upgrade the Create NS NBI code to support 3.3.1
- Follow and confirm 3.3.1 changes on the message sequencing, request, response, pre- and post-conditions.
- Preconditions:
- SOL007 NS packages are stored in ETSI Catalog Manager.
- if SOL 005 Adapter is not ready,
- the Cli-based (Postman-based) SO NFVO Client is ready to send the SOL005-compliant Create NS request
- if the SOL 005 Adapter / Simulator is ready,
- SOL 005 Adapter / Simulator subscribed to SO NFVO for LCCN notifications
- The SO-NFVO (so-etsi-nfvo) pod is ready
- Test the following scenarios:
- SO NFVO NBI API Handler needs to support the SOL005-compliant Create NS API
- Supports Create NS request API: POST /api/nslcm/v1/ns_instances (CreateNsRequest)
- Supports Create NS responses with NsInstance with 201 (for success) or an error
- Returns a dummy 201 until the backend business logic is ready
- Only mandatory attributes of NsInstance will be set.
- Support successful or error conditions
- Sends NsIdentifierCreationNotification to the NFVO subscriber(s) (e.g., ONAP SO SOL005 Adapter)
- Note: this will be handled by the separate user story: Sends NsIdentifierCreationNotification to the NFVO subscriber(s) (e.g., ONAP SO SOL005 Adapter)
- SO NFVO NBI API Handler needs to support the SOL005-compliant Create NS API
- Post conditions: the NS Instance is set as NOT_INSTANTIATED state
Note: secure communication is handled by a separate user story, SO-3165.
Jira | ||||||
---|---|---|---|---|---|---|
|
Instantiate NS to ETSI 3.3.1 from ETSI 2.7.1
| No |
|
Enhance the Terminate NS NBI | SO NFVO NBI API Handler needs to enhance its Terminate NS to ETSI 3.3.1 from ETSI 2.7.1
| No |
|
Enhance the Delete NS NBI | SO NFVO NBI API Handler needs to enhance its Delete NS to ETSI 3.3.1 from ETSI 2.7.1
| No |
|
Enhance Get NS Operation Status NBI | SO NFVO NBI API Handler needs to enhance its Get NS operation to ETSI 3.3.1 from ETSI 2.7.1
Note: Instantiate NS and Terminate NS use the GET individual NS LCM operation occurrence
|
SO-2862 - Get NS Operation Status NBI support OPEN
No |
|
------ | |||||||||||||
Support for SO NFVO SOL005 NBI Subscription APIs | SO NFVO NBI API Handler needs to support 3.3.1 SOL005-based Subscription APIs Supports SOL005-compliant Restful Northbound Subscription and Notification APIs for SO/SOL005 Adapter Supports the following SOL005 Subscription APIs, which are defined in the sub-tasks:
Note: if the SOL005 Adapter is not enhanced for SO NFVO, its simulator will be developed for simulating the subscription handling.
| No |
|
Create NS Subscription NBI | SO NFVO NBI API Handler needs to support Create NS subscription NBI
| No |
|
Get NS Subscription NBI | SO NFVO NBI API Handler needs to support the optional Get NS Subscription NBI
| No |
|
Delete NS Subscription NBI | SO NFVO NBI API Handler needs to support Delete NS Subscription NBI
| No |
|
Send NS Notifications (As a Client) | SO NFVO NBI API Handler needs to support sending NS notifications to the subscribed component (e.g., SOL005 Adapter)
| No |
|
Support for secure communication across ETSI-Alignment components | ETSI-Alignment components need to communicate each other securely via HTTPs
|
No |
|
Support for secure communication between SOL005 Adapter and SO NFVO | SOL005 Adapter and SO NFVO need to communicate each other thru secure communications via HTTPs
|
No |
|
Support for secure communication between SO NFVO BPMN and SOL003 Adapter |
(We keep it as HTTP since it would be internal component communications). If so, we will close this. | No |
|
Support for secure communication between SOL003 Adapter and VNFM Simulator / VNFM | SOL003 Adapter and VNFM Simulator / VNFM need to communicate each other thru secure communication via HTTPs |
No |
|
Support for secure communication between SO NFVO and ETSI Catalog Manager | SO NFVO and ETSI Catalog Manager need to communicate each other thru secure communication via HTTPs (note: the current communication is secure, but we may want to enhance it in Honolulu. TBD) |
No | |||||||
Support for secure communication between SOL003 Adapter and ETSI Catalog Manager | SOL003 Adapter and ETSI Catalog Manager need to communicate each other thru secure communication via HTTPs (note: the current communication is secure, but we may want to enhance it in Honolulu. TBD) | Yes, but TBD | |||||
------ | |||||||
Enhance SO NFVO NS LCM and Workflows Management | SO NFVO needs to enhance NS LCM and Workflows management - validate if it works with 3.3.1 Test the following NS LCM functions (that are defined in the subsequent user stories) and verify they are still working for 3.3.1
|
No |
|
Enhance Create NS LCM and Workflows | SO NFVO needs to enhance the Create NS backend operations and workflows which do the following sequence - validate if it works with 3.3.1
|
No |
|
Enhance Instantiate NS | SO NFVO needs to enhance the Instantiate NS backend operations and workflows which do the following sequence: - validate if it works with 3.3.1
curl -X POST /api/parser/v1/parsernsd' \ -H 'Content-Type: application/json' \ --data-raw '{ "csarId": "csarid", "packageType": "ns", "inputs": "[]" }'
|
No |
|
Enhance Terminate NS | SO NFVO needs to enhance the Terminate NS backend operations and workflows which do the following sequence: - validate if it works with 3.3.1
|
No |
|
Enhance Delete NS | SO NFVO needs to enhance the Delete NS backend operations and workflows which do the following sequence: - validate if it works with 3.3.1
|
No |
|
Enhance Get NS Operation Status | SO NFVO needs to enhance the Get NS Operation Status operation and workflows which do the following sequence: - validate if it works with 3.3.1
|
No |
|
Create NS Subscription | SO NFVO needs to support the Create NS Subscription operation and workflows which do the following sequence: <Create NS Subscription: note: the following workflow is a template, and it can be enhanced as needed.>
| No |
|
Get NS Subscription | SO NFVO needs to support the Get NS Subscription operation and workflows which do the following sequence: <Get NS Subscription: note: the following workflow is a template, and it can be enhanced as needed.>
| No |
|
Delete NS Subscription | SO NFVO needs to support the Delete NS Subscription operation and workflows which do the following sequence: <Delete NS Subscription: note: the following workflow is a template, and it can be enhanced as needed.>
| No |
|
Send NS Notifications | SO NFVO needs to support the Send NS Notification operation and workflows which do the following sequence: <Send NS Notification: note: the following workflow is a template, and it can be enhanced as needed.>
| No |
|
Support for Create VLs | SO NFVO needs to support the Create VLs operation and workflows which do the following sequence:
|
No |
|
Support for Delete VLs | SO NFVO needs to support the Delete VLs operation and workflows which do the following sequence:
|
No |
|
Support for Get VLs | SO NFVO needs to support the Get VLs operation and workflows which do the following sequence:
|
No |
|
Support for granting VNF (non OOF-based one) | SO NFVO needs to support the granting VNF (non OOF-based one) operation and workflows which do the following sequence:
| No |
| ||||||||||||
Support for NS Catalog DB Adapter | SO NFVO needs to enhance access for ETSI Catalog Manager
Note: it is done in Guilin. | No | |||||||||||||
Support for queries for VNF/ |
| No | |||||||||||||
Support for package notification endpoint for ETSI Catalog Manager notification |
|
No |
|
Support for NS package subscription to ETSI Catalog Manager | SO NFVO needs to subscribe to ETSI Catalog Manager to receive Nsd{x} Notification(s)
|
No |
|
=== | |||||||||||||||
Support for NS Inventory (AAI) Adapter |
| No |
| ||||||||||||
Support for NS AAI APIs (CRUD) |
| No |
| ||||||||||||
Support for Network AAI APIs (CRUD) |
| No |
| ||||||||||||
Support for VNF AAI APIs (CRUD) |
| No |
| ||||||||||||
Support for Vserver AAI APIs (CRUD) |
| No |
| ||||||||||||
Support for Customer AAI APIs (CRUD) |
| ||||||||||||||
Support for NS LCM Database Management Enhancement |
Also, regression testing is necessary for SOL005 NS operations.
|
No |
|
Support for MultiCloud Adapter |
|
No |
|
Support for Create Network to VIM API |
|
No |
|
Support for Delete Network (VL) from VIM API |
|
No |
|
Low | |||||||||||||||
Package and dynamically deploy NS LCM Workflows with business logic | When ONAP SO support Dynamic BPMN, package and deploy NS LCM workflows with business logic as a WAR file.
| No |
| ||||||||||||
Package and deploy default NS LCM workflows with business logic |
| No |
| ||||||||||||
Support for UI and REST interfaces for custom workflow war deployment |
| No | |||||||||||||
Support for NS Resource Infra Management (RIM) Manager |
| No |
| ||||||||||||
Support for OOF-based Granting VNF |
| ||||||||||||||
Support for Software Image Management |
| ||||||||||||||
Support for CNFM Emulator | Provides CNFM Emulator to make connections between SOL003 Adapter and Kubernetes Master to CNF orchestration. | TBD | |||||||||||||
Support for CSIT for SO NFVO and SOL003 Adapter | |||||||||||||||
SOL005 Adapter Operations
...