|
|
NorduGrid Note |
|
proposal |
|||
|
|
||
Bookkeeping Service |
||
Oxana Smirnova* |
||
|
||
|
A proposal for a bookkeeping and provenance history service. |
|
UI |
NorduGrid User Interface |
GM |
NorduGrid Grid Manager |
Bookkeeping database |
Any database server capable of keeping the data and supporting GSI authorization |
User SN |
Subject Name of a user's certificate |
VO |
Virtual Organisation |
There should be a database, with GSI-based authentication and authorisation, and it should be as redundant as MDS, i.e., based on more than one server. Known candidates are OpenLDAP and MySQL.
Information into such a database should be written by the UI and the GM, in a following manner:
UI, after each job submission, writes:
Job ID
Job name
User SN
User VO affiliation
Submission time
Submission machine (client)
NorduGrid client (UI) version
Client Globus middleware version
List of input files
Executable with parameters
List of output files
Requested runtimeenvironment
Requested memory
Requested CPU
Requested disk space
List of uploaded files with size
Execution cluster (gatekeeper)
GM, while job proceeds, writes:
Execution node name
Execution node CPU type
Execution node memory
Execution node OS
NorduGrid server version
Server Globus middleware version
List of downloaded files with size
Status changes with timestamp
At the end: consumed CPU time
At the end: consumed wall time
At the end: consumed memory
At the end: PBS message(s)
At the end: list of uploaded files with size
UI, upon job retrieval or clean-up, writes:
Action type with timestamp
list of retrieved/erased files
GM, upon deletion of non-retrieved job, writes:
Action type (clean-up) with timestamp
List of erased files