Page Comparison

In R2, we plan to support the following use cases for Integration/E2E testing (use cases moved from OOF Beijing M1 Release Planning): 

...

1. Support for VNF Scale out, VoLTE, and 5G was moved to R3 due to our dependencies not supporting these use cases in R2. 
2. Additionally, we supported OOF integration with MultiCloud, where using the vCPE workflow (vCPE Homing Use Case), we check for instantaneous capacity availability at a set of cloud-regions with MultiCloud (https://jira.onap.org/browse/OPTFRA-148). 
3. Support for HPA is manifested through the vCPE use case (vCPE Homing Use Case). 

vCPE use case:

Service Instantiation workflows in R1 (from Use Case: Residential Broadband vCPE (Approved))

Image Added

In R1, homing was performed though an emulator that provided the Internal Homing depicted above. In R2, we replace this emulator with the actual Homing Service provided by OOF. 

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

Image Added

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 ?