Red Hat Bugzilla – Bug 1356045
[RFE] Storage...virtual machines and Storage...templates subtab columns need the ability to expand and sort
Last modified: 2018-05-15 13:40:08 EDT
This RFE asks for the ability to expand and sort the columns in both the Templates and Virtual Machines subtab of the Storage Tab. Why is this important? Go to the storage tab, select a storage domain, and see a list of dozens or hundreds of VMs. I have a large RHEV customer who needs to sort those VMs and select ranges to do operations on the whole range. The customer also needs the ability to expand the columns to see the whole field inside the columns.
This is not a small task since this particular subtabs are not using the standard FE infrastructure to render because they are having expandable content. @Greg: could you please elaborate a bit more on what operations would you like to be able to do? Why from the storage subtabs? And also which fields are not visible? thank you
Try this. Within RHEVM Admin console Click on Storage tab Highlight a storage domain Click on Edit Try to expand or sort the LUN ID or Serial # or any other field. With hundreds of LUNs we need to sort the fields too. _______________________________________________________________ Within RHEVM Admin console Click on Storage tab Click on Virtual Machine at bottom pane Try to expand any of the column. None are expandable. ________________________________________________________________ Within RHEVM Admin console Click on Storage tab Click on Template at bottom pane Try to expand any of the column. None are expandable.
moving to storage team, since most of the items here are storage.
For Tomas - see John's comment #2 for my needsinfo. I'm not sure if clearing my needsinfo messes up the one Yaniv D put in a couple days ago. - Greg
There's currently an open RFE on the UX team for supporting all of the above in tree based sub tabs, once it's fixed it will be quite easy to implement in our sub tabs
(In reply to Greg Scott from comment #0) > This RFE asks for the ability to expand and sort the columns in both the > Templates and Virtual Machines subtab of the Storage Tab. > > Why is this important? > > Go to the storage tab, select a storage domain, and see a list of dozens or > hundreds of VMs. I have a large RHEV customer who needs to sort those VMs > and select ranges to do operations on the whole range. The customer also > needs the ability to expand the columns to see the whole field inside the > columns. What operations exactly? Perhaps we can ease the work of selecting VMs and performing an operation on them. What is the selection criteria?
John, I'll need your help getting Yaniv the info he needs. So I'm keeping the needsinfo flag turned on. See comment 2 for John's description of examples where columns need to be sortable and expandable. So now Yaniv is asking for examples of why that capability would be useful. This info is important to help engineering prioritize what to work on. I'll take a stab at some of it. Let's say there's a list of hundreds of VMs. They are all named the same, except for maybe a sequence number at the end. But those last few characters of the name are not visible because the column is too small. That makes it challenging to select a VM to operate on. So why not just go to the VM tab and do it from there? This is a viable workaround, but it sometimes takes *minutes* to refresh the VMs in the VM tab, and selecting the proper VM requires putting together a complex query. So a 10 second operation becomes a complex 5 minute query. Times hundreds of VMs, it becomes a productivity killer. And when looking at the LUNs in a storage domain - same thing, the LUNs sre all named with a long string in the front with the unique portion of the name on the right. But the column isn't always wide enough to show it. Why care about individual LUNs in a storage domain? Because this is how the customer ties performance and capacity measurements back to the SAN. thanks - Greg
On the LUN stuff - the ability to sort is also important because the WWIDs never show up grouped together - so there's no easy way to see which LUNs belong to what storage domains. - Greg
Is this improved after the UI changes in 4.2?
Most likely it was improved in most if not all the gaps described
Tested on ovirt-engine-https://bugzilla.redhat.com/show_bug.cgi?id=1509629 All mentioned (and more) columns are expendable and sortable. If any specific column that wasn't mentioned in this bug needs to be tested put needinfo for me. Moving to VERIFIED
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No external trackers attached] For more info please contact: rhv-devops@redhat.com
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [No external trackers attached] For more info please contact: rhv-devops@redhat.com
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, 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/RHEA-2018:1488