Difference: BasicUsage (7 vs. 8)

Revision 82008-11-04 - AndrasLaszlo

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

How to submit simple jobs onto the Grid

Line: 20 to 20
  setenv X509_USER_KEY /some_directory/globus/userkey.pem (for tcsh).
Changed:
<
<		To customize the Grid behavior, the environmental variable EDG_WL_UI_CONFIG_VAR can be used to point to a configuration file file, like:
>
>		By default, a directory called .glite should be present in your home directory. If, for whatever reason you wish to relocate this directory, you should tell this to the Grid system using the following environmental variables:
 
Changed:
<
<		export EDG_WL_UI_CONFIG_VAR=/some_directory/edg.conf (for bash), or
>
>		export GLITE_USER_HOME=/some_directory/glite (for bash), or
 
Changed:
<
<		setenv EDG_WL_UI_CONFIG_VAR /some_directory/edg.conf (for tcsh).
>
>		setenv GLITE_USER_HOME /some_directory/glite (for tcsh).
 
Changed:
<
<		The default version of the file edg.conf may be obtained from /opt/edg/etc/edg_wl_ui_cmd_var.conf on any UI machine.
>
>		To customize the Grid behavior, the environmental variable GLITE_WMSUI_CONFIG_VAR can be used to point to a configuration file, like:

export GLITE_WMSUI_CONFIG_VAR=/some_directory/glite_wms.conf (for bash), or

setenv GLITE_WMSUI_CONFIG_VAR /some_directory/glite_wms.conf (for tcsh).

The default version of the file glite_wms.conf may be obtained from /opt/glite/etc//glite_wms.conf on any UI machine. (However, the prefix /opt may be different on various platforms, if non-standard installation directory is used for GLite.)

 

Log onto the Grid (get authenticated on the Grid)

Line: 34 to 40
  > grid-proxy-init Here, you will be prompted for your grid password. Or:
Changed:
<
<		> grid-proxy-init  -valid 4:00 This is the same, but the authentication will expire in 4 hours. The default (and maximum) lifetime is 12 hours.
>
>		> grid-proxy-init  -valid 04:00 This is the same, but the authentication will expire in 4 hours. The default (and maximum) lifetime is 12 hours.
  If you are member of more then one VO, you can choose between them by using the voms-proxy-init for logging in, instead of grid-proxy-init command. E.g.:

> voms-proxy-init  -voms hungrid Or:

Changed:
<
<		> voms-proxy-init  -voms hungrid  -valid 4:00
>
>		> voms-proxy-init  -voms hungrid  -valid 04:00
  To get information on your user proxy, you can use the commands grid-proxy-info or voms-proxy-info  -all. You can destroy your user proxy by grid-proxy-destroy or voms-proxy-destroy.
Line: 49 to 55
  This means getting a so called job proxy. Commands are:
Changed:
<
<		> myproxy-init Here, you will be prompted for your grid password, and to specify an additional password (for extra protection) attached to your so called job proxy, to be created.

> myproxy-init  -n This is the same, but you won't be asked to specify an additional password for protecting your job proxy.

>
>		> myproxy-init  -d  -n Here, you will be prompted for your grid password.
 
Changed:
<
<		Running myproxy-init is necessary when you are running long-term jobs. Having a job proxy ensures that your jobs still will be authenticated on the Grid, even though your user proxy (used to perform interactive Grid manupulations) may have had expired. You can get information on your job proxy by myproxy-info. You can destroy your job proxy by myproxy-destroy. The default (and maximum) lifetime of a job proxy is 168 hours.
>
>		Running myproxy-init is necessary when you are running long-term jobs. Having a job proxy ensures that your jobs still will be authenticated on the Grid, even though your user proxy (used to perform interactive Grid manupulations) may have had expired. You can get information on your job proxy by myproxy-info  -d. You can destroy your job proxy by myproxy-destroy  -d. The default (and maximum) lifetime of a job proxy is 168 hours.
  Note: If you don't get a job proxy, you may not be able to retrieve your job outputs for long-term jobs!

Prepare and submit your job

Changed:
<
<		The programme which you want to run on the Grid is called a job. These consist of some executable(s) and some input(s), which can be submitted to the Grid system. The result shall be some output(s), which can be retrieved after your job has finished.
>
>		The program which you want to run on the Grid is called a job. These consist of some executable(s) and some input(s), which can be submitted to the Grid system. The result shall be some output(s) and error(s), which can be retrieved after your job has finished.
  The job specifications are described for the Grid system by the so called Job Description Language (JDL). For each of your jobs, you should prepare a JDL file. An example for a typical simple JDL file content may be:
Line: 71 to 75
  Executable = "testjob.sh";
Changed:
<
<		 StdOutput = "testjob.stdout";
>
>		 StdOutput = "testjob.stdoutanderror";
 
Changed:
<
<		 StdError = "testjob.stdout";
>
>		 StdError = "testjob.stdoutanderror";
  InputSandbox = {"testjob.sh", "inputfile.dat"};
Changed:
<
<		 OutputSandbox = {"testjob.stdout", "outputfile.dat"};
>
>		 OutputSandbox = {"testjob.stdoutanderror", "outputfile.dat"};
  Requirements = ( Member("AFS", other.GlueHostApplicationSoftwareRunTimeEnvironment) &&
Line: 100 to 104
  Once you prepared the JDL file, you can look for the available queues, which are capable of running your job, by the command:
Changed:
<
<		> edg-job-list-match -vo your_vo testjob.jdl
>
>		> glite-wms-job-list-match --vo your_vo testjob.jdl
  This will return a list of Grid queues (computing elements), which are capable of executing your job.

The job can be submitted by the command:

Changed:
<
<		> edg-job-submit -vo your_vo testjob.jdl
>
>		> glite-wms-job-submit --vo your_vo -a testjob.jdl
  This will return a sURL address, which is a unique identifier of your job, which shall be denoted by jobID in the followings.

The status of the job can be viewed by:

Changed:
<
<		> edg-job-get-status jobID
>
>		> glite-wms-job-status jobID
  This will return the current status of your job.

If your job has failed to be ran by the Grid system, the logging may be retrieved by:

Changed:
<
<		> edg-job-get-logging-info jobID
>
>		> glite-wms-job-logging-info jobID
  This will return the logging info on your job. A convenient way to find out failure reasons is:
Changed:
<
<		> edg-job-get-logging-info -v 2 jobID > log
> grep "reason" log | uniq
>
>		> glite-wms-job-logging-info -v 3 jobID | grep "reason" | uniq
 
Changed:
<
<		This will return all the available logging info on your job (-v 2 switch), and shall write it into the file log. The second command line lists the unique lines of the file log, containing the string reason, which will tell the reasons for various actions of the Grid system.
>
>		This will return all the available most detailed logging info on your job, and shall print lines containing the string "reason", furthermore shall suppress multiple printing of consecutive identical lines.
  If your job has properly finished, you can retrieve the outputs by the command:
Changed:
<
<		> edg-job-get-output jobID
>
>		> glite-wms-job-output jobID
  This will retrieve the content of the OutputSandbox into the directory /tmp/jobOutput/yourusername_jobID. It is also possible to specify some other directory name by the --dir switch.
Changed:
<
<		For further information, look at the man pages of the above commands, and maybe also to the man pages of other edg- commands. For further references on simple job submission, see https://edms.cern.ch/file/454439//LCG-2-UserGuide.html. Also a complete description of the JDL language is available there.
>
>		For further information, look at the man pages of the above commands, and maybe also to the man pages of other glite-wms- commands. For further references on simple job submission, see https://edms.cern.ch/file/722398//gLite-3-UserGuide.pdf. Also a complete description of the JDL language is available there.
 

Changed:
<
<		-- AndrasLaszlo - 17 Sep 2007
>
>		-- AndrasLaszlo - 4 Nov 2008
View topic | History: r15 < r14 < r13 < r12 | More topic actions...
 
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