Page History

...

• 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: 

    Code Block
    language bash
    { "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 Use modified CSARs flavorLabel attributes to match the ones created in policy - See below 'HPA Updated CSAR's' section.
  • 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: 

HPA Updated CSAR's

csars_20180516_HPA.zip

The above CSAR's are copies of the ones Kang is using for vCPE Regression Integration with one minor change.

Each CSAR has heat Environment File update to vcpe_flavor_name as follows:

HPA Code uses the vcpe_flavor_name to match HPA flavors to the correct policy and service.