Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for dynamically adding/removing hosts #3

Open
ke4qqq opened this issue Nov 30, 2011 · 2 comments
Open

Add support for dynamically adding/removing hosts #3

ke4qqq opened this issue Nov 30, 2011 · 2 comments
Milestone

Comments

@ke4qqq
Copy link

ke4qqq commented Nov 30, 2011

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.

@ToddHebert
Copy link

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)

@ke4qqq
Copy link
Author

ke4qqq commented Jan 28, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants