
Metric 'memory.usage' depends on balloon driver, and shows the memory usage inside guest-os, while 'memory.resident' represents volume of RAM used by the instance on the physical machine So, it is more reasonable to use 'memory.resident' when calculating node utilization by gathering instances utilization of the node. Change-Id: I12dff5176bcf6cb103aa44cafd54f9ecd7170864
3.2 KiB
VM Workload Consolidation Strategy
Synopsis
display name:
vm_workload_consolidation
goal: vm_consolidation
watcher.decision_engine.strategy.strategies.vm_workload_consolidation
Requirements
Metrics
The vm_workload_consolidation strategy requires the following metrics:
metric | service name | plugins | comment |
---|---|---|---|
|
none none |
The following metrics are not required but increase the accuracy of the strategy if available:
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
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