...
Attribute | Required? | Cardinality | Content | Values | Description |
---|---|---|---|---|---|
UUID | Y | 1 | UUID/String | UUID of NST | |
invariantUUID | Y | 1 | UUID/String | Invariant UUID |
RequestInfo Object
Attribute | Required? | Cardinality | Content | Values | Description |
---|---|---|---|---|---|
transactionId | Y | 1 | UUID/String | A unique ID to track an ONAP transaction. | |
requestId | Y | 1 | UUID/String | A unique ID to track multiple requests associated with a transaction. | |
callbackUrl | Y | 1 | URL | The end point of a callback service where recommendations are posted. | |
callbackHeader | Y | 1 | JSON blob | The header information a client expecting in a async callback. | |
sourceId | Y | 1 | String | The unique ID of a client making an optimization call. | |
numSolutions | Y | 1 | Integer | Expected number of solutions. numSolution can also be specified using an optimization query policies, where the default configured value is 1. The value from a request gets higher precedence over the value defined in a policy. | |
timeout | N | 1 | Integer | A tolerance window (in secs) for expecting solutions. Default is 600 secs. | |
addtnlArgs | N | 1 | JSON BLOB | Any additional parameters that have to be considered for NSI selection |
2.3. Synchronous Response Body
...
Attribute | Required? | Cardinality | Content | Values | Description |
---|---|---|---|---|---|
invariantUUID | Y | 1 | UUID/String | Invariant UUID | |
UUID | Y | 1 | UUID/String | UUID of NSI | |
NSIName | Y | 1 | String | Name of NSI | |
NSIId | Y | 1 | String | Id of NSI | |
matchLevel | Y | 1 | JSON BLOB | Details of match of requirements in service profile, and recommendation rank (future enhancement, based on telemetry, capacity, etc.) |
newNSISolution Object
Attribute | Required? | Cardinality | Content | Values | Description |
---|
SliceProfileList | Y | 1 |
NSSIList
Y
..N |
List of NSSISolution objects
JSON BLOB | A JSON object containing slice profile parameters. The contents are based on 3GPP TS 23.541 Release 16 contents, and will be in the form of attribute value pairs. Assumption: Slice profile contains sub-net type. If not, this should also be included. | ||||
|
|
|
|
| |
matchLevel | Y | 1 | JSON BLOB | Details of match of requirements in service profile, and recommendation rank (future enhancement, based on telemetry, capacity, etc.) |
NSTResponseInfo Object
resourceDetails | N |
Attribute
Required?
Cardinality
Content
Values
Description
UUID
1 |
UUID/String
UUID of NST
JSON BLOB | Details of resources for newNSISolutions |
NSSISolution Object
|
|
|
|
|
|
---|---|---|---|---|---|
|
|
|
|
| |
NSTResponseInfo Object
|
|
|
|
|
|
---|---|---|---|---|---|
|
|
|
|
| |
NSSI Object
|
|
|
|
|
|
---|---|---|---|---|---|
|
|
|
|
| |
3. Select NSSI API
Interface Definition | Description |
---|---|
Content-Type | application/json |
Operation Type | POST |
URI | https://{host}:{port}/api/oof/v1/selection/nssi |
...