You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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

Sequence Diagram :

Capacity based NSI Selection


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. No need to change

DCAE api

DCAE api is documented here in this page.

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.




  • No labels