Ch. 1 - Installing and
Configuring Linux

Ch. 2 - Deploying Torque (Open PBS)

Ch. 3 - Deploying Sun Grid Engine (SGE)

Ch. 4 - Deploying The PostgreSQL Relational Database

Ch. 5 - Fixing Java and ANT

Ch. 6 - Deploying The Globus Toolkit 4.0.x

Ch. 7 - Connecting Globus Gram WS and Torque (Open PBS)

Building the WS GRAM PBS jobmanager

Testing the GRAM WS PBS jobmanager

Ch. 8 - Connecting Globus Gram WS and SUN Grid Engine

Ch. 9 - A Distributed Grid Application

Chapter 7: Connecting Globus Gram WS and Torque (Open PBS)

Building the WS GRAM PBS jobmanager

Before building the WS GRAM PBS jobmanager you should stop the container on nodeb. While you could just SIGTERM it, you can also use the 'globus-stop-container' command after setting up the credentials properly for user 'globus':

[globus@nodeB gt4.0.1-all-source-installer]$ export X509_USER_CERT=/opt/globus-4.0.1/etc/containercert.pem
[globus@nodeB gt4.0.1-all-source-installer]$ export X509_USER_KEY=/opt/globus-4.0.1/etc/containerkey.pem

Now as user 'globus' create a proxy certificate:

[globus@nodeB gt4.0.1-all-source-installer]$ grid-proxy-init
Your identity: /O=Grid/OU=GlobusTest/CN=host/nodeb.ps.univa.com
Creating proxy ........................................... Done
Your proxy is valid until: Fri Feb 24 02:16:13 2006

Now stop the container on nodeB:

[globus@nodeB gt4.0.1-all-source-installer]$ globus-stop-container

Before building the PBS jobmanager you need to make sure the the PBS commands are in the path for the globus user:

[globus@nodeB ]$ export PATH=/opt/pbs/bin:$PATH
[globus@nodeB ]$ which qsub
/opt/pbs/bin/qsub
[globus@nodeB gt4.0.1-all-source-installer]$ which qstat
/opt/pbs/bin/qstat
[globus@nodeB gt4.0.1-all-source-installer]$ which pbsnodes
/opt/pbs/bin/pbsnodes

You also need to set the PBS_HOME environment variable to point to the directory where PBS writes the server log files. If you followed the directions in this tutorial then the directory is /usr/spool/PBS:

When the ls/user/spool/PBS/server_logs/ command is run there may be several log files present and files with names corresponding to the dates when pbs was running. The resulting listing shown is only an example.

[globus@nodeB ~]$ ls /usr/spool/PBS/server_logs/
20060228

[globus@nodeB ~]$ export PBS_HOME=/usr/spool/PBS

The GRAM WS PBS jobmanager is included in the GT 4.0.1 source so you only need to go back to the source distribution directory and build it:

[globus@nodeB ~]$ cd gt4.0.1-all-source-installer
[globus@nodeB gt4.0.1-all-source-installer]$ make gt4-gram-pbs
[globus@nodeB gt4.0.1-all-source-installer]$ make install
running /opt/globus-4.0.1/setup/globus/setup-seg-pbs.pl..[ Changing to /opt/globus-4.0.1/setup/globus ]
..Done
running /opt/globus-3.0.1/setup/globus/setup-globus-scheduler-provider-pbs..[ Changing to /opt/globus-4.0.1/setup/globus ]
checking for pbsnodes... /opt/pbs/bin/pbsnodes
checking for qstat... /opt/pbs/bin/qstat
find-pbs-provider-tools: creating ./config.status
config.status: creating /opt/globus-4.0.1/libexec/globus-scheduler-provider-pbs
..Done
running /opt/globus-4.0.1/setup/globus/setup-gram-service-pbs..[ Changing to /opt/globus-4.0.1/setup/globus ]
Running /opt/globus-4.0.1/setup/globus/setup-gram-service-pbs
..Done

The last step is to configure the jobmanager so that it knows that rsh is being used:

[globus@nodeB globus]$ cd $GLOBUS_LOCATION/setup/globus
[globus@nodeB globus]$ ./setup-globus-job-manager-pbs --remote-shell=rsh
find-pbs-tools: WARNING: "Cannot locate mpiexec"
find-pbs-tools: WARNING: "Cannot locate mpirun"
checking for mpiexec... no
checking for mpirun... no
checking for qdel... /opt/pbs/bin/qdel
checking for qstat... /opt/pbs/bin/qstat
checking for qsub... /opt/pbs/bin/qsub
checking for rsh... /usr/kerberos/bin/rsh
find-pbs-tools: creating ./config.status
config.status: creating /opt/globus-4.0.1/lib/perl/Globus/GRAM/JobManager/pbs.pm

Next >