...
Until Casablanca release, the communication between SO & VF-C is based on ONAP APIs. In Dublin, this interface will be aligned to SOL 005 and the usecase will be designed in such a way that, any SOL 005 Compliant NFV-O can interact with SO, in addition to VF-C.
Resource commitment :
Verizon : Bharath Thiruveedula Prateek Gupta udhaya chandran Sirisha Gopigiri
Usecase Lead :
Verizon : Bharath Thiruveedula
TSC Contact :
Verizon : Viswanath Kumar Skand Priya
Participating ONAP Projects :
Implementation : SO, VF-C
Functionality enablement / support : UUI, AAI/ESR
ETSI NFV-SOL 005 Introduction
...
Till Casablanca release, SO supports NS LCM API and scaling of NS. We are not going to add any new APIs in this release. But we will modify existing NS LCM APIs alone to make compatible with SOL 005.
API Action | Method | URI | Description |
---|---|---|---|
Create NS | POST | /ns_instances | To create a Network Service |
Instantiate NS | POST | /ns_instances/{nsInstanceId}/instantiate | To instantiate Network service |
Get NS Details | GET | /ns_instances/{nsInstanceId} | To query the status of the Network Service |
Terminate NS | POST | /ns_instances/{nsInstanceId}/terminate | To Delete Network Service Instance |
Sequence Diagram of the flow:
...
As ESR one of subcomponent of AAI, all ESR entities will be pushed to AAI graph database.
Step - 3 Send NS request from UUI
...
along with orchestrator details:
In Usecase UI, two new dropdowns will be introduced.
- For selecting SOL 005 APIs or follow the existing APIs in VF-C
- To select orchestrator which is populated by querying AAI
Along with the above details, UUI will send E2E service instance request will be sent request to SO.
Step - 4 VF-C/SOL 005 Adapter fetch orchestrator details from AAI:
VF-C adapter will fetch orchestrator details from AAI based on the details provided by UUI.
Saving of orchestrator details in nfvo mapping table in so request db correspond to each instance/job.
Step - 5 VF-C/SOL 005 Adapter send the requests to NFVO:Based on the SOL 005 flag that received from SO, VF-C adapter will either use new SOL005 API call or use the default VFC apis which are not SOL005.
The adapter will fetch the orchestrator details from AAI and call corresponding SOL 005 APIs
Frequently Asked Questions :
...
- 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)
What | CreateNS | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Path | POST {apiRoot}/nslcm/v1/ns_instances | |||||||||||||
When | While creating NS for Sol005 NFVO | |||||||||||||
Request Model |
| |||||||||||||
Response Model |
| |||||||||||||
Callers | OSS/BSS or SO Sol005 Adapter |
What | InstantiateNs | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Path | POST {apiRoot}/nslcm/v1/ns_instances/{nsInstanceId}/instantiate | |||||||||||||
When | Calling from SO Sol005/VFC Adapter | |||||||||||||
Request Model |
| |||||||||||||
Response Model | No Response. | |||||||||||||
Callers | OSS/BSS, SO Sol005 Adapter |
What | Find the details of created NS | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Path | GET {apiRoot}/nslcm/v1/ns_instances/{nsInstanceId} | |||||||||||||
When | Calling from SO Sol005/VFC Adapter | |||||||||||||
Request Model | NA | |||||||||||||
Response Model |
| |||||||||||||
Callers | OSS/BSS, SO Sol005 Adapter |
What | Terminate already created NS | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Path | POST {apiRoot}/nslcm/v1/ns_instances/{nsInstanceId}/terminate | |||||||||||||
When | Calling from SO Sol005/VFC Adapter | |||||||||||||
Request Model |
| |||||||||||||
Response Model | No Response | |||||||||||||
Callers | OSS/BSS, SO Sol005 Adapter |
GAP Analysis SO E2E Service Instance NBI Vs SOL 005 API.
1. Parameter Parameter Analysis for InstantiateNS
Parameter | SO NBI Not Present(NP)/Present(P) | Mandatory(M) /Optional(O) | Significance |
---|---|---|---|
nsFlavourId | NP | M | Identifier of the NS deployment flavour to be instantiated |
sapData | NP | O | Create data concerning the SAPs of this NS |
addpnfData | NP | O | Information on the PNF(s) that are part of this NS. |
vnfInstanceData | NP | O | Specify an existing VNF instance to be used in the NS. If needed, the VNF Profile to be used for this VNF instance is also provided. |
nestedNsInstanceId | NP | O | Specify an existing NS instance to be used as a nested NS within the NS. |
localizationLanguage Structure { "vnfProfileId":"", "locationConstraints":{ "countryCode":"", "civicAddressElement":{ "caType":1, "caValue":"" } } } | Partially Provided. Only vnfProfileId is provided. More details are in following rows | O | Defines the location constraints for the VNF to be instantiated as part of the NS instantiation. An example can be a constraint for the VNF to be in a specific geographic location. |
localizationLanguage.vnfProfileId | P | M | |
localizationLanguage.locationConstraints | P | O | |
localizationLanguage.locationConstraints.countryCode | NP | M | |
localizationLanguage.locationConstraints.civicAddressElement | NP | M | |
additionalParamsForNs | P "requestInputs" Note: Present under service.parameters.requestInputs | O | Allows the OSS/BSS to provide additional parameter(s) at the NS level (as opposed to the VNF level, which is covered in additionalParamsForVnf). |
additionalParamsForVnf | P requestInputs Note: Present under service.parameters.resources.requestInputs | O | Allows the OSS/BSS to provide additional parameter(s) per VNF instance (as opposed to the NS level, which is covered in additionalParamsForNs). This is for VNFs that are to be created by the NFVO as part of the NS instantiation and not for existing VNF that are referenced for reuse. |
startTime | NP | O | Timestamp indicating the earliest time to instantiate the NS. |
nsInstantiationLevelId | NP | O | Identifies one of the NS instantiation levels declared in the DF applicable to this NS instance. If not present, the default NS instantiation level as declared in the NSD shall be used. |
additionalAffinityOrAntiAffiniityRule | NP | O | Specifies additional affinity or anti-affinity constraint for the VNF instances to be instantiated as part of the NS instantiation. Shall not conflict with rules already specified in the NSD. |
2. Parameter Parameter Analysis for createNS
Parameter | SO NBI Not Present(NP) /Present(P) | Mandatory(M) /Optional(O) | Significance |
---|---|---|---|
nsdId | P (serviceUuid) | M | Identifier of the NSD that defines the NS instance to be created. |
nsName | P (name) | M | Human-readable name of the NS instance to be created |
nsDescription | P (description) | M | Human-readable description of the NS instance to be created. |
3. Parameter Parameter Analysis for terminateNS
Parameter | SO NBI Not Present(NP) /Present(P) | Mandatory(M) /Optional(O) | Significance |
---|---|---|---|
terminationTime | NP | O | Timestamp indicating the end time of the NS, i.e. the NS will be terminated automatically at this timestamp. Cardinality "0" indicates the NS termination takes place immediately. |
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
|
Status of the Usecase as of 25 March 2019:
- AAI changes pushed to gerrit: https://gerrit.onap.org/r/#/c/82892/
- ESR Changes both backend and frontend pushed to gerrit: https://gerrit.onap.org/r/#/c/82935/ and https://gerrit.onap.org/r/#/c/82948/
- UsecaseUI changes for backend got merged: https://gerrit.onap.org/r/#/c/83002/ and https://gerrit.onap.org/r/#/c/82925/
- UUI frontend changes pushed to gerrit: https://gerrit.onap.org/r/#/c/82926/
- Change in the plan:
- VFC in Dublin release supports both SOL 005 APIs and non SOL 005 APIs. maopeng zhang Yan Yang
- So Service Orchestrator(SO)'s VFC adapter will now talk in both SOL 005 and non SOL 005(old code) way. Seshu Kumar Mudiganti
Status of the Usecase as of 3rd May 2019:
Component | Subcomponent | Gerrit Link | Status | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
AAI | Schema-service | https://gerrit.onap.org/r/#/c/82892/ |
| ||||||||
ESR | Server | https://gerrit.onap.org/r/#/c/82935/ |
| ||||||||
ESR | GUI | https://gerrit.onap.org/r/#/c/82948/ |
| ||||||||
UUI | GUI | https://gerrit.onap.org/r/#/c/82926/ |
| ||||||||
UUI | Server |
| |||||||||
SO | MSO-requestsdb-adapter | https://gerrit.onap.org/r/#/c/82893/ |
| ||||||||
SO | VFC-Adapter |
|