The "cpu_util" metric has been deprecated a few years ago. We'll obtain the same result by converting the cumulative cpu time to a percentage, leveraging the rate of change aggregation. Change-Id: I18fe0de6f74c785e674faceea0c48f44055818fe
2.8 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 |
---|---|---|---|
|
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
Planner
Default Watcher's planner:
watcher.decision_engine.planner.weight.WeightPlanner
Configuration
Strategy parameters are:
parameter | type | default Value | description |
---|---|---|---|
|
String |
'instance_cpu_usage' |
Workload balance base on cpu or ram utilization. Choices: ['instance_cpu_usage', 'instance_ram_usage'] |
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=instance_cpu_usage
External Links
None.