| 179 | * 3. Starting Globus container[[BR]][[BR]] |
| 180 | * After you install and set up on the DRBL server and clients successfully, you can start the webservices container to test if Globus works well. Globus Toolkit is installed based on DRBL, so its installation directory is shared on all machines. For example, if you install PBS on node1 and install SGE on node2 and build the WS GRAM PBS jobmanager and the WS GRAM SGE jobmanager to be included in Globus webservices container, you should follow the steps. [[BR]][[BR]] |
| 181 | {{{ |
| 182 | node1: |
| 183 | (1) move $GLOBUS_LOCATION/etc/globus_wsrf_gram_SGE to other directories (ex:$GLOBUS_LOCATION/) |
| 184 | (2) start Globus container |
| 185 | (3) move $GLOBUS_LOCATION/globus_wsrf_gram_SGE back to $GLOBUS_LOCATION/etc/ |
| 186 | }}} |
| 187 | {{{ |
| 188 | node2: |
| 189 | (1) move $GLOBUS_LOCATION/etc/globus_wsrf_gram_PBS to other directories (ex:$GLOBUS_LOCATION/) |
| 190 | (2) start Globus container |
| 191 | (3) move $GLOBUS_LOCATION/globus_wsrf_gram_PBS back to $GLOBUS_LOCATION/etc/ |
| 192 | }}} |
| 193 | * In this way, you can successfully start the WS GRAM PBS jobmanager on node1, not on node2. And you can also successfully start the WS GRAM SGE jobmanager on node2, not on node1. |
| 194 | {{{ |
| 195 | root@node1:~# ps aux | grep pbs |
| 196 | root 11941 0.0 0.0 4584 1100 ? S Oct06 0:00 /usr/local/globus-4.2.0/libexec/globus-scheduler-event-generator -s pbs -t 1197005617 |
| 197 | }}} |
| 198 | {{{ |
| 199 | root@node2:~# ps aux | grep sge |
| 200 | root 11943 0.0 0.0 4588 1000 ? S Oct06 0:01 /usr/local/globus-4.2.0/libexec/globus-scheduler-event-generator -s sge -t 1223308213 |
| 201 | }}} |
| 202 | |