Difference between revisions of "GenericHostStateSpec"
(Created page with " == Summary == This blueprint addresses an issue that there are multiple sources of information that the nova scheduler can consume to make scheduling decision, for example, C...") |
(→Summary) |
||
| Line 1: | Line 1: | ||
== Summary == | == Summary == | ||
| − | This blueprint addresses an issue that there are multiple sources | + | This blueprint addresses an issue that there are multiple sources for the nova scheduler to make scheduling decision. This blueprint is needed because we do not want the Scheduler to be dependent on Ceilometer. Such a source, for example, Cinder, Ceilometer, and compute node, are referred to as metric source. |
| + | |||
| + | == Design == | ||
| + | The key design is a key-value dictionary that works as an abstraction layer between the scheduler and the metric sources. The key within the layer should be unique across the sources. It is configurable within this layer how to map between each key to a metric source, for example, a number of free VCPUs is mapped to a compute node. | ||
== Design == | == Design == | ||
Revision as of 07:56, 6 May 2013
Summary
This blueprint addresses an issue that there are multiple sources for the nova scheduler to make scheduling decision. This blueprint is needed because we do not want the Scheduler to be dependent on Ceilometer. Such a source, for example, Cinder, Ceilometer, and compute node, are referred to as metric source.
Design
The key design is a key-value dictionary that works as an abstraction layer between the scheduler and the metric sources. The key within the layer should be unique across the sources. It is configurable within this layer how to map between each key to a metric source, for example, a number of free VCPUs is mapped to a compute node.
