Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Route optimizer receives the service route request from SDNC with the source and destination interface ids.
  2. The controllers of both the points are found using the AAI queries.
  3. Then optimizer queries AAI to fetch all the possible Controllers in the inventory to send it to minizinc. It fetches all the inter-domain links from the inventory and filters it based on the "rate" mentioned in the request and the operational status "up".
  4. Since minizinc expects the data in a certain way, optimizer wil encode all the data retrieved using the sckit module in python and send it to minizinc.
  5. The pymzn module is used to interface python with the minizinc language.
  6. Once minizinc chooses the optimized path, the optimizer will again decode the data and find the chosen links from the source to the destination.
  7. The optimizer then would fetch the interface details from the link and form a proper service route list that would be sent back to SDNC along with the list of logical links.
  8. SDNC in turn will fetch the end points from the service routes list object from the response and create as many domain services as present in the service route list.
  9. The logical links in the response will be used to form the relationship with the access service which will be done by SDNC.
  10. For the above example if a route has to be found between the "id20" of Controller1 "id21" of Controller5 following request will be sent to OOF by SDNC defined above.
  11. After running the algorithm OOF wil return the following response defined above.

...