Workload Balance Migration Strategy

updated: 2019-02-13 12:00

Workload Balance Migration Strategy¶

Synopsis¶

display name: Workload Balance Migration Strategy

goal: workload_balancing

Requirements¶

None.

Metrics¶

The workload_balance strategy requires the following metrics:

metric	service name	plugins	comment
`cpu_util`	ceilometer	none
`memory.resident`	ceilometer	none

Cluster data model¶

Default Watcher’s Compute cluster data model:

Actions¶

Default Watcher’s actions:

action description

migration

action	description
`migration`

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 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

External Links¶