The Globus Consortium

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

Building and Installing

Installing Updated Packages

Creating a Certificate Authority

Obtaining a Host Certificate on nodeB

Making a Copy for the Container

Creating the grid-mapfile

Configuring the RFT Service

Configuring sudo

Starting the Container

Starting globus-gridftp-server

Repeat for nodeA

Obtaining Credentials for Generic User

Testing the Grid Services on nodeB

Obtaining host credentials for nodeA

Testing globus-gridftp-server on nodeA

Testing file staging

Completing Deployment on nodeC

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

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

Ch. 9 - A Distributed Grid Application

Chapter 6: Deploying The Globus Toolkit 4.0.x

Completing Deployment on nodeC

At this point all the services are running and tested on nodeB, and we have a generic user configured on nodeA to be able to run jobs, including jobs that involve the staging of files.

You should go back through this chapter and repeat the necessary steps to deploy Globus on nodeC. Again you do not need to create a new certificate authority--you only need the one available and owned by the 'globus' user on nodeB. But you will need to get host certificates for nodeC and make a copy that the container on nodeC can use.

When you use use the 'grid-ca-sign' command to sign the certificate that you copied over from nodeC you will need to run it with the -force option.

You should be able to run all the tests of services in this chapter on nodeC that you ran on nodeA. Simply replace "nodec" with "nodea" in the URLs used on the command line for globus-url-copy and globusrun-ws.

< Back

© 2006 - Globus Consortium