Generic host state for Scheduler
This blueprint aims to address two key issues. First, currently, the only source of information for host state is a compute node; nonetheless, it is important for extending scheduling capability, if the scheduler can also use information collected from other services, for example, Ceilometer and Cinder. This blueprint addresses how such a generic host state could be implemented. Second, currently, the update interval for all metrics of host state is shared; however, some metrics change at different speeds, for instance, the number of free VCPUs and CPU utilization, and should be monitored at different intervals.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- rerngvit yanggratoke
Related branches
Related bugs
Sprints
Whiteboard
Who is doing the work here? It needs to be assigned before it can go into the havana roadmap. --russellb
Ceilometer supports different intervals for different polling tasks. Maybe that could be leveraged. -llu
blueprint https:/
Ceilometer supports different intervals for different polling tasks. Maybe that could be leveraged. -llu
blueprint https:/
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
