Bug 4409 - Investigate and improve GRAM service auditing
: Investigate and improve GRAM service auditing
: development
: Macintosh All
: P3 normal
: ---
Assigned To:
: 3742 4410 4411 4412 4528 4833 4902
  Show dependency treegraph
Reported: 2006-05-17 10:05 by
Modified: 2012-09-05 11:43 (History)

GT auditing and interface to accounting (258.50 KB, application/octet-stream)
2006-05-17 14:48, Stuart Martin
GT audit and interface to accounting (258.50 KB, application/msword)
2006-05-23 09:50, Stuart Martin
GT Audit and Interface to Accounting (292.50 KB, application/msword)
2006-12-08 10:07, Stuart Martin


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

Description From 2006-05-17 10:05:07
Service auditing should be improved to be more scalable as well as provide the
means to locate an audit entry for a specific job in an efficient way.

Currently, WS GRAM service auditing information is ouput in the container log
file.  For Pre-WS GRAM it is output in the gatekeeper log file.  To find
specific information for a specific job a parsing program is needed to search
through the log.  Additionally, the log file contains a large amount of data
other than the gram service auditing information.  The current thought is to
add the ability to the GRAM service to insert audit records directly into a
------- Comment #1 From 2006-05-17 14:48:37 -------
Created an attachment (id=955) [details]
GT auditing and interface to accounting

The attachment is a design doc for a Globus Toolkit Audit System.  We describe
how auditing information will be produced by Globus Toolkit services and
integrated with local accounting systems for use by Grid Service Providers. Use
cases focus on the GRAM service, but the design is meant to be extensible for
any grid service.
------- Comment #2 From 2006-05-17 14:58:43 -------
The doc is also available from here:
------- Comment #3 From 2006-05-23 09:50:11 -------
Created an attachment (id=962) [details]
GT audit and interface to accounting

Previous Word doc attachement was listed with the wrong type.
------- Comment #4 From 2006-06-01 11:44:52 -------
Referring to version 0.6 of the document:

1. In section 5.2, it would be useful to have an 
   operation like 



  1.1 returns the list of GJIDs for the user defined by 
      the Grid UID and, 

  1.2 if the optional all_users parameter is "true" 
      and if there is somehwere (e.g., in a DB role-table 
      or in the LRM configuration) a "manager" role defined 
      for the GridUID of the client, then it returns the GJIDs 
      of all the jobs from all users. (Perhaps a time-stamp 
      could be  a second parameter to restrict the time 
      interval of the selected GJIDs.)

2. In the figures in Sections 7.1 and 7.2:

  2.1 replace "RM adapter" with "LRM adapter";
  2.2 replace "Resource manager" with "Local Resource manager";
  2.3 replace "RM Accounting" with "LRM accounting" 

3. In Section 8, "Glossary", insert definition for AMIE
   (AMIE appears in the Figures in Section 7, but 
    it is not defined)

4. Using OGSA DAI for pre-WS GRAM has the advatange 
   of having one solution for both WS and pre-WS GRAM. 
   However, it has two disadvantages:

   (1) Requires installing a GT4 container along with 
       the pre-WS Gatekeeper/Job Manager;

   (2) Requires a client that "speaks" OGSA DAI. 

   Would it be possible to add the accounting/auditing 
   functionality to pre-WS GRAM as a lightweight 
   gatekeeper service (which, unlike the per-job job manager, 
   will be a per-gatekeeper service that queries the 
   Audit and Accounting tables)?

------- Comment #5 From 2006-12-08 10:07:24 -------
Created an attachment (id=1138) [details]
GT Audit and Interface to Accounting

I added more detailed examples of the query interface using OGSA-DAI.
------- Comment #6 From 2007-08-18 14:09:54 -------
GRAM2 and GRAM4 "auditing enabled" services are being packaged by TG's packing
team for CTSS V4.  We are supporting them as needed to make this a success.

------- Comment #7 From 2012-09-05 11:43:11 -------
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: