• Peer Configuration Overview
• Initial Configuration
• Viewing Jobs From Other Peers

Peer Configuration Overview

In the simplest case, establishing a peer relationship can be accomplished with as few as two configuration lines: one line to indicate how to contact the peer and one line to indicate how to authenticate the server. However, data migration issues, credential mapping, and usage policies must often be addressed in order to make a peer-based grid effective.

To address these issues Moab provides facilities to control how peers inter-operate, enabling full autonomy over both client and server ends of the peer relationship.

Initial Configuration

At a minimum, only two parameters must be specified to establish a peer relationship: RMCFG and CLIENTCFG.  RMCFG allows a site to specify interface information directing Moab on how to contact and inter-operate with the peer. For peer interfaces, a few guidelines must be followed with the RMCFGparameter:

• the TYPE attribute of the peer must be set to moab
• the SERVER attribute must point to the host and user interface port of the remote Moab server
• the name of the resource manager should match the name of the remote peer cluster as specified with the SCHEDCFG parameter in the peer moab.cfg.

SCHEDCFG[MoabServer01] MODE=NORMAL SERVER=hpc-01:41111
RMCFG[MoabServer02]    TYPE=moab   SERVER=hpc-02:40559
...

Configuring the CLIENTCFG parameter is mandatory. When specifying the CLIENTCFG parameter for peers, the following guidelines must be followed:

• the CLIENTCFG parameter must be specified in the moab-private.cfg file on both peers
• an RM: prefix is required before the peer's name
• if using default secret key based security, the value of the KEY attribute must match the KEY value set on the corresponding remote peer
• the AUTH attribute must be set to admin1 in the moab-private.cfg on the destination Moab

CLIENTCFG[RM:MoabServer02] KEY=3esfv0=32re2-tdbne
....

CLIENTCFG[RM:MoabServer01] KEY=3esfv0=32re2-tdbne AUTH=admin1
...