Caveat: This VESagent These practice applies to multicloud-windriver only right now.
...
Cloud Region Registry (Manually)
By default ESR will trigger this registry process, but in case ESR failed to do so or the previous registration is incomplete for some reasons, users could trigger the registration manually
Code Block | ||||
---|---|---|---|---|
| ||||
$ export MC_EP=http://{{multicloud-windriver IP}}:9005/api/multicloud-titanium_cloud/v0/{{vimid}}
e.g. $ export MC_EP=http://172.30.3.37:9005/api/multicloud-titanium_cloud/v0/CloudOwner_RegionOne
$ curl -v -s -H "Content-Type: application/json" -X POST $MC_EP/registry
|
...
VESagent provision for a Cloud Region
Assuming:
IP to access multiCloud-windriver: 172.30.3.37
...
Code Block | ||||
---|---|---|---|---|
| ||||
{"vesagent_config":{"backlogs":[ {"domain":"fault","type":"vm","tenant":"sampletenant"}],"poll_interval_default":10,"ves_subscription":{"username":"admin","password":"admin","endpoint":"http://172.30.3.55:8081/eventListener/v5"}}} |
Provisioning the MultiCloud VESagent
Code Block | ||||
---|---|---|---|---|
| ||||
$ export MC_EP=http://{{multicloud-windriver IP}}:9005/api/multicloud-titanium_cloud/v0/{{vimid}} e.g. $ export MC_EP=http://172.30.3.37:9005/api/multicloud-titanium_cloud/v0/CloudOwner_RegionOne $ curl -v -s -H "Content-Type: application/json" -d sample@sample_vesagent_2vms -X POST $MC_EP/vesagent |
...