Outlet Temperature Based Strategy¶
Requirements¶
This strategy has a dependency on the host having Intel’s Power Node Manager 3.0 or later enabled.
Metrics¶
The outlet_temperature strategy requires the following metrics:
| metric | service name | plugins | comment |
|---|---|---|---|
hardware.ipmi.node.outlet_temperature |
ceilometer | IPMI |
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 |
|---|---|---|---|
threshold |
Number | 35.0 | Temperature threshold for migration |
period |
Number | 30 | The time interval in seconds for getting statistic aggregation from metric data source |
Efficacy Indicator¶
None
Algorithm¶
For more information on the Outlet Temperature Based Strategy please refer to: https://specs.openstack.org/openstack/watcher-specs/specs/mitaka/implemented/outlet-temperature-based-strategy.html
How to use it ?¶
$ openstack optimize audittemplate create \
at1 thermal_optimization --strategy outlet_temperature
$ openstack optimize audit create -a at1 -p threshold=31.0
External Links¶
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.