watcher/doc/source/strategies/outlet_temp_control.rst
Santhosh Fernandes 377889859d Add period input parameter to vm workload consolidation and
outlet temp control strategy.

Closes-Bug: #1614021
Change-Id: Iec975e4a4a39168a65ae89ca75a5ca9445c14f9d
2017-03-27 15:06:36 +05:30

2.9 KiB

Outlet Temperature Based Strategy

Synopsis

display name: outlet_temperature

goal: thermal_optimization

Outlet (Exhaust Air) temperature is a new thermal telemetry which can be used to measure the host's thermal/workload status. This strategy makes decisions to migrate workloads to the hosts with good thermal condition (lowest outlet temperature) when the outlet temperature of source hosts reach a configurable threshold.

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

Cluster data model

Default Watcher's Compute cluster data model:

watcher.decision_engine.model.collector.nova.NovaClusterDataModelCollector

Actions

Default Watcher's actions:

action description
migration

watcher.applier.actions.migration.Migrate

Planner

Default Watcher's planner:

watcher.decision_engine.planner.default.DefaultPlanner

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