Bug 699890

Summary:	Filter on Attributes for Jobs, Nodes, Slots etc.
Product:	Red Hat Enterprise MRG	Reporter:	William Henry <whenry>
Component:	cumin	Assignee:	grid-maint-list <grid-maint-list>
Status:	CLOSED EOL	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	high	Docs Contact:
Priority:	low
Version:	Development	CC:	croberts, matt, sgraf, tmckay
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-02 19:36:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description William Henry 2011-04-26 20:20:26 UTC

Description of problem:

Customers with large Grid configurations are often pressed for time when trying to find valuable information on why jobs aren't running or why machines aren't accepting jobs etc.

After navigating to a specific job or machine or slot an administrator wants information fast. Often the attributes they are looking for might be custom, customer specific attributes. Having to scroll through a page to find an attribute takes time and this will be repeated over and over all day long.

Some way of finding attributes fast (besides a CTRL-F in the browser) is desirable. Admins want info to pop of the page fast.

One solution would be to have various tabs that can be selected quickly that contain only one viewable page of attrs.

Another would be the ability to filter very fast on a user entered string.

To augment either of the above it would be good to put the most sought after attrs near the top - e.g. START expression or Requirements etc. Or Custom attrs.

When looking at this issue consider an administrator that is getting calls all day from people wondering: "Why is my job not running?" Or "Why is this node continually rejecting my job?" After doing a search for the job (by description) or the node or the slot, the administrator is looking for specific attrs possibly while the submitter is still on the phone.

FYI I had another BZ on this topic but it focused on reducing all the wasted white-space.

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Comment 6 Chad Roberts 2011-06-15 12:25:41 UTC

Available in revision 4830.

Included is the following functionality:

We have added an "overview" tab to the view of an individual job.  By default, it will contain the folowing attributes:  JobStatus, Cmd, Args, ExitStatus, JobStartDate, LastRemoteHost, LastJobStatus, Owner.  That list of attributes can be overridden in cumin.conf to include any standard or custom attribute.  The display order of the attributes is governed by the order that they appear in that list.

Comment 7 Chad Roberts 2011-06-15 12:29:50 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause:  Navigating the myriad of job attributes is cumbersome and undesirable.

Consequence:  Users may wind-up spending more time trying to find specific job attributes.

Change:  We have included a new "overview" tab on the page that displays the details of a job.  There is a default list of attributes that will appear there, but that list can be overridden in cumin.conf to include any set of regular or custom attributes.  The display order of the attributes is governed by the order that the attributes appear in the list.

Result:  Users now have another option when viewing job attributes that they can customize to meet their needs.

Comment 8 Trevor McKay 2011-07-06 17:07:27 UTC

Quote from William Henry via IRC:

"right now the main issue is that when I find a job or a slot and I want to look at an attribute I might have to scroll a lot.  And I have to do this while there is so much whitespace on the attribute page."

So, sounds like removing white space and parceling attributes across multiple tabs might help usability in general, without really creating new functionality.

Comment 10 Matthew Farrellee 2011-07-08 14:40:30 UTC

Deleted Technical Notes Contents.

Old Contents:
Cause:  Navigating the myriad of job attributes is cumbersome and undesirable.

Consequence:  Users may wind-up spending more time trying to find specific job attributes.

Change:  We have included a new "overview" tab on the page that displays the details of a job.  There is a default list of attributes that will appear there, but that list can be overridden in cumin.conf to include any set of regular or custom attributes.  The display order of the attributes is governed by the order that the attributes appear in the list.

Result:  Users now have another option when viewing job attributes that they can customize to meet their needs.

Comment 12 Trevor McKay 2012-03-01 18:59:10 UTC

Note, initial prototype for this was removed pending further design review.