|
|||
17.2 Grid Configuration
17.2.1 Peer Configuration OverviewIn the simplest case, establishing a peer-to-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. 17.2.2 Peer-to-Peer Initial ConfigurationAt 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 RMCFG parameter:
Example
SCHEDCFG[MoabServer01] MODE=NORMAL SERVER=hpc-master:41111 RMCFG[MoabServer02] TYPE=moab SERVER=hpc-slave1:40559 ... Configuring the CLIENTCFG parameter is mandatory. When specifying the CLIENTCFG parameter for peers, the following guidelines must be followed:
Example
CLIENTCFG[RM:slave1] KEY=3esfv0=32re2-tdbne AUTH=admin1 ....
17.2.3 Viewing Jobs From Other PeersPeers in a grid can view submitted jobs from other peers by using showq. The moab.cfg file needs to be modified on each peer to configure them to send tranmissions to each other.
Searches Moab documentation only
|
|||
| © 2001-2010 Adaptive Computing Enterprises, Inc. | |||