Personal Grid
From Java CoG Kit
Please note we have not tested this recently, please help us reporting if this still works.
Contents |
Setup
The Java CoG Project has 100% Java executables of some popular Globus client tools. This includes a prototype of the personal gatekeeper that is Globus protocol 2.0 compliant. This actually should also work on a windows machine within cygwin.
Make usre you set the COG_INSTALL_PATH and the JAVA_HOME variable in your shell rc file. Than add the
$JAVA_HOME/bin
and
$COG_INSTALL_PATH
to your $PATH environment
Use the "cog-setup" GUI to set up your Globus environment. This requires that you have already applied for your Globus Certificate.
Creating a Grid Proxy
Use the "visual-grid-proxy-init" tool to create a proxy. You should not use the Java "grid-proxy-init" because it doesn't hide your password when you type it into the Unix shell.
Running a Personal Gatekeeper
The Globus Personal Gatekeeper allows you to run GRAM jobs on any machine you have JGlobus installed on. This can be achieved as follows:
- Log into the machine you already have your JGlobus environment set up in.
- Perform a "visual-grid-proxy-init". You may want to specify a longer "Proxy lifetime" to keep your gatekeeper alive longer.
- Run the "screen" program. This will keep your session running after you logout.
- Start the "globus-personal-gatekeeper". Use "globus-personal-gatekeeper &" to run the job in the background. You will receive a contact string.
- Copy down the contact string. It will look something like: "128.123.45.657:2119:/O=Grid/O=Globus/OU=mcs.anl.gov/CN=Gregor". Be warned that the IP address may be wrong. It is best to replace the IP address with the fully qualified hostname of the machine. For our example we assume the machine name is hot.mcs.anl.gov.
- Detach yourself from your Screen program by typing "Ctrl-a, Ctrl-d"
- Logout of your session.
Submitting a job
- From another machine where you have a valid Grid proxy, try submitting a job. An example of this is:
> globus-job-run "hot.mcs.anl.gov:2119:/O=Grid/O=Globus/OU=mcs.anl.gov/CN=Gregor" /bin/date
- This will return something like
Mon Nov 11 12:29:06 CST 2002
- Please do not forget to kill of your "globus-personal-gatekeeper" when you are done with it. To do this, you should log back into the machine you started the personal gatekeeper on, issue a "screen -r", and do a "killall java" (or more elegant solution if you prefer).
- Naturally, if the machine you are running the personal gatekeeper is rebooted, you will loose your gatekeeper.
Running a Personal GASS Server
If you need a quick and simple way to copy files to a another host that doesn't have GridFTP installed, use the "globus-gass-server" to start up a personal version of a GASS server. The setup of the server is almost the exact same as the personal gatekeeper setup.
- Log into the machine you already have your JGlobus environment set up in.
- Perform a "visual-grid-proxy-init". You may want to specify a longer "Proxy lifetime" to keep your gatekeeper alive longer.
- Run the "screen" program. This will keep your session running after you logout.
- Start the "globus-gass-server". Use "globus-gass-server &" to run the job in the background. You will receive a contact string for the GASS server.
- Copy down the contact string. It will look something like: "https://123.456.78.901:54485". Be warned that the IP address may be wrong. It is best to replace the IP address with the fully qualified hostname. We assume for our example that it is hot.mcs.anl.gov.
- Detach yourself from your Screen program by typing "Ctrl-a, Ctrl-d"
- Logout of your session.
- From another machine where you have a valid Grid proxy, try submitting a job. An example of this is:
> globus-url-copy file:///etc/fstab https://123.456.78.901:54485//tmp/gregor
- Please do not forget to kill of your "globus-personal-gatekeeper" when you are done with it. To do this, you should log back into the machine you started the personal gatekeeper on, issue a "screen -r", and do a "killall java" (or more elegant solution if you prefer).
- Naturally, if the machine you are running the personal GASS server is rebooted, you will loose your service.
