Globus Installation Acceptance Document

The following sections outline a sufficient set of actions that can be used to confirm that the required Globus components are installed and configured correctly. These tests focus on the areas of credential management, job migration, and data staging.

Credential Management

CA Certificate Setup Confirmation

To verify that the SimpleCA certificate is installed in /etc/grid-security/certificates and that your certificate is in place with the correct permissions, run:


user$ grid-proxy-init -debug -verify

Correct configuration will result in an output like the following:

User Cert File: /home/user/.globus/usercert.pem
User Key File: /home/user/.globus/userkey.pem

Trusted CA Cert Dir: /etc/grid-security/certificates

Output File: /tmp/x509up_u1817
Your identity: /O=Grid/OU=GlobusTest/OU=simpleCA-mayed.mcs.anl.gov/OU=mcs.anl.gov/CN=User
Name
Enter GRID pass phrase for this identity:
Creating proxy ..............................++++++++++++
...............++++++++++++
Done
Proxy Verify OK
Your proxy is valid until: Sat Mar 20 03:01:46 2004

Data Staging

Grid FTP

Telnet Test

Once the Grid FTP server is running, port 2811 should be open on the server machine. Use the telnet command to confirm access to confirm that this port is accessible. The telnet output should resemble the following:

Telnet

% telnet localhost 2811
                Trying 127.0.0.1...
                Connected to localhost.
                Escape character is '^]'.
                220 GridFTP Server somehost.org 2.0 (gcc32dbg, 1113865414-1) ready.

Testing File Transfer

Next, confirm that files can be transfered between hosts using globus-url-copy. First off, confirm file transfers from the remote server to the local machine are working (hit ctl-c to stop).

globus-url-copy -vb -dbg gsiftp://host.server,running.on/dev/zero file:///dev/null

Next, confirm file transfers from the local host to the remote machine work (hit ctl-c to stop).

globus-url-copy -vb -dbg file:///dev/zero gsiftp://host.server.running.on/dev/null

Finally, you can test third-party file transfers with the following command (ctl-c to stop).

globus-url-copy -vb -dbg gsiftp://host.server1.on/dev/zero
gsiftp://host.server2.on/dev/null

Job Migration

Local Job Submission

The following test will confirm that jobs can be submitted to and run on the local host. First, confirm that the server isrunning and listening on the expected port by executing the following on the machine running the Globus Gatekeeper service:

telnet localhost 2119

The output should look like the following (press ctl-c to exit).

Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.

Next, submit a local job by executing the following:

globus-job-run localhost /bin/date

The resulting output should be the same as running the /bin/date command by itself.

Remote Job Submission

The following test will confirm that jobs can be submitted to and run on a remote host. First, confirm that the Gatekeeper service is running on the host by issuing the telnet command.

telnet remotehost.org 2119

Again, the output should look like the following (press ctl-c to exit).

Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.

Now test a remote job submission by executing the following:

globus-job-run remotehost.org /bin/date

Again, the resulting output should be the same as running the /bin/date command by itself.


	Learn More About Us Product Information Access Portal Demo Highlighted Customers Training Documentation News Download Moab Cluster Suite ·Customer Download ·Eval Download ·Access Portal Demo Moab Grid Suite ·Customer Download ·Eval Download Maui TORQUE Purchase Products Support Other Services Authorized Resellers Support Customer Support Purchase Support Evaluation Support Documentation Mailing List Contact Us Product Information Sales Technical Support Free Eval Support Partner Press
Home Products Services Resources Partners Press News Company	Globus Installation Acceptance Document Globus Installation Acceptance Document The following sections outline a sufficient set of actions that can be used to confirm that the required Globus components are installed and configured correctly. These tests focus on the areas of credential management, job migration, and data staging. Credential Management CA Certificate Setup Confirmation To verify that the SimpleCA certificate is installed in /etc/grid-security/certificates and that your certificate is in place with the correct permissions, run: user$ grid-proxy-init -debug -verify Correct configuration will result in an output like the following: User Cert File: /home/user/.globus/usercert.pem User Key File: /home/user/.globus/userkey.pem Trusted CA Cert Dir: /etc/grid-security/certificates Output File: /tmp/x509up_u1817 Your identity: /O=Grid/OU=GlobusTest/OU=simpleCA-mayed.mcs.anl.gov/OU=mcs.anl.gov/CN=User Name Enter GRID pass phrase for this identity: Creating proxy ..............................++++++++++++ ...............++++++++++++ Done Proxy Verify OK Your proxy is valid until: Sat Mar 20 03:01:46 2004 Data Staging Grid FTP Telnet Test Once the Grid FTP server is running, port 2811 should be open on the server machine. Use the telnet command to confirm access to confirm that this port is accessible. The telnet output should resemble the following: Telnet % telnet localhost 2811 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 GridFTP Server somehost.org 2.0 (gcc32dbg, 1113865414-1) ready. Testing File Transfer Next, confirm that files can be transfered between hosts using globus-url-copy. First off, confirm file transfers from the remote server to the local machine are working (hit ctl-c to stop). globus-url-copy -vb -dbg gsiftp://host.server,running.on/dev/zero file:///dev/null Next, confirm file transfers from the local host to the remote machine work (hit ctl-c to stop). globus-url-copy -vb -dbg file:///dev/zero gsiftp://host.server.running.on/dev/null Finally, you can test third-party file transfers with the following command (ctl-c to stop). globus-url-copy -vb -dbg gsiftp://host.server1.on/dev/zero gsiftp://host.server2.on/dev/null Job Migration Local Job Submission The following test will confirm that jobs can be submitted to and run on the local host. First, confirm that the server isrunning and listening on the expected port by executing the following on the machine running the Globus Gatekeeper service: telnet localhost 2119 The output should look like the following (press ctl-c to exit). Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. Next, submit a local job by executing the following: globus-job-run localhost /bin/date The resulting output should be the same as running the /bin/date command by itself. Remote Job Submission The following test will confirm that jobs can be submitted to and run on a remote host. First, confirm that the Gatekeeper service is running on the host by issuing the telnet command. telnet remotehost.org 2119 Again, the output should look like the following (press ctl-c to exit). Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. Now test a remote job submission by executing the following: globus-job-run remotehost.org /bin/date Again, the resulting output should be the same as running the /bin/date command by itself.
© 2001-2008 Cluster Resources, Incorporated