Call for Community Testing: 3.9.3 WS MDS Aggregator

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 Aggregator 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 Aggregator

General Overview

The Aggregator module consists of an Aggregating ServiceGroup framework which supports an extensible plugin architecture.

The Aggregating ServiceGroup framework is designed to facilitate the collecting of information from or about WS-Resources via plugin aggregator sources and the feeding of that information to plugin aggregator sinks.

Resources may be registered to an aggregating ServiceGroup using the ServiceGroup add operation. Each registration will be represented as a ServiceGroupEntry resource. When a registration is made, the appropriate aggregation source and sinks will be informed and aggregated data from the registered resource will begin to flow via the aggregation source into the aggregation sink.

The method of collection by source and processing by the sink is dependent on the particular instantiation of the aggregator.

Reasons for testing WS MDS Aggregator

[describe why volunteers are needed]

Components affected by WS MDS Aggregator

MDS-Aggregator depends on the following GT components:

  • MDS Service Group
  • MDS UsefulRP
    • /li>

MDS-Aggregator depends on the following 3rd party software:

  • None

Environment/build parameters and other special conditions to test

  1. [example #1: Various security policies on resource/service/client]
  2. ...
  3. [example #n: The use of different JVMs]

Release notes

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