How to set up a gatekeeper with a GRAM job manager
==================================================


The following commands should be executed as root unless otherwise
specified.


Creating gatekeeper configuration
---------------------------------

After installing the globus-gatekeeper package, run

  /usr/share/globus/setup/setup-globus-gatekeeper

in order to create the /etc/globus-gatekeeper.conf configuration file
and the /etc/grid-services directory.


Creating gram-job-manager configuration
---------------------------------------

The Globus gatekeeper is normally used to start a GRAM job manager on
the behalf of a user. After installing the globus-gram-job-manager
package, run

  /usr/share/globus/setup/setup-globus-gram-job-manager

in order to create the /etc/globus-job-manager.conf configuration file
and the /tmp/gram_job_state directory.


Creating a service configuration
--------------------------------

The GRAM job manager needs to have a service configured that runs the
tasks that the globus GRAM job manager accepts. In order to configure
a service first install the corresponding package for your local
resource management system (LRMS). For a small test setup without an
LRMS use the "fork" service.

 - globus-gram-job-manager-setup-condor
 - globus-gram-job-manager-setup-fork
 - globus-gram-job-manager-setup-lsf
 - globus-gram-job-manager-setup-pbs
 - globus-gram-job-manager-setup-sge

After installing one of the packages above, create a service
configuration by running

  /usr/share/globus/globus-job-manager-service -add -s <service-name> -t <type>

where <service-name> is a unique name for the service, and <type> is
the type of service you want to run (condor, fork, lsf, ...).

You can run more than one service in the same gatekeeper as long they
have different server names. The configuration for the service will be
created in /etc/grid-services/<service-name>. The first service you
create will be the default and a symlink /etc/grid-services/jobmanager
will be created that points to its configuration. To later change the
default to a different service change this symlink to point to a
different one.


Starting the service
--------------------

Before starting the service make sure you have a host certificate and
key installed in the right locations and with the right permissions.

 - /etc/grid-security/hostcert.pem
 - /etc/grid-security/hostkey.pem

To start the service, run

  service globus-gatekeeper start

To make the service start automatically at boot, run

  chkconfig globus-gatekeeper on


Testing the service
-------------------

Athentication test against the new gatekeeper - as a non-root user
with a valid user proxy, run

  globusrun -a -r <resource-contact>

where <resource-contact> is the service's contact string. See "man
globusrun" for details.