GT 3.9.5 Development Release Notes for WS MDS Aggregator

Component Overview

The WS MDS Aggregator is the software framework on which WS MDS services (currently, the WS MDS Index and WS MDS Trigger services) are built. The aggregator framework collects data from an aggregator source and sends that data to an aggregator sink for processing. Aggregator sources distributed with the Globus Toolkit include modules that query service data, acquire data through subscription/notification, and execute programs to generate data. Aggregator sinks include modules that implement the WS MDS Index service interface and the WS MDS Trigger service interface.

Feature Summary

Features new in release GT 3.9.5

  • Ported to use WSRF mechanisms (previously used OGSI).
  • Additional sources which collect information by polling and by execution of local scripts.
  • Management of aggregations is now performed over the wire through WS ServiceGroup APIs.

Other Supported Features

  • Collects information from grid resources using pluggable aggregation sources.
  • Delivers collected information to pluggable sinks.
  • Manages creation and destruction of individual aggregation registrations.

Bug Fixes

Known Problems

Technology Dependencies

MDS-Aggregator depends on the following GT components:

  • Java WS Core

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

  • None

Tested Platforms

Tested Platforms for WS MDS Aggregator Framework

  • Linux on i386
  • Windows XP

Backward Compatibility Summary

Protocol changes since GT version 3.2

  • The aggregator framework is a complete reimplementation of the MDS3 aggregator framework using WSRF rather than OGSI protocols.
  • No wireside compatibility with MDS3 aggregator framework.
  • Architectural similarity should make porting straightforward.

API changes since GT version 3.2

  • APIs entirely rewritten, so no API compatibility.
  • Architectural similarity should make porting straightforward.

Exception changes since GT version 3.2

  • See API changes above.

Schema changes since GT version 3.2

  • Registration interface uses WSRF rather than OGSI schemas.
  • New per-source and per-sink configuration schemas.

For More Information

Click here for more information about this component.