HypervisorMonitoringPlugin
Revision as of 20:32, 8 October 2013 by SandyWalsh (talk | contribs) (Created page with "=== Periodic Tasks in compute.manager === * update_available_resource() - yes :* potentially also call with resource_tracker information that includes requested resources (not...")
Periodic Tasks in compute.manager
- update_available_resource() - yes
- potentially also call with resource_tracker information that includes requested resources (not just what hypervisor is reporting)
- actually called in resource_tracker.update_available_resource()
- _cleanup_running_deleted_instances - Should emit notification
- _run_image_cache_manager_pass - Should emit notification
- _run_pending_deletes - Should emit notification
- _check_instance_build_time - Should emit notification
- _heal_instance_info_cache
- _poll_rebooting_instances - Might emit notification on anomolies
- _poll_rescued_instances - Might emit notification on anomolies
- _poll_unconfirmed_resizes - Might emit notification on anomolies
- _poll_shelved_instances
- _instance_usage_audit - maybe, but unlikely
- _poll_bandwidth_usage - yes
- _poll_volume_usage - yes
- _sync_power_states - calls virt.get_info() which has mem/max_mem info ... dunno?
- _reclaim_queued_deletes
What to do with measurements?
- Send samples to Ceilometer via UDP
- Emit over/under alerts via notifications.
Configuration / Restarts
- How to configure plugins?
- How to update configurations without restarting compute node?
