Appendix C. GT 4.1.0 Call for Community Testing: WS GRAM

1. What is a "Call for Community Testing"?

A Call for Community Testing is a mechanism to notify our users that new Globus code is available for testing in the field. Through these calls, we hope to expose the code to a wide variety of usage scenarios early in its development process. The ultimate goals are to catch bugs that have historically been found only after final releases, and to elicit feedback from the community on ways our software can be improved.

2. Participating in the WS GRAM Testing Call is easy!

  1. Install the software in a non-production environment. Use the 4.1.0 distribution from http://www.globus.org/toolkit/downloads/development/; the code can also be retrieved directly from CVS using the tag globus_4_1_0.
  2. Exercise the software.
  3. Log your experiences in http://bugzilla.globus.org/globus/ under the "GRAM" product. Please mention 4.1.0 explicitly in the body of the report.
  4. If you have any questions or comments regarding this component, join the gram-user@globus.org list to participate in discussions with other testers. (To subscribe, read the instructions here.)
  5. Optional: Consider sending descriptions of your tests to gram-dev@globus.org so that we might use them to build standard tests in the future.

3. Testing period

The testing period for this call is [FIXME: date range].

4. About WS GRAM

Web Services Grid Resource Allocation and Management (WS GRAM) component comprises a set of WSRF-compliant Web services to locate, submit, monitor, and cancel jobs on Grid computing resources. WS GRAM is not a job scheduler, but rather a set of services and clients for communicating with a range of different batch/cluster job schedulers using a common protocol. WS GRAM is meant to address a range of jobs where reliable operation, stateful monitoring, credential management, and file staging are important.

5. Reasons for testing WS GRAM

  • We need volunteers to exercise WS GRAM to... [FIXME]

6. Technology dependencies

GRAM depends on the following GT components:

  • Java WS Core
  • Transport-Level Security
  • Delegation Service
  • RFT
  • GridFTP
  • MDS - internal libraries

GRAM depends on the following 3rd party software:

Scheduler adapters. These dependencies exist only for the batch schedulers configured, thus making job submissions possible to the batch scheduling service. Scheduler adapters are included in the GT 4.1.0.x releases for the following schedulers:

Other scheduler adapters available for GT 4.1.0.x releases:

The XML::Parser Perl module is required for job description extension support.

7. Environment/build parameters and other special conditions to test

  1. [FIXME]

8. For more information

For more information, see the WS GRAM Release Notes.