Page History

...

Interface details (data flow)

...

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)

Actions

• Update Existing API for NST selection
• Define Optimization policy models
• Add examples for consuming apis (AAI and SDC)
• OOF internal flows for NST selection

NSI Selection 

Interface details (data flow)

Prerequisite: NSMF gathers all the NSSMF capabilities from the corresponding NSSMFs

Step 1 - 5 is already captured in the previous flow

...

6a. NSI selection request. NSMF requests OOF for a suitable NSI/set of slice profiles

• Data: NST info with its constituent NSSTs, Service profile, NSSMF capabilities, Weightage

7. Get Optimization policies for NSI selection

• Policies for demand (NSI)
• Policies for Constraints (Threshold, etc.,)
• Policies for Optimization

8. Get the candidate NSIs from AAI

• Existing API in AAI
• Request: NST model info (model UUID)
• Response: List of NSI info
• Example:

9. Select suitable NSI or set of slice profiles based on optimization

• HAS run the optimization and selects the best solution
• Detailed flow with OSDF and conductor has to be worked out

6b. NSI selection Response

• Selected NSI/Set of Slice profiles

Actions

• Update to existing NSI selection API. API specifications have to be worked out (Step 6)
• Define Optimization policy models (Step 7)
• Add an example to consumed AAI API (Step 8)
• OOF internal flow for NSI selection and slice profile generation (Step 9)

• From, to, data

Component functionalities

• <Component name>: