Bug 1317859

Summary: [RFE] - Migration Policy: Add option to manually set migration bandwidth per VM.
Product: [oVirt] ovirt-engine Reporter: meital avital <mavital>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED WONTFIX QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, mavital, tjelinek
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-14 05:57:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description meital avital 2016-03-15 11:37:33 UTC 
Description of problem:
Currently, as part of migration improvement plans, migration policy should
allow to configure migration maxBandwidth.
In addition to this improvement, it would be nice to have the option to set
migration bandwidth per VM.

Possible use cases for this RFE:
- To prioritize important VMs such as VM with large amount of memory, HA VM
and VM with high workload.
Comment 1 Yaniv Kaul 2016-03-15 21:12:42 UTC 
Why? This is not the way to prioritize them. There is a priority field for them, isn't it? Certainly setting specific BW per VM is useless - we have no idea how much a VM would need. The only thing that makes sense is to prioritize which VMs get migrated first and which follows. 

We really hope with the improvements, things will look much much better, and thus more specific throttling won't be needed.
Comment 2 Tomas Jelinek 2016-04-14 05:57:16 UTC 
After a discussion with Meital we agreed that the current "priority" field plus the new migration policies will be enough to handle the intention behind this RFE.
For now closing as wont fix, please feel free to reopen if after the introduction of migration policies this will still be relevant.