Actually, the metric "cpu_util" and "memory.resident" are necessary in vm_workload_consolidation.py, according to line 75. So modify this document about this part. Change-Id: I648f341184a0b42d88dcb4c934af989997fe3fea
2.9 KiB
VM Workload Consolidation Strategy
Synopsis
display name:
VM Workload Consolidation Strategy
goal: vm_consolidation
watcher.decision_engine.strategy.strategies.vm_workload_consolidation.VMWorkloadConsolidation
Requirements
Metrics
The vm_workload_consolidation strategy requires the following metrics:
metric | service name | plugins | comment |
---|---|---|---|
|
none none 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
change_nova_service_state
watcher.applier.actions.change_nova_service_state.ChangeNovaServiceState
Planner
Default Watcher's planner:
watcher.decision_engine.planner.weight.WeightPlanner
Configuration
Strategy parameter is:
parameter | type | default Value | description |
---|---|---|---|
|
Number |
3600 |
The time interval in seconds for getting statistic aggregation from metric data source |
Efficacy Indicator
watcher.decision_engine.goal.efficacy.specs.ServerConsolidation.get_global_efficacy_indicator
Algorithm
For more information on the VM Workload consolidation strategy please refer to: https://specs.openstack.org/openstack/watcher-specs/specs/mitaka/implemented/zhaw-load-consolidation.html
How to use it ?
$ openstack optimize audittemplate create \
at1 server_consolidation --strategy vm_workload_consolidation
$ openstack optimize audit create -a at1