Difference: WmsxExample (9 vs. 10)

Revision 102008-11-04 - AndrasLaszlo

Line: 1 to 1
 
META TOPICPARENT name="WmsxSoftware"

WMSX examples

Changed:
<
<
Note: On certain platforms, file or directory names, given as command line arguments to wmsx-provider.sh or wmsx-requestor.sh, are are only recognized properly, when specified as absolute paths.
>
>
Note: If your home directory is located on AFS, it is advised to source the following shell script before logging on to the Grid:
## Make new .globus directory and export it:
if [[ -d /tmp/$USER/globus ]] ; then chmod -R 755 /tmp/$USER/globus ; fi
rm -rf /tmp/$USER/globus
mkdir -p /tmp/$USER/globus
cp $HOME/.globus/usercert.pem /tmp/$USER/globus/
cp $HOME/.globus/userkey.pem /tmp/$USER/globus/
export X509_USER_CER=/tmp/$USER/globus/usercert.pem
export X509_USER_KEY=/tmp/$USER/globus/userkey.pem
## Make new .glite directory and export it:
if [[ -d /tmp/$USER/glite ]] ; then chmod -R 755 /tmp/$USER/glite ; fi
rm -rf /tmp/$USER/glite
mkdir -p /tmp/$USER/glite
cp -rd $HOME/.glite/vomses /tmp/$USER/glite/
export GLITE_USER_HOME=/tmp/$USER/glite
(for bash), or
## Make new .globus directory and export it:
if ( -d /tmp/$USER/globus ) then
    chmod -R 755 /tmp/$USER/globus
endif
rm -rf /tmp/$USER/globus
mkdir -p /tmp/$USER/globus
cp $HOME/.globus/usercert.pem /tmp/$USER/globus/
cp $HOME/.globus/userkey.pem /tmp/$USER/globus/
setenv X509_USER_CER /tmp/$USER/globus/usercert.pem
setenv X509_USER_KEY /tmp/$USER/globus/userkey.pem
## Make new .glite directory and export it:
if ( -d /tmp/$USER/glite ) then
    chmod -R 755 /tmp/$USER/glite
endif
rm -rf /tmp/$USER/glite
mkdir -p /tmp/$USER/glite
cp -rd $HOME/.glite/vomses /tmp/$USER/glite/
setenv GLITE_USER_HOME /tmp/$USER/glite
(for tcsh). This ensures that the necessary files are accessible even after your AFS tickets expire.
 

Simple job submission with traditional JDL files

Changed:
<
<
Job submission with edg-job-submit is not very straightforward, as the generated job identifier has to be stored, and then the job output retrieval directory has to be resolved by this identifier. To save you from this typing exercise, the WMSX is capable of managing the output retrieval directory for simple jobs.
>
>
Job submission with glite-wms-job-submit is not very straightforward, as the generated job identifier has to be stored, and then the job output retrieval directory has to be resolved by this identifier. To save you from this typing exercise, the WMSX is capable of managing the output retrieval directory for simple jobs.
  You can find a prepared example for this task here: simplejob.tar.gz. To submit the example job, type the following commands.
Line: 21 to 60
 
> voms-proxy-init  -voms your_vo
# If your job is expected to be long, also get long term authentication:
Changed:
<
<
> myproxy-init -n
>
>
> myproxy-init -d -n
 

Submit the job:

> wmsx-provider.sh  workdir
> wmsx-requestor.sh  -vo your_vo
Deleted:
<
<
# If you want to use a backend other than glitewms (possibilities: edg/glite/glitewms/worker): > wmsx-requestor.sh -backend your_backend
 # If your job is expected to be long, also make the WMSX remember your grid password: > wmsx-requestor.sh -remembergrid
# If your job is expected to be long and you are working on AFS, also make the WMSX remember your AFS password:
Line: 44 to 81
 If you are finished, you can stop WMSX, and destroy your Grid authentications:
> wmsx-requestor.sh  -k
Added:
>
>
> killall java # <- This is necessary due to a WMSX bug.
 # If myproxy-init was used, i.e. for long term jobs:
Changed:
<
<
> myproxy-destroy
>
>
> myproxy-destroy -d
 > voms-proxy-destroy
Line: 68 to 106
 
> voms-proxy-init  -voms your_vo
# If your jobs are expected to be long, also get long term authentication:
Changed:
<
<
> myproxy-init -n
>
>
> myproxy-init -d -n
 

Submit the jobs:

> wmsx-provider.sh  workdir
> wmsx-requestor.sh  -vo your_vo
Deleted:
<
<
# If you want to use a backend other than glitewms (possibilities: edg/glite/glitewms/worker): > wmsx-requestor.sh -backend your_backend
 # If your jobs are expected to be long, also make the WMSX remember your grid password: > wmsx-requestor.sh -remembergrid
# If your jobs are expected to be long and you are working on AFS, also make the WMSX remember your AFS password:
Line: 91 to 127
 If you are finished, you can stop WMSX, and destroy your Grid authentications:
> wmsx-requestor.sh  -k
Added:
>
>
> killall java # <- This is necessary due to a WMSX bug.
 # If myproxy-init was used, i.e. for long term jobs:
Changed:
<
<
> myproxy-destroy
>
>
> myproxy-destroy -d
 > voms-proxy-destroy
Line: 113 to 150
 
> voms-proxy-init  -voms your_vo
# If your jobs are expected to be long, also get long term authentication:
Changed:
<
<
> myproxy-init -n
>
>
> myproxy-init -d -n
 

Submit the jobs:

> wmsx-provider.sh  workdir
> wmsx-requestor.sh  -vo your_vo
Deleted:
<
<
# If you want to use a backend other than glitewms (possibilities: edg/glite/glitewms/worker): > wmsx-requestor.sh -backend your_backend
 # If your jobs are expected to be long, also make the WMSX remember your grid password: > wmsx-requestor.sh -remembergrid
# If your jobs are expected to be long and you are working on AFS, also make the WMSX remember your AFS password:
Line: 136 to 171
 If you are finished, you can stop WMSX, and destroy your Grid authentications:
> wmsx-requestor.sh  -k
Added:
>
>
> killall java # <- This is necessary due to a WMSX bug.
 # If myproxy-init was used, i.e. for long term jobs:
Changed:
<
<
> myproxy-destroy
>
>
> myproxy-destroy -d
 > voms-proxy-destroy
Changed:
<
<
-- AndrasLaszlo - 16 Apr 2008
>
>
-- AndrasLaszlo - 04 Nov 2008
 

META FILEATTACHMENT attr="" autoattached="1" comment="Interactive example" date="1208360461" name="interactive.tar.gz" path="interactive.tar.gz" size="529" user="Main.AndrasLaszlo" version="1"
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback