Bug 1317859 - [RFE] - Migration Policy: Add option to manually set migration bandwidth per VM.
Summary: [RFE] - Migration Policy: Add option to manually set migration bandwidth per VM.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 11:37 UTC by meital avital
Modified: 2016-04-14 05:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-14 05:57:16 UTC
oVirt Team: Virt
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.