You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So - after getting the free unicorn that's included with every CloudStack download - it would be awesome to have the 'Add a CloudStack' cloud do the following on addition:
*listVirtualMachines
And then compare that with the machines already being monitored
For those machines that aren't monitored - add them to Zenoss monitoring
For those machines that are powered off - they should be Discovered, but put in maintenance
For those machines that are powered on - they should be Discovered in production.
An an ongoing basis - there should be a event command that does the following:
If a machine is added (and zenoss discovers that via the event log) - that should trigger Zenoss adding the virtual machine
If a machine is shutdown (and zenoss discovers that via the event log) - that should trigger Zenoss placing the machine in maintenance
If a machine is destroyed (and zenoss discovers that via the event log) - that should trigger Zenoss placing the machine in decommissioned.
The text was updated successfully, but these errors were encountered:
This is a fantastic idea.. but won't work to well when you have 40 VM's with the exact same IP address in the each customer's separate guest subnet (10.1.1.0/24 by default)
indeed - didn't think about that - was honestly thinking private cloud usage - but same issue would apply. Maybe the NaaS stuff in acton solves that. Otherwise, we'd likely need a collector for each account to do that well.
So - after getting the free unicorn that's included with every CloudStack download - it would be awesome to have the 'Add a CloudStack' cloud do the following on addition:
*listVirtualMachines
And then compare that with the machines already being monitored
For those machines that aren't monitored - add them to Zenoss monitoring
For those machines that are powered off - they should be Discovered, but put in maintenance
For those machines that are powered on - they should be Discovered in production.
An an ongoing basis - there should be a event command that does the following:
If a machine is added (and zenoss discovers that via the event log) - that should trigger Zenoss adding the virtual machine
If a machine is shutdown (and zenoss discovers that via the event log) - that should trigger Zenoss placing the machine in maintenance
If a machine is destroyed (and zenoss discovers that via the event log) - that should trigger Zenoss placing the machine in decommissioned.
The text was updated successfully, but these errors were encountered: