Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

TESTING PROGRESS: 95%

Pairwise:

Dependencies: OOF, Multicloud, SO, Policy, AAI

Components

Status

AAI – Multicloud

Working – As reported by Bin Yang            Done - Working

OOF – AAI

Testing In Progress. Connectivity issues with AAI resolved. Basic plans (w/o HPA) are passing. Waiting for Multicloud fix for issue

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-232
. Tested with the bug fix and tested some basic HPA flavors that are working.

OOF  – SO

Testing In Progress – SO - OOF testing started in SB01

OOF  – Policy

Testing Completed – Bugs found, Policy Team working on Fix - Will Retest per Ankit        

Done - Working


OOF  – SO

Done - Working

OOF  – Policy

Done - Working per Ankit     


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

...

Thursday   

...

 5/

...

31/

...

18

We were able to send a homing request to OOF and receive HPA flavor labels. Solving the last issue from OOF. See 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-661

Tuesday     5/29/18

Fixed  

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-573
 - we are able to send homing request and get correct homing request back.

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 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-573

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: 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-637
 
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-636

OOF Issues: 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-239
 
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-241
 
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-239
 
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-232

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

      Code Block
      languagebash
      titleHPA 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":[ 
                           { 
         

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

      Code Block
      languagebash
      titleHPA 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"
            ],
            "policyTypehpa-attribute-key":"hpaPolicynumVirtualCpu",
            "resources						"hpa-attribute-value":"vGMuxInfra4",
            "flavorFeatures":[ 
               { 
                  "flavorLabeloperator":"vcpe.vgmux=",
                  "flavorProperties":[ 
              },
      					 {
            { 
                        "hpa-featureattribute-attributeskey":[ 
      "virtualMemSize",
                              { "hpa-attribute-value":"8192",
                              "hpa-attribute-keyoperator":"numVirtualCpu=",
      						"hpa-attribute-value":"4",
                              "operatorunit":"=MB"
                           },
      					 {
      
                        ],
                        "hpa-attribute-keymandatory":"virtualMemSizeTrue",
                              "hpa-attribute-valuefeature":"8192basicCapabilities",
                        "architecture":"generic",
      				      "operator"hpa-version":"=v1",
                     },
               "unit":"MB"
            { 
                    }
          "hpa-feature-attributes":[ 
                   ],
              { 
               "mandatory":"True",
                        "hpa-featureattribute-key":"basicCapabilitieslogicalCpuPinningPolicy",
                            "architecture":"generic",
      				  "hpa-attribute-versionvalue":"v1dedicated",
                        },
            "operator":"="
               { 
                 }
             "hpa-feature-attributes":[ 
                ],
                 { 
            "mandatory":"True",
                        "hpa-attribute-keyfeature":"logicalCpuPinningPolicycpuPinning",
                        "architecture":"generic",
      				      "hpa-attribute-valueversion":"dedicatedv1",
                              "operator":"="}
                  ]
               }
            ]
          }
      }
      Code Block
      languagebash
      titleHPA Policy Example 2
      { 
           "riskLevel":"1",
         ]"riskType":"SampleRiskType",
         "policyName":"PolicyHPA3",
          "service":"hpaPolicy",
                 "mandatory"guard":"TrueFalse",
         "description":"Must have Huge pages support",
         "templateVersion":"OpenSource.version.1",
         "priority":"1",
           "hpa-featureversion":"cpuPinningCSIT",
                  "content":{ 
            "architectureidentity":"generichpaPolicy_set3",
      				      "hpa-versionpolicyScope":"v1",[ 
               "INTERNATIONAL"
            }],
            "policyType":"hpaPolicy",
            ]"resources":"vGMuxInfra",
            "flavorFeatures":[ 
          }
           { ]
           }
      }
      Code Block
      languagebash
      titleHPA Policy Example 2
      { 
             "riskLevelflavorLabel":"1vcpe.vgmux",
                  "riskTypeflavorProperties":"SampleRiskType",
         "policyName":"PolicyHPA3",
         "service":"hpaPolicy",
         "guard":"False",
         "description":"Must have Huge pages support",
         "templateVersion":"OpenSource.version.1",
         "priority":"1",
         "version":"CSIT",
         "content":{ 
      [ 
                     { 
                        "hpa-feature-attributes":[ 
                     "identity":"hpaPolicy_set3",
            "policyScope":[{ 
                 "INTERNATIONAL"
             ],
            "policyTypehpa-attribute-key":"hpaPolicynumVirtualCpu",
            "resources						"hpa-attribute-value":"vGMuxInfra4",
            "flavorFeatures":[ 
      
                 { 
                  "flavorLabeloperator":"vcpe.vgmux>=",
                  "flavorProperties":[ 
              },
      					 {
            { 
                        "hpa-featureattribute-attributeskey":[ 
      "virtualMemSize",
                             {  "hpa-attribute-value":"8",
                              "hpa-attribute-keyoperator":"numVirtualCpu",
      						"hpa-attribute-value":"4"=",
                              "operatorunit":">=MB"
                           },
      					 {
                              "hpa-attribute-key":"virtualMemSize",
            ],
                        "hpa-attribute-valuemandatory":"8True",
                              "operator"hpa-feature":"=basicCapabilities",
                            "architecture":"generic",
      				  "unithpa-version":"MBv1"
                           }
                        ],
               }
            ]
         "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

...

    • }
      }


       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.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.

...

Code Block
languagexml
{
	"variables": [],
	"info": {
		"name": "SO Pairwise",
		"_postman_id": "2cf34bf0-16d9-e9ad-0948-c0ded70fed44",
		"description": "",
		"schema": "https://schema.getpostman.com/json/collection/v2.0.0/collection.json"
	},
	"item": [
		{
			"name": "SO Create vCPE",
			"request": {
				"url": "http://{{SO Host}}:8080/ecomp/mso/infra/serviceInstances/v5",
				"method": "PUT",
				"header": [
					{
						"key": "Content-Type",
						"value": "application/json",
						"description": ""
					},
					{
						"key": "Authorization",
						"value": "Basic SW5mcmFQb3J0YWxDbGllbnQ6cGFzc3dvcmQxJA==",
						"description": ""
					}
				],
				"body": {
					"mode": "raw",
					"raw": "{\r\n  \"requestDetails\": {\r\n    \"cloudConfiguration\": {\r\n      \"lcpCloudRegionId\": \"RegionOne\",\r\n      \"tenantId\": \"1e097c6713e74fd7ac8e4295e605ee1e\"\r\n    },\r\n    \"modelInfo\": {\r\n      \"modelInvariantId\": \"a3ebfaf2-3dea-43b0-bb8e-566f95735230\",\r\n      \"modelName\": \"vcpesvc_rescust_0412a\",\r\n      \"modelType\": \"service\",\r\n      \"modelVersion\": \"1.0\",\r\n      \"modelVersionId\": \"dc316752-561f-48a3-8354-d873c813735d\"\r\n    },\r\n    \"owningEntity\": {\r\n      \"owningEntityId\": \"520cc603-a3c4-4ec2-9ef4-ca70facd79c0\",\r\n      \"owningEntityName\": \"OE-Demonstration\"\r\n    },\r\n    \"project\": {\r\n      \"projectName\": \"Project-Demonstration\"\r\n    },\r\n    \"requestInfo\": {\r\n      \"instanceName\": \"vcpe_svc_vcpesvc_rescust_0412a_201805102300\",\r\n      \"productFamilyId\": \"a9a77d5a-123e-4ca2-9eb9-0b015d2ee0fb\",\r\n      \"requestorId\": \"vCPE-Robot\",\r\n      \"source\": \"VID\",\r\n      \"suppressRollback\": \"true\"\r\n    },\r\n    \"requestParameters\": {\r\n      \"aLaCarte\": \"false\",\r\n      \"subscriptionServiceType\": \"vCPE\",\r\n      \"userParams\": [\r\n        {\r\n          \"name\": \"BRG_WAN_MAC_Address\",\r\n          \"value\": \"fa:16:3e:c0:34:ef\"\r\n        },\r\n        {\r\n           \"name\": \"Customer_Location\",\r\n           \"value\": {\r\n              \"customerLatitude\": \"32.897480\",\r\n              \"customerLongitude\": \"-97.040443\",\r\n              \"customerName\": \"some_company\"\r\n          }\r\n        }\r\n\r\n      ]\r\n    },\r\n    \"subscriberInfo\": {\r\n      \"globalSubscriberId\": \"SDN-ETHERNET-INTERNET\",\r\n      \"subscriberName\": \"Kaneohe\"\r\n    }\r\n  }\r\n}"
				},
				"description": ""
			},
			"response": []
		},
		{
			"name": "Policy vCPE HPA1",
			"request": {
				"url": "http://{{Policy Host}}/pdp/api/createPolicy",
				"method": "PUT",
				"header": [
					{
						"key": "Content-Type",
						"value": "application/json",
						"description": ""
					},
					{
						"key": "Authorization",
						"value": "Basic dGVzdHBkcDphbHBoYTEyMw==",
						"description": ""
					},
					{
						"key": "cache-control",
						"value": "no-cache",
						"description": ""
					},
					{
						"key": "clientauth",
						"value": "cHl0aG9uOnRlc3Q=",
						"description": ""
					},
					{
						"key": "content-type",
						"value": "application/json",
						"description": ""
					},
					{
						"key": "environment",
						"value": "TEST",
						"description": ""
					}
				],
				"body": {
					"mode": "raw",
					"raw": "{\r\n   \"riskLevel\":\"1\",\r\n   \"riskType\":\"SampleRiskType\",\r\n   \"policyName\":\"PolicyHPA3\",\r\n   \"service\":\"hpaPolicy\",\r\n   \"guard\":\"False\",\r\n   \"description\":\"Must have Huge pages support\",\r\n   \"templateVersion\":\"OpenSource.version.1\",\r\n   \"priority\":\"1\",\r\n   \"version\":\"CSIT\",\r\n   \"content\":{\r\n      \"identity\":\"hpaPolicy_set3\",\r\n      \"policyScope\":[\r\n         \"INTERNATIONAL\"\r\n      ],\r\n      \"policyType\":\"hpaPolicy\",\r\n      \"resources\":\"vGMuxInfra\",\r\n      \"flavorFeatures\":[\r\n         {\r\n            \"flavorLabel\":\"vcpe.vgmux\",\r\n            \"flavorProperties\":[\r\n               {\r\n                  \"hpa-feature-attributes\":[\r\n                     {\r\n                        \"hpa-attribute-key\":\"numVirtualCpu\",\r\n                        \"hpa-attribute-value\":\"4\",\r\n                        \"operator\":\"=\"\r\n                     },\r\n                     {\r\n                        \"hpa-attribute-key\":\"virtualMemSize\",\r\n                        \"hpa-attribute-value\":\"8192\",\r\n                        \"operator\":\"=\",\r\n                        \"unit\":\"MB\"\r\n                     }\r\n                  ],\r\n                  \"mandatory\":\"True\",\r\n                  \"hpa-feature\":\"basicCapabilities\",\r\n                  \"architecture\":\"generic\",\r\n                  \"hpa-version\":\"v1\"\r\n               },\r\n               {\r\n                  \"hpa-feature-attributes\":[\r\n                     {\r\n                        \"hpa-attribute-key\":\"logicalCpuPinningPolicy\",\r\n                        \"hpa-attribute-value\":\"dedicated\",\r\n                        \"operator\":\"=\"\r\n                     }\r\n                  ],\r\n                  \"mandatory\":\"True\",\r\n                  \"hpa-feature\":\"cpuPinning\",\r\n                  \"architecture\":\"generic\",\r\n                  \"hpa-version\":\"v1\",\r\n               }\r\n            ]\r\n         }\r\n      ]\r\n   }\r\n}"
				},
				"description": ""
			},
			"response": []
		},
		{
			"name": "Policy vCPE HPA2",
			"request": {
				"url": "http://{{Policy Host}}/pdp/api/createPolicy",
				"method": "PUT",
				"header": [
					{
						"key": "Content-Type",
						"value": "application/json",
						"description": ""
					},
					{
						"key": "Authorization",
						"value": "Basic dGVzdHBkcDphbHBoYTEyMw==",
						"description": ""
					},
					{
						"key": "cache-control",
						"value": "no-cachecache",
						"description": ""
					},
					{
						"key": "clientauth",
						"value": "cHl0aG9uOnRlc3Q=",
						"description": ""
					},
					{
						"key": "clientauthcontent-type",
						"value": "cHl0aG9uOnRlc3Q=application/json",
						"description": ""
					},
					{
						"key": "content-typeenvironment",
						"value": "application/jsonTEST",
						"description": ""
					}
				],
					"body": {
						"keymode": "environmentraw",
						"value": "TEST",
						"description": ""
					}
				],
				"body": {
					"mode": "raw",
					"raw": "{"raw": "{\r\n   \"riskLevel\":\"1\",\r\n   \"riskType\":\"SampleRiskType\",\r\n   \"policyName\":\"PolicyHPA3\",\r\n   \"service\":\"hpaPolicy\",\r\n   \"guard\":\"False\",\r\n   \"description\":\"Must have Huge pages support\",\r\n   \"riskLeveltemplateVersion\":\"OpenSource.version.1\",\r\n   \"riskTypepriority\":\"SampleRiskType1\",\r\n   \"policyNameversion\":\"PolicyHPA3CSIT\",\r\n   \"servicecontent\":{\r\n      \"identity\":\"hpaPolicy_set3\",\r\n      \"guardpolicyScope\":[\r\"False\"n         \"INTERNATIONAL\"\r\n      ],\r\n      \"descriptionpolicyType\":\"Must have Huge pages supporthpaPolicy\",\r\n      \"templateVersionresources\":\"OpenSource.version.1vGMuxInfra\",\r\n      \"priorityflavorFeatures\":[\"1\",r\n         {\r\n            \"versionflavorLabel\":\"CSITvcpe.vgmux\",\r\n            \"contentflavorProperties\":{[\r\n      \"identity\":\"hpaPolicy_set3\",\r\n         {\r\n                  \"policyScopehpa-feature-attributes\":[\r\n                     {\"INTERNATIONAL\"\r\n           ],\r\n       \"policyType\":\"hpaPolicy\",\r\n      \"resourceshpa-attribute-key\":\"vGMuxInfranumVirtualCpu\",\r\n      \"flavorFeatures\":[\r\n         {\r\n            \"flavorLabelhpa-attribute-value\":\"vcpe.vgmux4\",\r\n            \"flavorProperties\":[\r\n               {\"operator\":\">=\"\r\n                     \"hpa-feature-attributes\":[\},\r\n                     {\r\n                        \"hpa-attribute-key\":\"numVirtualCpuvirtualMemSize\",\r\n                        \"hpa-attribute-value\":\"48\",\r\n                        \"operator\":\">=\",\r\n                        },\"unit\":\"MB\"\r\n                     {}\r\n                  ],\r\n                  \"hpa-attribute-keymandatory\":\"virtualMemSizeTrue\",\r\n                        \"hpa-attribute-valuefeature\":\"8basicCapabilities\",\r\n                        \"operatorarchitecture\":\"=generic\",\r\n                        \"unithpa-version\":\"MBv1\"\r\n                     }\r\n            ]\r\n      ],   }\r\n      ]\r\n   }\r\n}"
				},
				"description": ""
			},
			"response": []
		}
	]
}


Associate a Complex Object with a cloud region

Code Block
titleAssociate Complex with Cloud Region
collapsetrue
Assume:
	AAI IP:PORT      \"mandatory\":\"True\",\r\n= 10.12.6.233:8443
    cloud-owner = CloudOwner
    Cloud-region-id = RegionOne
	Complex  object with physical  \"hpa-feature\":\"basicCapabilities\",\r\n                  \"architecture\":\"generic\",\r\n                  \"hpa-version\":\"v1\"\r\n               }\r\n  location id: clli1


curl -X PUT \
  https://10.12.6.233:8443/aai/v11/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/relationship-list/relationship \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic QUFJOkFBSQ==' \
  -H 'Cache-Control: no-cache' \
  -H 'Content-Type: application/json' \
  -H 'Postman-Token: 64960a1c-be11-cb66-ffb5-f6d0298b0ac4' \
  -H 'Real-Time: true' \
  -H 'X-FromAppId: jimmy-postman' \
  -H 'X-TransactionId: 9999' \
  -d '{
"related-to": "complex",
"related-link": "/aai/v11/cloud-infrastructure/complexes/complex/clli1",
"relationship-data": [
{
          ]\r\n"relationship-key": "complex.physical-location-id",
        "relationship-value": }\r\n      ]\r\n   }\r\n}"
				},
				"description": ""
			},
			"response": []
		}
	]
}"clli1"
}
]
}'



Another way to populate the default cloud region with complex is the robot script:

    Attach to robot VM, execute following script:

       $ /opt/demo.sh init_customer

    The default cloud-region (CloudOwner,RegionOne) and the default complex (clli1) and the association between them will be populated .

    Caveat:  The cloud-region populated by this script is not conform to the cloud region expected by multicloud. So it is not possible to discover/populate HPA information under this default cloud region.