VM Workload Consolidation Strategy¶
Requirements¶
Metrics¶
The vm_workload_consolidation strategy requires the following metrics:
| metric | service name | plugins | comment |
|---|---|---|---|
memory |
ceilometer | none | |
disk.root.size |
ceilometer | none |
The following metrics are not required but increase the accuracy of the strategy if available:
| metric | service name | plugins | comment |
|---|---|---|---|
memory.resident |
ceilometer | none | |
cpu_util |
ceilometer | none |
Planner¶
Default Watcher’s planner:
Weight planner implementation
This implementation builds actions with parents in accordance with weights. Set of actions having a higher weight will be scheduled before the other ones. There are two config options to configure: action_weights and parallelization.
Limitations
- This planner requires to have action_weights and parallelization configs tuned well.
Configuration¶
Strategy parameter is:
| parameter | type | default Value | description |
|---|---|---|---|
period |
Number | 3600 | The time interval in seconds for getting statistic aggregation from metric data source |
Efficacy Indicator¶
[{'value': 0, 'name': 'released_nodes_ratio', 'unit': '%', 'description': u'Ratio of released compute nodes divided by the total number of enabled compute nodes.'}]
Algorithm¶
For more information on the VM Workload consolidation strategy please refer to: https://specs.openstack.org/openstack/watcher-specs/specs/mitaka/implemented/zhaw-load-consolidation.html
How to use it ?¶
$ openstack optimize audittemplate create \
at1 server_consolidation --strategy vm_workload_consolidation
$ openstack optimize audit create -a at1
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.