Hello,
I would like to ask a few questions about configuring
the working directory created by WS-GRAM for each
GRAM job.
WS-GRAM creates for each job a directory hierarchy under
${GLOBUS_USER_HOME}/.globus/JOB-HASH
This is problematic when we want the job working directory
to be shared among multiple back-end clusters.
This is because this value of the job working directory
causes a contradiction:
1. ${GLOBUS_USER_HOME}/.globus/ must not be
exported because it holds the user's private key
2. ${GLOBUS_USER_HOME}/.globus/ must be
exported because we want the above working
directory to be available to multiple batch systems
(i.e., not co-located with WS-GRAM).
Because users tend to store their cert/key pair under
${GLOBUS_USER_HOME}/.globus/, requirement (1)
cannot be dropped.
However, requirement (2) could be dropped if one could
define the job's working directory not to be under
${GLOBUS_USER_HOME}/.globus/.
My questions are:
1. Is there a way to define the job's working directory to
be in a configurable location? And a related question:
2. Because the scratch directory looks like a good candidate
for the job's working directory, is there a way to use
as job's working directory
$GLOBUS_SCRATCH_DIR/JOB-HASH
instead of
$GLOBUS_USER_HOME/.globus/JOB-HASH
Thank you.
Gabriel
