NST Selection

Interface details (data flow)

1) Select NST request comes from SO to OOF. The request will contain the service profile

2) OOF accepts the request & sends a synchronous response to SO

3) OOF Calls Policy to fetch the policies needed for NST selection

4) Policy returns the relevant policies to OOF

5) OOF calls AAI to fetch only the NSTs information. 

6) AAI returns all the NST's metadata in the response. 

GET  /aai/v19/service-design-and-creation/models/?role=NST&depth=2

From the metadata, we can get the model name and model version

7) For every NST, OOF will call SDC to download the corresponding CSAR artifact (The URL to download the CSAR will be formed by the metadata (model name & model version) info fetched from AAI)

GET /sdc/v1/catalog/services/{serviceModelName}/{serviceVersion}/artifacts/{artifactName}

service version is the model version (received from AAI)

artifact name is service-<model-name>-csar.csar

8) SDC returns the CSAR for the request NST model

9) OOF processes every CSAR to find the best suitable template and returns an asynchronous response to SO

In the CSAR Definitions/service-<model-name>-template-interface.yml template is the one which has to be compared with the service profile

Component functionalities

• <Component name>:

Allocate NSI (WIP)

Interface details (data flow)

• From, to, data

Component functionalities

• <Component name>: