Capacity based NSI/NSSI Selection - OOF changes

NOTE : This documentation is still in progress and not the final version.

Sequence Diagram :

Steps : 

1. SO request OOF for NSI/NSSI selection
2. OSDF fetches the optimization policies for the requested NST/NSST
3. OSDF request HAS(conductor) for optimization
4. HAS fetches the list of NSIs/NSSIs from AAI
5. Using the NSI/NSSI id that it fetched from AAI, HAS requests DCAE(Slice Analysis MS) with attributes present in the service profile
6. DCAE returns current capacity of the NSIs/NSSIs requested
7. Based on the current capacity, HAS run the optimization to choose the suitable NSI/NSSI
8. The selected NSI/NSSI is returned to OSDF, which forwards it to SO

Outgoing APIs

AAI API

Already present in the code. The below pages contain the details regd. the AAI APIs used.

NSI Selection

NSSI Selection

DCAE API

DCAE API is documented in this page.

Sample Request :

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/slices-config/

Sample Response :

{ 

    "sliceConfigDetails": [{ 

        "sliceIdentifier": "5d9b3293-fa20-4776-bb41-92ba5e384419", 

        "aggregatedConfig": { 

            "dLThptPerSlice":27, 

            "uLThptPerSlice":30, 

            "maxNumberOfConns":300 

        } 

    }, 

    { 

        "sliceIdentifier": "e316f4b2-01fa-479a-8522-64fe9c0c2971", 

        "aggregatedConfig": { 

            "dLThptPerSlice":40, 

            "uLThptPerSlice":25, 

            "maxNumberOfConns":400 

        } 

    }] 

} 

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.