Flow diagram
Steps
- SO request OOF for NSI/NSSI selection
- OSDF fetches the optimization policies for the requested NST/NSST
- OSDF request HAS(conductor) for optimization
- HAS fetches the list of NSIs/NSSIs from AAI
- Using the NSI/NSSI id that it fetched from AAI, HAS requests DCAE(Slice Analysis MS) with attributes present in the service profile
- DCAE returns current capacity of the NSIs/NSSIs requested
- Based on the current capacity, HAS run the optimization to choose the suitable NSI/NSSI
- The selected NSI/NSSI is returned to OSDF, which forwards it to SO
Outgoing APIs
AAI api
Already present in the code. No need to change
DCAE api
DCAE api is documented here in this page.
Sample Request API :
curl -X GET -H "authorization: Basic YWFpOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=" -H "x-ecomp-instanceid:AAI" -H 'Accept:application/json' -k https://10.31.4.43:8080/api/v1/current-throughput/
API Definition
Get throughput from DCAE
Interface definition | Description |
Content-Type | application/json |
Operation | GET |
URI | /api/v1/current-throughput |
Request Body
Attribute | Required | Type | Description |
sliceIdentifiers | Y | List<String> | Identifier for the specific type of slices |
current-throughput | Y | String | current throughput value expected from DCAE |
Request Body - Sample
{
"sliceIdentifiers": [
"7e000ddc-7ba1-4fdb-a7ce-8f0a65ab3282",
"cb51e744-bfcf-4188-885a-e3e3c51ed53e"
],
"current-throughput"
}
Response Codes
Code | Description |
200 | Data returned successfully |
400 | Bad Request (Error in request attributes) |
500 | Internal server error |
Response Body
Attribute | Required | Type | Description |
currentThroughputResponse | Y | currentThroughputResponse | Response body containing the current throughput for the requested slices |
currentThroughputResponse - Sample Response
Response Body - Sample
{
"sliceConfigDetails": [{
"sliceIdentifier": "5d9b3293-fa20-4776-bb41-92ba5e384419",
"currentThroughput": 100
},
{
"sliceIdentifier": "e316f4b2-01fa-479a-8522-64fe9c0c2971",
"currentThroughput": 160
}]
}
NOTE: sliceIdentifier – can be SNSSAI/slice-profile-id
Impacted OOF modules
HAS-DATA component
HAS data component fetches the data from AAI and other inventory sources. A new inventory source for DCAE should be added, and it should be used during the NSI/NSSI selection flow (Please refer NST selection which also a similar flow. NST selection uses SDC to get the additional attributes)