Bug 1170259
| Summary: | [UX] Need to display causal information for situations a disk can't be (live) migrated | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | lkuchlan <lkuchlan> | ||||||
| Component: | ovirt-engine | Assignee: | Tal Nisan <tnisan> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Raz Tamir <ratamir> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.5.0 | CC: | amureini, gklein, kgoldbla, lkuchlan, lsurette, ppostler, rbalakri, Rhev-m-bugs, rmcswain, srevivo, tnisan, ykaul, ylavi | ||||||
| Target Milestone: | ovirt-4.0.7 | Keywords: | UserExperience | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-12-25 10:48:34 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: | |||||||||
| Attachments: |
|
||||||||
(In reply to lkuchlan from comment #0) > 3. Live merge all the disks (not including template disks) to the second NFS > domain This doesn't make sense. Are you live *MERGING* the disk or live *MIGRATING* to another domain? Currently the message mentioned in the bug's description is shown if there are no suitable storage domain targets for the disk to be moved into.
("The following disks cannot be moved : vm_Disk1...")
The issue that is raised in this bug is just one particular reason for the disk not being able to be moved- generally it will be an overkill to mark why each of the domains are not available for the disk..
For instance, if there is a shareable disk on nfs domain, and I have a gluster and block storage, The message will have to inform that Gluster does not support shareable disks and also that File based disk can't be moved to Block storage- and that's the reason there are no available domains to that disk.. (remember I could also have many disks.)
Maybe a proper message could be:
"No suitable storage domains available for the following disks: ...
Please refer to the documentation for more details."
or something similiar?
Einav- What do you think?
Created attachment 994547 [details]
mock-up: Move Disk - improvement suggestion
(In reply to Amit Aviram from comment #5) > Currently the message mentioned in the bug's description is shown if there > are no suitable storage domain targets for the disk to be moved into. > ("The following disks cannot be moved : vm_Disk1...") > > The issue that is raised in this bug is just one particular reason for the > disk not being able to be moved- generally it will be an overkill to mark > why each of the domains are not available for the disk.. generally, I agree with this statement, however please note that you don't need to display everything at once; see attachment 994547 [details] for a suggestion that does not clutter the GUI too much, yet provides the reason(s) for each disk on demand using a tool-tip. If the reason for not having any valid target storage domains is typically imperative, I would consider doing something like attachment 994547 [details]. > > For instance, if there is a shareable disk on nfs domain, and I have a > gluster and block storage, The message will have to inform that Gluster does > not support shareable disks and also that File based disk can't be moved to > Block storage- and that's the reason there are no available domains to that > disk.. (remember I could also have many disks.) > > Maybe a proper message could be: > "No suitable storage domains available for the following disks: ... > Please refer to the documentation for more details." > > or something similiar? > > Einav- What do you think? assuming you prefer this type of solution over my suggestion above: yes, the text can definitely change accordingly; I would probably just add the word 'target' there, in order to relate that to the column currently titled as 'Target'. i.e.: """ No suitable target storage domains available for the following disks: ... Please refer to the documentation for more details. """ Allon, looking at these options- what do you think should be implemented? (In reply to Amit Aviram from comment #8) > Allon, looking at these options- what do you think should be implemented? I'd go with something like Einav's attachment suggest. MUCH better user experience, for a feature that's complicated as it is, and will become even less intuitive in 3.6.0 (3.6 DCs should allow moving between block and file) *** Bug 1203423 has been marked as a duplicate of this bug. *** *** Bug 1183985 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 1379153 *** |
Created attachment 964188 [details] image and logs Description of problem: [Text] Error related causal information is missing from text following a LSM as follows: “the following disks cannot be moved : vm_Disk1...” Version-Release number of selected component (if applicable): 3.5 vt11 How reproducible: 100% Steps to Reproduce: 1. Create at least 2 vms with at least one disk based off a template that resides in an NFS data domain 2. Run all the vms 3. Live merge all the disks (not including template disks) to the second NFS domain Actual results: Expected results: Additional info: