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

Compare with Current View Page History

« Previous Version 3 Next »

Pairwise:

Dependencies: OOF, Multicloud, SO, Policy, AAI

Components

Status

AAI – Multicloud

Working – As reported by Bin Yang            

OOF – AAI

Testing In Progress – Bug found with AAI Cert., Patch Pushed. Will be retested ASAP

OOF  – SO

Testing Setup – Will be last component to test. Blocked by Pairwise between other components, Test Data setup

OOF  – Policy

Testing In Progress – Will be completed Today                    


We are making good progress on pairwise testing. HPA is unique in that it relies on a multitude of projects and OOF is new and untested. Most of HPA work is gated by OOF, but we are doing our best to help facilitate OOF testing.


Updates: 

Integration:

vCPE Regression (ensure HPA changes do not break vCPE)
vCPE + HPA
  • Gated by vCPE Regression, If vCPE doesn’t work in regression it won’t work with HPA
  • The work to test HPA over vCPE regression is only + 10%
vCPE + HPA Integration Test Plan
  • Setup vCPE the same as regression; up to Service Instantiation
  • Before vCPE Service Instantiation
    • Create HPA policies – An example policy: Config_OOF_PolicyHPA3.2.json
      is attached, though this will change based on flavors in OpenStack/Multicloud in the lab
    • Create flavors in OpenStack
    • Modify CSARs flavorLabel attributes to match the ones created in policy
    • Distribute CSARs to SO
  • At vCPE Service Instantiation
    • Send updated REST service instantiation request to SO that includes user param: Customer_Location
  • Continue the same as vCPE Regression and confirm all is well

Updates: 
  • No labels