Difference: BasicUsage (11 vs. 12)

Revision 122010-09-10 - BenceSomhegyi

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

How to submit simple jobs onto the Grid

Line: 40 to 40
 

Log onto the Grid (get authenticated on the Grid)

Deleted:
<
<
This means getting a so called user proxy. Commands are:

> grid-proxy-init Here, you will be prompted for your grid password. Or:

> 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 glite-voms-proxy-init for logging in, instead of grid-proxy-init command. E.g.:
Changed:
<
<
> glite-voms-proxy-init -voms hungrid Or:
>
>
> glite-voms-proxy-init -voms hungrid Or:
 
Changed:
<
<
> glite-voms-proxy-init -voms hungrid -valid 04:00
>
>
> glite-voms-proxy-init -voms hungrid -valid 04:00
  To get information on your user proxy, you can use the commands grid-proxy-info or glite-voms-proxy-info -all. You can destroy your user proxy by grid-proxy-destroy or glite-voms-proxy-destroy.
Line: 58 to 52
  This means getting a so called job proxy. Commands are:
Changed:
<
<
> myproxy-init -d -n Here, you will be prompted for your grid password.
>
>
> myproxy-init -d -n Here, you will be prompted for your grid password.
  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.
Line: 88 to 82
  Requirements = ( Member("AFS", other.GlueHostApplicationSoftwareRunTimeEnvironment) && other.GlueCEPolicyMaxWallClockTime>=2160 &&
Changed:
<
<
other.GlueHostMainMemoryRAMSize>=512
>
>
other.GlueHostMainMemoryRAMSize>=512 && RegExp ("kfki.hu", other.GlueCEUniqueID);
  );

]

Line: 100 to 95
 
Executable
This variable specifies the executable file of your job.
StdOutput
The StdOut of your program shall be written into this file.
StdError
The StdError of your program shall be written into this file.
Changed:
<
<
InputSandbox
This is a list of files, which are sent to the system as the components of your job. Typically the executable of your program, and some supplementary files. The size of the files, sent via the InputSandbox, should be small (<10MegaBytes). Large files (as large input data files) should be communicated to the job by other ways, e.g. via AFS, NFS, or http (using e.g. wget), or via the Grid Storage System.
OutputSandbox
This is a list of files, which are retrieved after the job has finished. Typically the file containing the StdOut / StdError and some output files. The size of the files, retrieved via OutputSandbox, should be small (<100MegaBytes). Large files (as large output data files) should be transfered by other means, e.g. via the Grid Storage System.
Requirements
This optional variable may be a logical expression, specifying requirements for site or the node, where the job is going to be executed. Member("Some_software", other.GlueHostApplicationSoftwareRunTimeEnvironment) means the requirement of the software Some_software on the target node. other.GlueCEPolicyMaxWallClockTime>=running_time means the requirement for such queues, where the job execution time limit is larger than the specified running_time (in minutes). The requirement other.GlueHostMainMemoryRAMSize>=memory means requirement for such execution nodes, which have larger memory than the specified memory amount (in MegaBytes). A requirement of the form other.GlueCEUniqueID=="grid109.kfki.hu:2119/jobmanager-lcgpbs-hungrid" would mean the requirement that the job should be sent to the computing element (queue) grid109.kfki.hu:2119/jobmanager-lcgpbs-hungrid.
>
>
InputSandbox
This is a list of files, which are sent to the system as the components of your job. Typically the executable of your program, and some supplementary files. The size of the files, sent via the InputSandbox, should be small (<10MegaBytes). Large files (as large input data files) should be communicated to the job by other ways, e.g. via AFS, NFS, or http (using e.g. wget), or via the Grid Storage System.
OutputSandbox
This is a list of files, which are retrieved after the job has finished. Typically the file containing the StdOut / StdError and some output files. The size of the files, retrieved via OutputSandbox, should be small (<100MegaBytes). Large files (as large output data files) should be transfered by other means, e.g. via the Grid Storage System.
Requirements
This optional variable may be a logical expression, specifying requirements for site or the node, where the job is going to be executed. Member("Some_software", other.GlueHostApplicationSoftwareRunTimeEnvironment) means the requirement of the software Some_software on the target node. other.GlueCEPolicyMaxWallClockTime>=running_time means the requirement for such queues, where the job execution time limit is larger than the specified running_time (in minutes). The requirement other.GlueHostMainMemoryRAMSize>=memory means requirement for such execution nodes, which have larger memory than the specified memory amount (in MegaBytes). A requirement of the form RegExp("kfki.hu", other.GlueCEUniqueID) means, that the job should be sent to a KFKI computing element (either grid107.kfki.hu or grid109.kfki.hu).
  Once you prepared the JDL file, you can look for the available queues, which are capable of running your job, by the command:
> glite-wms-job-list-match  --vo your_vo  testjob.jdl
Changed:
<
<
This will return a list of Grid queues (computing elements), which are capable of executing your job.
>
>

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

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:
> glite-wms-job-status  jobID
Changed:
<
<
This will return the current status of your job.
>
>

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:
> glite-wms-job-logging-info  jobID
Changed:
<
<
This will return the logging info on your job. A convenient way to find out failure reasons is:
>
>

This will return the logging info on your job. A convenient way to find out failure reasons is:

 > glite-wms-job-logging-info -v 3 jobID | grep "reason" | uniq
Changed:
<
<
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.
>
>

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:
> glite-wms-job-output  jobID
Changed:
<
<
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 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.
>
>
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.
 
Added:
>
>
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.
  -- AndrasLaszlo - 10 Jul 2009 \ No newline at end of file
 
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