Difference: GridServices (14 vs. 15)

Revision 152018-01-19 - GordonStewart

  META TOPICPARENT 
 name="WebHome" 

 Grid Services
- META TOPICPARENT
+ name="WebHome"
 To use grid resources, you will need a certificate, from which you can generate a proxy certificate.  The proxy certificate has a relatively short lifetime, and is used to actually submit the job.  A proxy is associated with a particular Virtual Organisation (VO), for example vo.scotgrid.ac.uk, which is selected when it is created.  You can generate a proxy using the arcproxy command:
-<
<
+arcproxy -S <VO_ALIAS> -N
->
>
+$ arcproxy -S <VO_ALIAS> -N
 For example, to generate a proxy for the vo.scotgrid.ac.uk VO:
-<
<
+arcproxy -S vo.scotgrid.ac.uk -N
->
>
+$ arcproxy -S vo.scotgrid.ac.uk -N
Your identity: /C=UK/O=eScience/OU=Glasgow/L=Compserv/CN=bugs bunny
Contacting VOMS server (named vo.scotgrid.ac.uk): voms.gridpp.ac.uk on port: 15509
Proxy generation succeeded
Your proxy is valid until: 2018-01-19 23:36:59
  Job description (xRSL)
 Jobs are submitted using the arcsub command:
-<
<
+arcsub -j <DATABASE_FILENAME> -c <CE_HOSTNAME> <XRSL_FILENAME>
->
>
+$ arcsub -c <CE_HOSTNAME> <XRSL_FILENAME>
 For example, to submit test.xrsl to svr011 at Glasgow:
-<
<
+arcsub -j test.db -c svr011.gla.scotgrid.ac.uk test.xrsl
->
>
+$ arcsub -c svr011.gla.scotgrid.ac.uk test.xrsl
Job submitted with jobid: gsiftp://svr011.gla.scotgrid.ac.uk:2811/jobs/NCKLDmEQkwrnZ4eC5pmRAbBiTBFKDmABFKDmpMFKDmABFKDmQffBxy
->
>
+When a job is submitted successfully, you will be presented with its job ID which can be used to refer to the job later.  Information about submitted jobs is also recorded in a job list file; by default, this file is ~/.arc/jobs.dat (~/.arc/jobs.xml with some versions of ARC), but you can choose a different location by supplying the -j argument to arcsub:

$ arcsub -j <JOBLIST_FILENAME> -c <CE_HOSTNAME> <XRSL_FILENAME>


For example:

$ arcsub -j test.dat -c svr011.gla.scotgrid.ac.uk test.xrsl


 Querying the status of a job 

You can obtain information about the status of jobs using the arcstat command:

$ arcstat <JOB_ID>


For example, to obtain information about the job submitted in the previous step:

$ arcstat gsiftp://svr011.gla.scotgrid.ac.uk:2811/jobs/NCKLDmEQkwrnZ4eC5pmRAbBiTBFKDmABFKDmpMFKDmABFKDmQffBxy
Job: gsiftp://svr011.gla.scotgrid.ac.uk:2811/jobs/NCKLDmEQkwrnZ4eC5pmRAbBiTBFKDmABFKDmpMFKDmABFKDmQffBxy
 Name: StageJob
 State: Queuing

Status of 1 jobs was queried, 1 jobs returned information


You may have to wait a few minutes after submitting a job before status information becomes available.

You can also query the status of all jobs in a job list file:

$ arcstat -j <JOBLIST_FILENAME>


 Retrieving job output 

Output and log files for a job can be retrieved using the arcget command.  As when querying the status of a job, you can use either a job ID or a job list file with this command:

$ arcget <JOB_ID>
$ arcget -j <JOBLIST_FILENAME>


For example, to get the output of the job submitted above:

$ arcget gsiftp://svr011.gla.scotgrid.ac.uk:2811/jobs/NCKLDmEQkwrnZ4eC5pmRAbBiTBFKDmABFKDmpMFKDmABFKDmQffBxy
Results stored at: p6vLDmj3kwrnZ4eC3pmXXsQmABFKDmABFKDm9pFKDmABFKDmtVM1wm
Jobs processed: 1, successfully retrieved: 1, successfully cleaned: 1


You will only be able to retrieve job output once the job has finished.

View topic | History: r19 < r18 < r17 < r16 | More topic actions...