Bug 1749803
Summary: | [RFE] Improve workflow for storage migration of VMs with multiple disks | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Peter Lauterbach <pelauter> | ||||||
Component: | ovirt-engine | Assignee: | shani <sleviim> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Evelina Shames <eshames> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | urgent | ||||||||
Version: | unspecified | CC: | derez, eshenitz, lwright, mavital, michal.skrivanek, mkalinin, sfishbai, sgoodman, sleviim, tnisan | ||||||
Target Milestone: | ovirt-4.4.2 | Keywords: | FutureFeature | ||||||
Target Release: | 4.4.2 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | ovirt-engine-4.4.2.1 | Doc Type: | Enhancement | ||||||
Doc Text: |
This enhancement enables you to set the same target domain for multiple disks.
Previously, when moving or copying multiple disks, you needed to set the target domain for each disk separately. Now, if a common target domain exists, you can set it as the target domain for all disks.
If there is no common storage domain, such that not all disks are moved or copied to the same storage domain, set the common target domain as 'Mixed'.
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2020-09-23 16:11:04 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 902971, 1839058 | ||||||||
Attachments: |
|
Description
Peter Lauterbach
2019-09-06 13:10:11 UTC
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-4.4.2.2-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. https://access.redhat.com/errata/RHSA-2020:3807 |