...
- The scope of work is limited to NS LCM APIs, so Service Orchestrator (SO) won’t deal with CSAR package onboarding to VFC.
- As all the attributes that SOL005 instantiate request expects are not provided from Usecase UI, so scope of this work is limited to such requests.
- No new SO NBI is added for this usecase. SO E2E Service Instance APIs will be reused to support ETSI NFV-SOL 005
SOL 005 API Request and Response ( for reference only. These APIs will be implemented by VF-C / NFV-O)
...
API Mapping table ( SO NBI & ETSI NFV-SOL 005 )
# | SO NBI API | SO NBI Payload | SOL API | SOL 005 Payload | Identified GAPs | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1. | Create NS and Instance NS /onap/so/infra/e2eServiceInstances/{version} |
| /ns_instances | Create NS Payload
|
| ||||||||||||||||||||||||||
2. | Query NS details /onap/so/infra/e2eServiceInstances/{version}/{serviceId}/operations/{operationId} | No Payload | /ns_instances/{nsInstanceId} | No Payload | No Gap identified | ||||||||||||||||||||||||||
3. | Terminate NS /onap/so/infra/e2eServiceInstances/{version}/{serviceId} |
| /ns_instances/{nsInstanceId}/terminate |
| No Gap Identified | ||||||||||||||||||||||||||
4. | InstantiateNS /onap/so/infra/e2eServiceInstances/{version} | Same API for Create and Instantiate | /ns_instances/{nsInstanceId}/instantiate |
| For instantiate NS the following are the data that is missing in SO NBI
|
...