Edit $GLOBUS_LOCATION/etc/metascheduler/resourcemanager-config.xml and specify a "cluster" section for each resource manager you will be accessing through the RM Adapter.

You must define the following elements:

name: the name by which this cluster can be referenced.
type: the type of resource manager. Currently only supports type "LSF".
host: the host where the resource manager can be contacted. For LSF, this is the host which is running the gabd.
port: the port number where the resource manager can be contacted. For LSF, this is specified in $LSF_ENVDIR/ga.conf.

2. Configuring CSF

Edit $GLOBUS_LOCATION/etc/metascheduler/metascheduler-config.xml and specify:

GISHandle: the endpoint of the local Index Service.
registryHandle: the endpoint of the local container registry.

	Note
	Do not use 'localhost' or 127.0.0.1 within the endpoint. Use the actual host IP address or fully qualified host name.

3. Configuring the Queuing Service

Edit $GLOBUS_LOCATION/etc/metascheduler/metascheduler-config.xml in the section "queueConfig". By default, there are no queues configured in CSF. Any job submission to a queue will fail. Each queue has its own configuration section, in which you can specify:

name: this attribute on the queueConfig element specifies the name by which this queue is referenced.
plugin: the name of the class that implements the com.platform.metascheduler.impl.schedPlugin interface. The default plugin (schedPluginDefault) is always loaded for a queue regardless whether it is defined in the queue configuration. If the plugin doesn't exist or does not implement the schedPlugin interface, it will not be loaded. You can specify as many plugins for a queue as you wish.
scheduleInterval: the interval in seconds between scheduling cycles. Its value is and integer between 5 and 600. This parameter is optional, and if not defined will default to 30 seconds. This is a parameter of schedPluginDefault.
throttle: this is a parameter for the throttle scheduler plugin (com.platform.metascheduler.impl.schedThrottle), and sets the maximum number of jobs that can be dispatched to a back end resource manager in each scheduling cycle. The value is an integer greater than 0.

4. Support for multiple GT 4.1.3 hosting environments

CSF supports the management of jobs and reservations across resource managers hosted in multiple GT 4.1.3 containers which are part of the same Virtual Organization (VO) (i.e. they trust the same CAs). The multiple container support allows CSF services running in one container to send jobs to the Resource Manager Adapters in another container,etc. In order to support this behaviour, there needs to be a central Index Service for storing information about the different RM Adapters in the VO. This Index Service must be hosted in a container that doesn't host the CSF services.

In order to set up this configuration, the following steps should be taken:

On the hosts running the CSF services for the VO (1 or more hosts), edit $GLOBUS_LOCATION/etc/metascheduler/metascheduler-config.xml and set the endpoint of the central Index Service for the VO in:
- The ReservationConfig section, in the CommunityGISHandle element.
- The queueConfig section for each queue you want to use remote RM Adapters, in the communityGisHandle parameter.
On the host running the central Index Service, edit $GLOBUS_LOCATION/etc/globus_wsrf_mds_index/hierarchy.xml, and configure the location of the Index Services running in the containers running CSF as downstream elements.

Prev		Next
Building and installing	Home	Deploying