Versions Compared

Old Version 3

changes.mady.by.user Shankaranarayanan Puzhavakath Narayanan

Saved on

compared with

New Version 4

changes.mady.by.user Shankaranarayanan Puzhavakath Narayanan

Saved on

Key

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

...

Generic Homing workflow in R2 (from OOF Beijing M1 Release Planning) 

Note: 

  1. SDNC was moved out the scope for R2 for the instance capacity checks. However, the plugin that exercises this capacity check with SDNC exists in the repo, but is not exercised. 
  2. Similarly, Reservations (with MultiCloud and SDNC) were moved out of scope from R2, and into R3 due to lack of resources. 

Gaps

  • Customer location: Ideally, the PNF (BRG) location should be used, but based on Kang Xi's recommendation for R2 (in R1, customer location was hardcoded in homing emulator), we have this come as a part of the order parameters from SO. 
  • vGMUX Service Instance availability in A&AI. Our implementation uses v11 API, but how is this information populated in AAI ?
  • Testing HPA: vG is the only possible candidate, since that is the VNF that is spun up in this workflow (vgMuxInfra already exists, and we pick an existing instance as a part of the homing solution). Are there other relevant VNFs ?