HPA Beijing Testing

Pairwise:

Dependencies: OOF, Multicloud, SO, Policy, AAI

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: 

Tuesday 5/15/18: 

Monday   5/14/18: OOF - Policy, Bugs Found in Final Tests, Policy Team working on fixes per Ankit | OOF - AAI Needed further data populated by Multicloud in AAI - In Progress |  OOF - SO, Testing Setup but blocked by other parts | AAI - Multicloud Working

Friday      5/11/18: OOF -AAI, Bugs found, Fixed and Retested | OOF - SO, Testing Setup but blocked by other parts | OOF - Policy, Testing In Progress - Will be completed Today | AAI - Multicloud, Working

Integration:

vCPE Regression (ensure HPA changes do not break vCPE)

• Kang is working through this

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 – See wiki page Policy OOF HPA 
    An example policy: 

    {  
       "riskLevel":"1",
       "riskType":"SampleRiskType",
       "policyName":"PolicyHPA3",
       "service":"hpaPolicy",
       "guard":"False",
       "description":"Must have Huge pages support",
       "templateVersion":"OpenSource.version.1",
       "priority":"1",
       "version":"CSIT",
       "content":{  
          "identity":"hpaPolicy_set3",
          "policyScope":[  
             "INTERNATIONAL"
          ],
          "policyType":"hpaPolicy",
          "resources":"vGMuxInfra",
          "flavorFeatures":[  
             {  
                "flavorLabel":"flavor3",
                "flavorProperties":[  
                   {  
                      "score":"7",
                      "featureAttributes":[  
                         {  
                            "attribute":"memoryPageSize",
                            "operator":"="
                         }
                      ],
                      "mandatory":"True",
                      "hpaFeature":"hugePages",
                      "architecture":"generic"
                   },
                   {  
                      "score":"5",
                      "featureAttributes":[  
                         {  
                            "attribute":"logicalCpuThreadPinningPolicy",
                            "value":"prefer",
                            "operator":"="
                         },
                         {  
                            "attribute":"logicalCpuPinningPolicy",
                            "value":"dedicated",
                            "operator":"="
                         }
                      ],
                      "mandatory":"True",
                      "hpaFeature":"cpuPinning",
                      "architecture":"generic"
                   }
                ]
             }
          ]
       }
    }

    
     This example 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: