Call for Community Testing: 3.9.3 WS MDS Trigger Service

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, the Globus Alliance hopes to expose its 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.

Participating in the WS MDS Trigger Service Testing Call is easy!

  1. Optional: Consider sending mail to testing@globus.org to let us know that you're helping out and describing what you intend to test.
  2. Install the software in a non-production environment. Use the 3.9.3 distribution from http://www-unix.globus.org/toolkit/downloads/development/; the code can also be retrieved directly from CVS using the tag [tag].
  3. Exercise the software.
  4. Log your experiences in http://bugzilla.globus.org/globus/ under the "[component]" product. Please mention 3.9.3 explicitly in the body of the report.
  5. Optional: Consider sending descriptions of your tests to testing@globus.org so that we might use them to build standard tests in the future.
  6. If you have any questions are comments about the process, send an email to testing@globus.org.

Testing period

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

About WS MDS Trigger Service

The Trigger Service collects data from resources on the grid and, if administrator defined rules match, can perform various actions. An example use is to send email when queue length on a compute resource goes over a threshold value.

Reasons for testing WS MDS Trigger Service

Many interesting/hard-to-diagnose bugs previously found in MDS components have been discovered in large-scale wide-area testing in the presence of unexpected failure conditions (for example, network failures or resource failure). Such conditions are difficult to recreate in a restricted testing environment.

Components affected by WS MDS Trigger Service

[component name] depends on the following GT components:

  • GT component #1
  • ...
  • GT component #n

[component name] depends on the following 3rd party software:

  • 3rd party software dependency #1
  • ...
  • 3rd party software dependency #n

Environment/build parameters and other special conditions to test

Especially of interest are:

  • Index deployments over wide area networks
  • Index deployments involving large numbers of registered resources
  • Indexing of large GRAM installations (monitoring large numbers of nodes via Ganglia and Hawkeye

Release notes

Release notes for the 3.9.3 WS MDS Trigger Service can be found here.