Bug 995012 - Track job activity
Summary: Track job activity
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Community
Component: web UI
Version: 0.14
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: 0.17
Assignee: matt jia
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 651479 798710
TreeView+ depends on / blocked
 
Reported: 2013-08-08 12:05 UTC by Ales Zelinka
Modified: 2018-02-06 00:41 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-10 23:28:02 UTC


Attachments (Terms of Use)

Description Ales Zelinka 2013-08-08 12:05:41 UTC
Job History should contain record for any change done to a job by a user (and possibly by beaker itself). At least these should be logged:

 * cancellation
 * ack/nack
 * retention tag change
 * priority change


It's crucial to be able to trace changes back to the user who did them when more than one user can manipulate the jobs (submission delegates).

Comment 2 Nick Coghlan 2013-08-10 19:52:34 UTC
This is relevant for group jobs as well, since any group member may update the items Ales mentions.

Comment 3 xjia 2013-08-11 23:48:19 UTC
(In reply to Nick Coghlan from comment #2)
Is it a future feature?

Comment 4 Nick Coghlan 2013-08-26 01:40:01 UTC
This actually affects the old implicit job sharing model as well - even prior to explicit group jobs and submission delegates, multiple users could still update a job, without a clear history of who did what and when.

Comment 5 Nick Coghlan 2013-10-09 05:28:44 UTC
Definitely need to include this in 0.16, since http://beaker-project.org/dev/proposals/improved-reservations-and-loans.html#time-limited-loans will lead to the scheduler cancelling jobs automatically and users need to be able to see what happened.

Comment 7 matt jia 2014-05-05 05:45:16 UTC
On Gerrit:
 
http://gerrit.beaker-project.org/#/c/3059/

Cheers, Matt Jia

Comment 10 Dan Callaghan 2014-06-10 23:28:02 UTC
Beaker 0.17.0 has been released.


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