| |
How to get started on USCMS Testbeds
02-07-2003
USCMS Testbed utilizes the Grid technology for the implementation.
And the whole USCMS is organized as a Virtual Organization (VO).
The following is a quick guide on how to get started on the
USCMS testbeds:
- First, you need to have grid software installed or access to a
machine that has grid software installed. More information on
this can be found at www.globus.org
(currently, Globus Toolkit 2.2 is used at the uscms testbed.).
- Second, you need have a certificate acceptable for the USCMS testbeds.
Currently, USCMS testbeds accept DOESG certificate and will soon
accept KCA certificate from Fermilab. You can find more information on
how to apply for DOESG certificate and KCA certificate by clicking on
the links:
- Quick Guide on DOESG certificate application
- Quick Guide on KCA certificate application and utilization;
(If you have kerberos principal, it is ok).
This usually takes 2-3 days or longer to get a valid certificate.
- Third, after you have successfully got your grid certificate, please
e-mail your DN subject to the USCMS VO Admin. So that he/can update
the entries in the VO Database. You may also e-mail the site contact
person to get him to update the individual gatekeeper grid-mapfile.
- Fourth, you may then run some tests to see if you can successfully
run the jobs once you get notification on your entity has been
updated---put into the grid-mapfile. You may run the following
commands to test:
- Make sure the GLOBUS_LOCATION points to the correct Globus
installation directory. On ramen.fnal.gov at Fermilab, the directory
is /vdt. Then source the environment:
source $GLOBUS_LOCATION/etc/globus-user-env.csh
- Generate a temporary proxy:
(1). For DOESG, use this command:
grid-proxy-init
(2). For KCA, please use:
kca-proxy-init
- Issue a globus-job-run command:
globus-job-run /bin/echo "Hello World!"
Substitute the with a real gatekeeper machine
name, e.g., at Fermilab using ramen.fnal.gov:
globus-job-run ramen.fnal.gov /bin/echo "Hello World!"
- Destroy the proxy when you don't need it any more:
grid-proxy-destroy
Good luck.
|
|