watcher/doc/source/strategies/workload_balance.rst
licanwei 90291923a1 Update strategy doc
Ceilometer removed cpu_util metric in [1].
Another metric compute.node.cpu.percent need to set
compute_monitors option to cpu.virt_driver in the
nova.conf, we should remind user about these.
[1]: https://review.opendev.org/#/c/580709/

Change-Id: I89306ef7c26fa2927945bd4f3ee88b670511d147
2019-06-20 10:57:05 +08:00

2.7 KiB

Workload Balance Migration Strategy

Synopsis

display name: Workload Balance Migration Strategy

goal: workload_balancing

watcher.decision_engine.strategy.strategies.workload_balance.WorkloadBalance

Requirements

None.

Metrics

The workload_balance strategy requires the following metrics:

metric service name plugins comment

cpu_util

memory.resident

ceilometer

ceilometer

none

none

cpu_util has been removed since Stein.

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.weight.WeightPlanner

Configuration

Strategy parameters are:

parameter type default Value description

metrics

String

'cpu_util'

Workload balance base on cpu or ram utilization. choice: ['cpu_util', 'memory.resident']

threshold Number 25.0 Workload threshold for migration
period Number 300 Aggregate time period of ceilometer

Efficacy Indicator

None

Algorithm

For more information on the Workload Balance Migration Strategy please refer to: https://specs.openstack.org/openstack/watcher-specs/specs/mitaka/implemented/workload-balance-migration-strategy.html

How to use it ?

$ openstack optimize audittemplate create \
  at1 workload_balancing --strategy workload_balance

$ openstack optimize audit create -a at1 -p threshold=26.0 \
        -p period=310 -p metrics=cpu_util

None.