|Summary:||[RFE] Making VM pools able to allocate VMs to multiple storage domains to balance disk usage|
|Product:||Red Hat Enterprise Virtualization Manager||Reporter:||Luca Villa <luvilla>|
|Component:||ovirt-engine||Assignee:||Shahar Havivi <shavivi>|
|Status:||CLOSED ERRATA||QA Contact:||sefi litmanovich <slitmano>|
|Version:||3.3.0||CC:||amureini, bperkins, gklein, greartes, istein, lpeer, lsurette, luvilla, masayag, mavital, michal.skrivanek, mkalinin, rbalakri, Rhev-m-bugs, sherold, srevivo, ssekidde, trichard, ykaul|
|Fixed In Version:||Doc Type:||Enhancement|
With this release, when creating virtual machine pools using a template that is present in more than one storage domain, virtual machine disks can be distributed to multiple storage domains by selecting "Auto select target" in New Pool -> Resource Allocation -> Disk Allocation.
|Last Closed:||2017-04-25 00:47:13 UTC||Type:||Bug|
|oVirt Team:||Virt||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||1356488|
|Bug Blocks:||1066135, 1415559|
Description Luca Villa 2014-03-27 14:25:43 UTC
Nature and description of the request: The same template in RHEV can be copied to more than one SD. When a VM is created based on such a template its disks are allocated by default on the least used SD. The same applies upon pools' creation, however when a new VM within the pool is instantiated it's disks are allocated on the same SD as the pool even if there are less used SDs where the template also resides. This request is to make RHEV capable to dynamically allocate the disks of a VM in a pool based on the level of usage among SDs.
Comment 5 Michal Skrivanek 2014-08-22 11:07:39 UTC
complexity depends how fancy this needs to be. If we should just simply do a dumb round robin at the pool creation (or extension) time then it's not difficult As long as we keep it simple, i.e. at the pool creation time only
Comment 8 Michal Skrivanek 2015-03-31 09:57:01 UTC
*** Bug 1062441 has been marked as a duplicate of this bug. ***
Comment 11 Michal Skrivanek 2015-06-05 12:13:36 UTC
This bug did not make it in time for 3.6 release, moving out
Comment 12 sefi litmanovich 2016-12-04 11:06:10 UTC
1.Please Review the attached test cases for this RFE and let me know either here or private message if I should change/remove/add something to it. 2. Please see related bz - https://bugzilla.redhat.com/show_bug.cgi?id=1401278 3. Maybe we can add a feature that allows the user to remove vm's disk from one SD which will result in immediately re create the disk from the other SD? Don't know if this is useful but just a thought.
Comment 13 Yaniv Lavi 2016-12-14 16:18:40 UTC
This bug had requires_doc_text flag, yet no documentation text was provided. Please add the documentation text and only then set this flag.
Comment 14 sefi litmanovich 2017-02-21 16:52:24 UTC
Verified on rhevm-18.104.22.168-0.1.el7.noarch, host with vdsm-4.19.6-1.el7ev.x86_64, according to attached test cases. Test run: https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/testrun?id=02212017 There's only one bug which doesn't block the feature, but does limit the ability to use it: https://bugzilla.redhat.com/show_bug.cgi?id=1425493