Users gLite CE

From Begrid Wiki
Jump to navigationJump to search

Overview

With glite-ce-* commands, you can send your jobs directly to given CE.

Certificate Usage

Explanations are the same as for the glite-wms-* commands (here).

JDL

Explanations are the same as for the glite-wms-* commands (here).

Submission

To submit a job, just use this:

 glite-ce-job-submit -a -r <target_resource> <your_jdl_file>

The <target_resource> is specified like this :

<full_hostname>:<port_number>/cream-<service>-<queue_name>

where <service> identifies the underlying resource management system (e.g. lsf, pbs, etc.). For example :

 $ glite-ce-job-submit -a -r cream02.iihe.ac.be:8443/cream-pbs-beapps job.jdl
2016-02-09 14:44:44,459 WARN - VirtualOrganisation specified in the JDL but overriden with [beapps]
https://cream02.iihe.ac.be:8443/CREAM979231935

The output gives you the jobID:

https://cream02.iihe.ac.be:8443/CREAM979231935

You will need this jobID in the following steps to monitor your job and get its ouput when it's finished.

Monitoring

You can follow the different steps of your job execution with:

 glite-wms-job-status <jobID>

Example of output:

 $ glite-ce-job-status https://cream02.iihe.ac.be:8443/CREAM979231935
 
******  JobID=https://cream02.iihe.ac.be:8443/CREAM979231935
	Status        = [IDLE]

Fetching Outputs

When your job has reached the "DONE-OK" status, you are able to retrieve the output files (the ones you specified in the ouput sandbox of the jdl file). Use this command:

 glite-ce-job-output --dir <path to where you want your outputs> <jobID>


Template:TracNotice