- Doc Structure
- A Globus Primer
- Installing GT
- Platform Notes
- Migrating from GT2
- Migrating from GT3
- PDF version
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces
- Resource Properties
- Performance Studies
Table of Contents
- 1. What is a "Call for Community Testing"?
- 2. Participating in the WS MDS Trigger Service Testing Call is easy!
- 3. Testing period
- 4. About WS MDS Trigger Service
- 5. Reasons for testing WS MDS Trigger Service
- 6. Components affected by WS MDS Trigger Service
- 7. Environment/build parameters and other special conditions to test
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.
- Install the software in a non-production environment. Use the 4.1.0 distribution
the code can also be retrieved directly from CVS using the tag
- Exercise the software.
- Log your experiences in http://bugzilla.globus.org/globus/ under the "MDS4" product. Please mention 4.1.0 explicitly in the body of the report.
- If you have any questions or comments regarding this component, join the email@example.com list to participate in discussions with other testers. (To subscribe, read the instructions here.)
- Optional: Consider sending descriptions of your tests to firstname.lastname@example.org so that we might use them to build standard tests in the future. (To subscribe, read the instructions here.)
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.
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.
The Trigger Service depends on the following GT components:
The Trigger Service depends on the following 3rd party software: