MultiCloud component

Owned by Bin Yang
Last updated: May 31, 2018
2 min read

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



Cloud Region Registration
$ 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

           VES endpoint: http://172.30.3.55:8081/eventListener/v5 , user/passwd: admin/admin

           DMaaP IP: 172.30.3.70

           vimid: CloudOwner_RegionOne

           VM names: sample_vm_0 and sample_vm_1

           Tenant: sampletenant



VESagent provision sample 1: monitor specific VMs under specific tenant



sample_vesagent_2vms
{"vesagent_config":{"backlogs":[{"source":"sample_vm_0 ","domain":"fault","type":"vm","tenant":"sampletenant"},{"source":"sample_vm_1","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"}}}



VESagent provision sample 2: monitor all VMs under specific tenant (by not specify any source or server_id for a backlog)



sample_vesagent_all_vms
{"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

provisioning vesagent





Query the provision of MultiCloud VESagent

Query VESagent





Delete the provision of MultiCloud VESagent

Delete provision of VESagent for a VIM





Triggering the fault event:

          1, Subscribe DMaaP events:

                         while :; do curl -H “Content-Type:text/plain” -X GET http://172.30.3.70:3904/events/unauthenticated.SEC_FAULT_OUTPUT/group19/C1?timeout=50000; echo; done;

          2, Shut off the sample_vm_0 or sample_vm_1 or both

          3, observe the dumped event from subscription in step 1

subscription output





Triggering the fault cleared event:



          1, Subscribe DMaaP events:

                         while :; do curl -H “Content-Type:text/plain” -X GET http://172.30.3.70:3904/events/unauthenticated.SEC_FAULT_OUTPUT/group19/C1?timeout=50000; echo; done;

          2, Start the the sample_vm_0 or sample_vm_1 or both

          3, observe the dumped event from subscription in step 1

subscription output