Bug 4791 - Job state history RP
: Job state history RP
Status: RESOLVED WONTFIX
: GRAM
wsrf managed execution job service
: development
: Macintosh All
: P3 enhancement
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2006-10-19 11:09 by
Modified: 2012-09-05 11:43 (History)


Attachments


Note

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


Description From 2006-10-19 11:09:03
GRAM4 should provide an easy mechanism for a client to get the job state
history.    The specific request from Gregor is for each job state that
occurred and the timestamp of when it occurred.  The MEJS has this information
and could provide this in a new RP.  Also, new fields could be added to the
audit record for these job state change details.  Maybe we should do both of
these?
------- Comment #1 From 2006-10-19 11:50:23 -------
A commandline tool that returns that information easily would be highly useful.
Values of interest are

globus-job-info -contact .... -log

returs the log file

globus-job-info -contact .... -audit

returns the audit information 

All time stamps should be given in the format that it is in

Although different in nature, we need some information on who am I realy which
I think is commig from the audit informations. This returns the name of the
user in which behalf the job is submitted to the scheduler, which in principal
can be different from the login name and may even have a different dn.

globus-job-info -contact .... -whoami

lists the login name, the name under which the job is submitted, and the DN

The details can naturally be changed, but I guess the above gives an idea how
to proceed.
An XPATH query is unsuitable as the users will need this high level wrapper. 
------- Comment #2 From 2007-09-19 11:38:05 -------
Reassigning to current GRAM developer to close/fix as appropriate.
------- Comment #3 From 2012-09-05 11:43:28 -------
Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issue in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363