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.
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
*** Bug 1062441 has been marked as a duplicate of this bug. ***
This bug did not make it in time for 3.6 release, moving out
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.
This bug had requires_doc_text flag, yet no documentation text was provided. Please add the documentation text and only then set this flag.
Verified on rhevm-184.108.40.206-0.1.el7.noarch, host with vdsm-4.19.6-1.el7ev.x86_64, according to attached test cases.
There's only one bug which doesn't block the feature, but does limit the ability to use it: