Software Links
Getting Started
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- GT Developer's Guide
- GT User's Guide
- Migrating Guides
Reference
Manuals
Common Runtime
Security
- GSI C
- GSI Java
- Java WS A&A
- C WS A&A (coming soon)
- CAS
- Delegation Service
- MyProxy
- GSI-OpenSSH
- SimpleCA
Data Mgt
WS MDS
Execution Mgt
Table of Contents
Because MDS is built on top of Java WS Core, make sure you are familiar with the deployment information here.
MDS should be deployed in a distributed fashion. Some components should be deployed central to a VO, while others should be deployed on individual resources. This document is a suggested deployment, and is not the only way in which MDS components can be deployed.
The following diagrams outlines a VO-wide deployment:
[FIXME better diagram]
The following steps are VO-wide, although the services deployed do not need to be run on the same host or be at the same location.
Deploy an index service central to the VO to collect information about all of the resources in the VO.
If your VO is part of a larger VO, register the central index service of your VO to the central index of the larger VO.
Install the WebMDS servlet to show the contents of the central index service in a web browser.
Deploy a Trigger Service to notify interested parties about changes in the status of the VO.
On each GRAM4 installation
Configure cluster monitoring at each GRAM installation to publish information about each resource. [FIXME more details about how schedulers do not need config?]