...
| Code Block | ||||
|---|---|---|---|---|
| ||||
Assume:
AAI IP:PORT = 10.12.6.233:8443
cloud-owner = CloudOwner
Cloud-region-id = RegionOne
Complex object with physical 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": [
{
"relationship-key": "complex.physical-location-id",
"relationship-value": "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.