suzhengwei 5c86a54d20 workload balance base on cpu or ram util

By the input parameter "metrics", it makes decision to migrate a VM
base on cpu or memory utilization.

Change-Id: I35cce3495c8dacad64ea6c6ee71082a85e9e0a83

2017-08-09 07:04:10 +00:00

2.5 KiB

Raw Blame History

Workload Balance Migration Strategy

Synopsis

display name: workload_balance

goal: workload_balancing

watcher.decision_engine.strategy.strategies.workload_balance

Requirements

None.

Metrics

The workload_balance strategy requires the following metrics:

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

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

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

External Links