Bug 1078187 - [RFE] It would have been more convenient if the id for hosts and cluster, was displayed in UI
Summary: [RFE] It would have been more convenient if the id for hosts and cluster, was...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Ilanit Stein
URL:
Whiteboard: ux
Depends On: 957600 1172390
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-19 11:06 UTC by Ilanit Stein
Modified: 2015-11-16 06:31 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-15 21:40:05 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:
sherold: Triaged+


Attachments (Terms of Use)

Description Ilanit Stein 2014-03-19 11:06:38 UTC
Description of problem:
It would have been more convenient if the host \ cluster ID was shown in UI, under general tab. 
It may save the effort to look for it.

Version-Release number of selected component (if applicable):
av3

Comment 2 Ilanit Stein 2014-03-23 07:29:46 UTC
In case a customer, has a problem, and we debug it,
it is more convenient to have the id straight away, and search for it in the logs.

Also, this can be also useful in case of writing scripts. Such ids are required, as inputs. Otherwise we need to run a REST POST GET query to fetch it.
For example, to create 100 templates, we need to run a query for the cluster id.

Comment 3 Oved Ourfali 2014-03-24 07:31:11 UTC
Einav - thoughts?

Comment 4 Einav Cohen 2014-06-23 16:31:32 UTC
(In reply to Oved Ourfali from comment #3)
> Einav - thoughts?

specifically for debugging problems for customers - we added the correlation ID; if it is not helpful - need to understand why and adjust this feature accordingly. 
I don't think that exposing IDs in the GUI is the solution. 

For scripts - I am not sure exactly what the issue is. if someone needs to know information about a cluster, he needs to query the clusters anyway, to get their names, IDs, other meta-data, etc. 
In this case, IIUC, the user is using the GUI, as well as a script, and it would simply be more convenient for him to copy-paste the cluster-id from the GUI, rather than query it in the API. I don't think that it is an interesting-enough use-case. 

I am in favor of closing this bug. 
we can consider adding an 'id' column for the different grids, which will be hidden by default, once bug 957600 (currently flagged for future) will be taken care of, or add it in the 'General' sub-tab (which not all main-tabs have, and will not be applicable for items already in sub-tabs). again - not interesting enough IMO.

@Arthur - final decision?

Comment 5 Arthur Berezin 2014-06-25 19:20:37 UTC
Einav, I think that the actual solution here is as you suggested, having an id column that is hidden by default and the can view [BZ#957600], I don't think it would be useful cluttering the general sub-tab with information that is rhev internal.

Comment 6 Yaniv Kaul 2015-11-15 21:40:05 UTC
Closing - I don't think we are going to implement this. Hidden column and stuff are not part of the planned UI in 4.x


Note You need to log in before you can comment on or make changes to this bug.