IASBU, AS (DCom) and Zenoss created this POC to show how CIAC and Zenoss integrate and the value of the integration. This is the phase 1 only, which is the integration between CPO and Zenoss.
The following picture shows the sequence of events in this POC:
- Zenoss discovers existing infrastrucure and creates the dependency graphs for the system being monitored.
- A tenant user requests a VM through CCP UI. Organization ID is being used as Tenant ID in this POC.
- Once the request is submitted, CPO executes the automation flows to provision the VM
- As part of the provisioning process, after VM is successfully provisioned, CPO retrieves the unique VM ID from vCenter and sends the VM ID along with Tenant ID and VM Name to Zenoss.
- Zenoss also discovers the changes from the infrastructure.
- A fault is introduced in one of the blade.
- Zenoss is able to detect the fault and refect the problem in the dependency graph. The graph is able to show the affected blade as well as the tenant being impacted which was made possible becasue of the mapping sent from CPO at step 4.
The attached zip file (CIAC-Zenoss Demo.zip) contains the TAP (Zenoss Integration.tap) that makes the SSH call to Zenoss server to invoke a script, as well as the script "testcall.sh.txt" that makes the Zenoss API call.
