Deploying WS MDS in a Virtual Organization
WS 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 WS MDS components can be deployed.
What to deploy where
Click for larger diagram
Central to the VO
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.
See: WS MDS Index System Administrator's Guide. - Configure an executing index service to execute scripts for
monitoring non-WSRF services, and register it to the
central index service. This can be central to the VO.
See: Changing aggregator source, in the WS MDS Index System Administrator's Guide - 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.
See: Configuration, in the Aggregator Framework System Administrator's Guide - Install the WebMDS Tech Preview release to show the contents of the
central index service in a web browser.
See: WebMDS tech preview - Deploy a Trigger Service to notify interested parties about changes
in the status of the VO.
See: WS MDS Trigger System Administrator's Guide
On each GRAM installation
- Configure cluster monitoring at each GRAM installation to publish
information about each resource.
See: Cluster Monitoring and the GLUE Resource Property. - Register each resource into the central index service.
See: Configuration, in the Aggregator Framework System Administrator's Guide
On each RFT installation
- Register the RFT Factory to the VO index.
See: Registering RFT Services to an index.