The basic strategy requires the following metrics:
| metric | service name | plugins | comment |
|---|---|---|---|
compute.node.cpu.percent |
ceilometer | none | |
cpu_util |
ceilometer | none |
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.
Strategy parameter is:
| parameter | type | default Value | description |
|---|---|---|---|
migration_attempts |
Number | 0 | Maximum number of combinations to be tried by the strategy while searching for potential candidates. To remove the limit, set it to 0 |
period |
Number | 7200 | The time interval in seconds for getting statistic aggregation from metric data source |
[{'value': 0, 'name': 'released_nodes_ratio', 'unit': '%', 'description': u'Ratio of released compute nodes divided by the total number of enabled compute nodes.'}]
$ openstack optimize audittemplate create \
at1 server_consolidation --strategy basic
$ openstack optimize audit create -a at1 -p migration_attempts=4
None.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.