Moab Workload Manager® for Grids

17.5 Localized Grid Management

• 17.5.1 Enabling Bi-Directional Job Flow
• 17.5.1.1 True Peer-to-Peer Grid

17.5.1 Enabling Bi-Directional Job Flow

Figure 1: Bi-directional peer-to-peer setup.

For each peer interface, an RMCFG parameter is only required for the server (or source side of the interface.) However, if non-default resource reporting, usage limits, or other configuration is desired on the client side of the peer interface, then a client-side RMCFG parameter should be specified with CLIENT flag set and the associated configuration. If two peers are to share jobs in both directions, the relationship is considered to be bi-directional.

17.5.1.1 True Peer-to-Peer Grid

Previous examples involved grid masters that coordinated the activities of the grid and made it so direct contact between peers was not required. However, if preferred, the master is not required and individual clusters can interface directly with each other in a true peer manner. This configuration is highlighted in the following example:

SCHEDCFG[clusterA] MODE=NORMAL SERVER=clusterA
RMCFG[clusterA]    TYPE=pbs
RMCFG[clusterB]    TYPE=moab   SERVER=clusterB:40559

CLIENTCFG[RM:clusterB] AUTH=admin1 KEY=banana16

SCHEDCFG[clusterB] MODE=NORMAL SERVER=clusterB
RMCFG[clusterB]    TYPE=pbs
RMCFG[clusterA]    TYPE=moab   SERVER=clusterA:40559

CLIENTCFG[RM:clusterA] AUTH=admin1 KEY=banana16