Gratia Grid Accounting Project


The implementation of the OSG Accounting System is named Gratia and follows the requirements and design described in these documents.

See also the Full Project Definition.

Readiness and Trash/Trash/Integration Plan

We describe a service readiness and integration plan for the Gratia Grid Accounting System following guidelines set forth in New OSG Services. This version of the document pertains to the Gratia projects readiness plan for OSG 0.6.0.

Description of Service

See the Full Project Definition and requirement and design documents.

Running the Gratia services is not necessary to gain the advantage of access to accounting data for a site: one can install only the appropriate probes and use the central Gratia servers (BANANA Twiki link to server list).

Dependencies and Other Services

Running the Gratia services requires a Tomcat 5.5 container and a Mysql 5.0 or greater DB, neither of which are required to be running on the compute element or gatekeeper.

Running the Condor probe requires patches to and for VDT releases up through 1.5.0.

Required Resources

The Gratia services require Java 5, a running Tomcat 5.5 with at least (BANANA XXXMB) memory allocated to it, and a Mysql 5 or better DB. There are different requirements for each probe (BANANA links), but at a minimum they all require at least Python v2.2.

Server requirements

A local instance of the Gratia services is not required: see above.

Locally an appropriately configured Tomcat/Apache server is required and access to a Mysql database, neither of which need be on the compute element or gatekeeper. The Tomcat container should be allocated at least (BANANA XXXMB memory).


Gratia Services will be packaged with VDT via pacman; probes will be available via VDT or by RPM direct from the Gratia Probe Installation Page.

Installation and Configuration

Via VDT: BANANA provide pacman line; configuration procedure TBA.

Probes via RPM: see Gratia Probe Installation Page.

Testing and Validation

Probes and Services are tested on Fermilab's test batch facilities before being propagated to local and volunteer external sites for final pre-release validation.

A Gratia Services installation may be tested by running a test probe (not yet available). Individual probes may be tested by checking for expected data either through a Gratia Services report page or through direct DB queries and comparison with probe log files.



BANANA Greg: current Services handling speed in records per min, say?

Known Problems and Issues

Currently access to accounting data is unrestricted. A future enhancement will restrict direct DB access to the data and provided role-based access to reports based upon browser-provided certificates.

Patching and for VDT versions prior to 1.6.0 may be non-trivial if these files have already been customized locally.

Once sent to the Gratia collector, information from the Condor probe is discarded. If the collector loses this information (DB destruction), these data may not be reconstructible.

For each site, a user -> VO map file is required currently as there is no universal mechanism for obtaining these data from the underlying batch system for the currently available probes.

Contact Information

Send comments and questions to

More Documentation

See the current documentation at

Major updates:
-- PhilippeCanal - 14 Oct 2005

-- ChrisGreen - 09 Oct 2006

Topic revision: r8 - 12 Oct 2016 - 15:10:07 - KyleGross
Hello, TWikiGuest


TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..