Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1071372

Summary:	RFE: Calculate and show estimated system return time or average job waiting time
Product:	[Retired] Beaker	Reporter:	Alexander Todorov <atodorov>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	develop	CC:	aigao, asaha, dcallagh, llim, rmancy
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1071364	Environment:
Last Closed:	2014-03-04 10:35:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexander Todorov 2014-02-28 15:41:10 UTC

+++ This bug was initially created as a clone of Bug #1071364 +++

Wrt Bug #1071364 I would like to propose an enhancement, which however can be implemented in many ways and not necessary easily. 

For the Possible systems page I would like to see a column of estimated return time in human readable form (e.g. in 5 minutes, in 3 hours, etc) and be able to sort according to this.

It can be calculated with some heuristics but will not be accurate 100%:

- for systems which are reserved Beaker already knows when the reservation expires
- for system running tasks we can take the average run time of the specified tasks from previous runs on this system (and/or others) and for that particular distro or family. The point being that the more a system is used the more accurate the prediction will become. 



Another possible improvement is to calculate and plot the average waiting time for tasks/distros/recipes/in general. This metrics can be used by both QE teams and IT administrators to plan systems capacity in the test lab.

Comment 2 Dan Callaghan 2014-03-02 22:38:22 UTC

This is essentially the same as bug 814371.

Comment 3 Nick Coghlan 2014-03-02 23:45:05 UTC

This won't be implemented in Beaker itself. However, we're looking at working with the Metrique developers (https://github.com/kejbaly2/metrique) to provide pre-defined analytics for cases where a Beaker instance is hooked up to a suitable data warehouse.

Comment 4 Alexander Todorov 2014-03-04 10:35:02 UTC


*** This bug has been marked as a duplicate of bug 814371 ***