Page History

TESTING PROGRESS: 95%

Pairwise:

Dependencies: OOF, Multicloud, SO, Policy, AAI

...

 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: 

...

Thursday   

...

 5/

...

31/18

OOF - SO, Fixing some API conformance issues, for example OOF does not support License Homing for Beijing, removed from the homing call https://gerrit.onap.org/r/#/c/48825/, retesting and working through We were able to send a homing request to OOF and receive HPA flavor labels. Solving the last issue from OOF. See 

Tuesday     5/

...

29/

...

18

Fixed  

OOF - SO, We have had multiple working meetings since last week and have made a lot of progress. We got SB01 configured and have been running tests, filing bugs and fixing bugs and retesting.

SO Issues: 

Wednesday     5/23/18

OOF - SO, Fixing some API conformance issues, for example OOF does not support License Homing for Beijing, removed from the homing call https://gerrit.onap.org/r/#/c/48825/, retesting and working through 

Tuesday     5/22/18 

OOF - SO, We have had multiple working meetings since last week and have made a lot of progress. We got SB01 configured and have been running tests, filing bugs and fixing bugs and retesting.

SO Issues: 

Thursday     5/17/18 

 OOF - Policy Done | OOF - AAI Done | OOF - SO, testing started in SB01

Wednesday      5/16/18 

Example policies and modified CSAR's have been created and attached to this page. | OOF - Policy Debug Still in Progress | OOF - AAI Waiting for multicloud fix | OOF - SO, testing started in SB01

Tuesday      5/15/18

OOF -AAI, AAI connectivity resolved | OOF - Policy, Still testing/Troubleshooting with Policy | OOF - SO, exact regression CSAR's acquired, modification started | AAI – Multicloud, A couple issues with data model used have been fixed that blocked AAI

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%

OOF Issues: 

Thursday     5/17/18 

 OOF - Policy Done | OOF - AAI Done | OOF - SO, testing started in SB01

Wednesday      5/16/18 

Example policies and modified CSAR's have been created and attached to this page. | OOF - Policy Debug Still in Progress | OOF - AAI Waiting for multicloud fix | OOF - SO, testing started in SB01

Tuesday      5/15/18

OOF -AAI, AAI connectivity resolved | OOF - Policy, Still testing/Troubleshooting with Policy | OOF - SO, exact regression CSAR's acquired, modification started | AAI – Multicloud, A couple issues with data model used have been fixed that blocked AAI

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 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 
    Example policies: 

    Code Block
    language bash title HPA Policy Example 1
    { "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":"vcpe.vgmux", "flavorProperties":[ { "hpa-feature-attributes":[ { "hpa-attribute-key":"numVirtualCpu", "hpa-attribute-value":"4", "operator":"=" }, { "hpa-attribute-key":"virtualMemSize", "hpa-attribute-value":"8192", "operator":"=", "unit":"MB" } ], "mandatory":"True", "hpa-feature":"basicCapabilities", "architecture":"generic", "hpa-version":"v1" }, { "hpa-feature-attributes":[ { "hpa-attribute-key":"logicalCpuPinningPolicy", "hpa-attribute-value":"dedicated", "operator":"=" } ], "mandatory":"True", "hpa-feature":"cpuPinning", "architecture":"generic", "hpa-version":"v1", } ] } ] } }

    Code Block
    language bash title HPA Policy Example 2
    { "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":"vcpe.vgmux", "flavorProperties":[ { "hpa-feature-attributes":[ { "hpa-attribute-key":"numVirtualCpu", "hpa-attribute-value":"4", "operator":">=" }, { "hpa-attribute-key":"virtualMemSize", "hpa-attribute-value":"8", "operator":"=", "unit":"MB" } ], "mandatory":"True", "hpa-feature":"basicCapabilities", "architecture":"generic", "hpa-version":"v1" } ] } ] } }

    
     This example will change based on flavors in OpenStack/Multicloud in the lab.

  • Create flavors in OpenStack
    • flavors which is used to discover HPA information should named with prefix of "onap." , otherwise there will no HPA information can be extracted by multicloud plugins for OpenStack
    • the number of flavors to be created for ONAP is determined by number of the generic flavors multiplied by the combination of HPA specification.
      • In this example, there are 2 generic flavors:
        • medium: 4 vcpu, 4GB memory, 40GB storage
        • large: 6 vcpu, 8GB memory, 80GB storage
      • In this example, there are 2 set of HPA specification:
        
        • set 1: hw:numa_nodes=2, hw:cpu_policy=dedicated, hw:mem_page_size=2M;
        • set 2: hw:cpu_policy=dedicated, hw:mem_page_size=2M
        Hence the flavors named with prefix of "onap." are:
      • onap.flavor2.medium
        • medium with HPA set 1
      • onap.flavor2.large
        • large  with HPA set 1
      • onap.flavor3.medium
        • medium with HPA set 2
      onap.flavor3.largelarge with HPA set 2
      
  • 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

...

• • • • • =2, hw:cpu_policy=dedicated, hw:mem_page_size=2M;
        • set 2: hw:cpu_policy=dedicated, hw:mem_page_size=2M
      • Hence the flavors named with prefix of "onap." are:
        • onap.flavor2.medium
          • medium with HPA set 1
        • onap.flavor2.large
          • large  with HPA set 1
        • onap.flavor3.medium
          • medium with HPA set 2
        • onap.flavor3.large
          • large with HPA set 2
            
            
  • 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:

Thursday     5/31/18

We were able to send a homing request to OOF and receive HPA flavor labels. SO then processes these correctly. However we need to make it through vCPE Use Case to the portion where we instantiat vGW to verfy. Made it through vCPE Use Case until "PostProcess SDNC Create" where I hit bug: 
2018-06-01 00:32:35,497 | ERROR | tp1609525416-571 | GenericResourceApiProvider | 374 - org.onap.sdnc.northbound.generic-resource-api-provider - 1.3.3 - - | Caught exception executing service logic for tunnelxconn-topology-operation
org.onap.ccsdk.sli.core.sli.SvcLogicException: Invalid index values [0,]

Brian Freeman told me I could solve bug by pulling the latest containers and updating a few config to match SB07. Trying to pull the latest containers has been in progress for three hours. I will retest HPA when containers finish pulling.

Tuesday     5/29/18

Started integration testing by setting up vCPE use case in SB01. Will update wiki with instructions on the additional procedures.

Wednesday      5/16/18 

Example policies and modified CSAR's have been created and attached to this page. On policy side more will need to be created for all vCPE CSARs.

...