Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
oops, early return.
Investigate what kind of data is available in the plugins to quantify the "age" of a submission. This could be accumulated run time, or original queue date, other ideas?
This is an effort to make the "Longest Running Grid Submission" table in cumin useful. Right now what it actually reports is "oldest qmf object creation date" which is not really the same thing.
Will update QMF plugins/daemon as well as Aviary query server to include oldest_qdate (oldest_job, original_qdate, qdate???) field to submission object/summary respectively.
How about -
property name="QDate" type="absTime" desc="Oldest QDate of member jobs"
Can change as jobs filter out of existence and services restart. Schedd - when jobs leave the queue and the Schedd restarts. JobServer - when jobs leave the history and JobServer restarts. No need to update the QDate as jobs filter out of existence.
Added for QMF contrib:
<property name="QDate" type="absTime" desc="Oldest QDate of member jobs"/>
Aviary SubmissionSummary gets:
<xs:element name="qdate" type="xs:int"/>
This could be made as xs:dateTime but wasn't sure if you wanted that in epoch format or not. Seems like the date arithmetic would be more straightforward that way. Let me know.