1. Proposed title of this feature request
Improved workflow for VM storage Migration
2. What is the nature and description of the request?
When migrating storage for a VM with multiple disks, RHV requires that the admin individually select the destination storage domain for each VM disk. This becomes tedious when migrating the storage for many VMS with multiple disks. RHV should have a simpler workflow to move all the VM disks to a single storage domain.
3. Why does the customer need this? (List the business requirements here)
To reduce errors, and eliminate inefficiencies when migrating storage for VMS with multiple disks.
4. How would the customer like to achieve this? (List the functional requirements here)
There should be a default storage destination for all the storage on a VM as an initial step, but we should still retain the option to assign different VM disks to different destination storage domains.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
a. Migrate a VM with multiple disks to a single storage domain with a simplified workflow.
b. Migrate a VM with multiple disks to different storage domains, as you can today.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Benny, we said we'll have it as a part of using data domain for export
(In reply to Tal Nisan from comment #2)
> Benny, we said we'll have it as a part of using data domain for export
This will work for copying, but not for moving, is it enough?
If moving is required, then a "Set all to <sd>" combobox added to multiple move dialog can do the trick I think
From the customer point of view, this will be needed for moving a VM as well as copying.
(In reply to Peter Lauterbach from comment #4)
> From the customer point of view, this will be needed for moving a VM as well
> as copying.
if that's the case, then a "Set all to" combo would be good enough?
Please review this UX work with Storage team.
This flag was cleared by previous comment, resetting.
Has any work been done already that needs to be reviewed or do we want to start designing this feature before implementation starts? I definitely recommend doing some design iterations before any implementation starts.
we're late for 4.4 RFEs, looks minor and suitable for a backport though.
Created attachment 1700193 [details]
Design1 - Added a new "Apply to all" column
In case of moving more than 1 disk, there's a new column with "Apply to all" checkbox.
WIP: Once checking a checkbox, all target domains should match the "checked" one.
Created attachment 1700198 [details]
Design2 - target domain select-box
I think a column of "apply to all" could be rather confusing in this case for a few reasons:
* Multiple checkboxes implies multiple selections, but in this case only one row can be selected
(since obviously only one configuration can apply to all).
* Using a radio buttons instead mitigates the previous issue, but we also have to allow no selection.
I.e., use a different selection for every disk.
* It's not clear which properties are affected by the checkbox; target domain/disk profile/both?
As an alternative, I would suggest adding a 'target storage domain' select-box above the table
that affects all disks when changed: see 'Design2' attachment.
So to avoid confusion on custom selection (when a target domain is manually changed for a disk),
the select-box is changed to 'Mixed'
What do you think?
I'm OK with that one.
Laura, what do you think?
That works for me.
Verified on eninge-184.108.40.206-0.3
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Red Hat Virtualization security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.