Difference: SimpleOSGJobSubmission ( vs. 1)

Revision 12009/06/11 - Main.BruceThayre

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

Simple OSG Job Submission

Written by Terrence Martin
Monday, 30 January 2006
This document is the next step after getting your DOE grid certificate and grabbing your first proxy.


Making a simple job submission to OSG Condor


Before you start make sure you run voms-proxy-init so you have an up to date proxy.



1. Login to your submission host (eg. cms.t2.ucsd.edu)

1. mkdir ~/osg
2. cd ~/osg
3. Open your favorite editor on the file test.cmd
4. write the following condor script to test.cmd:

universe=globus
GlobusScheduler? =osg-gw-2.t2.ucsd.edu:/jobmanager-condor
executable=/bin/env
stream_output = False
stream_error = False
output = test1.out
error = test1.err
log = test1.log
queue

1. Save and close the editor
2. Make sure you have sourced your environment for OSG submission and gotten your voms-proxy. See above for instructions on doing that
3. Submit the job by running

condor_submit test.cmd

The job should complete in a few minutes to a couple of hours, check your status in the local condor queue with condor_q. A R means that your job is running on the remove host. If the job completes successfully you will see the environment the job ran under in test1.out. Any errors are in test1.err and the globus log will be in test1.log.
Additional Condor Tips

The condor documentation linked to from here provides much more detailed information on more complex test.cmd.

However here are some often used examples

Arguments

universe=globus
GlobusScheduler? =osg-gw-2.t2.ucsd.edu:/jobmanager-condor
executable=/bin/ls
arguments=/tmp
stream_output = False
stream_error = False
output = test1.out
error = test1.err
log = test1.log
queue

This will display the contents of /tmp

Submitting Multiple Jobs

universe=globus
GlobusScheduler? =osg-gw-2.t2.ucsd.edu:/jobmanager-condor
executable=/bin/ls
stream_output = False
stream_error = False

arguments=/tmp
output = test1.out
error = test1.err
log = test1.log
queue

arguments=/usr
output = test2.out
error = test2.err
log = test2.log
queue

arguments=/var
output = test3.out
error = test3.err
log = test3.log
queue

arguments=/etc
output = test4.out
error = test4.err
log = test4.log
queue

This will submit 4 seperate jobs each with their own output files and arguments.

Submitting Files with your jobs and getting a file back

Although it is preferred to use staging systems like srmcp to move large amounts of data back and forth from your job sometimes you need to transfer small files in and out of the batch system. Condor-g supports this via thetransfer_input_files and transfer_output_files options.

universe=globus
GlobusScheduler? =osg-gw-2.t2.ucsd.edu:/jobmanager-condor
executable=/bin/cp
stream_output = False
stream_error = False
WhenToTransferOutput? = ON_EXIT
transfer_files = ONEXIT
transfer_output = true
transfer_input_files = /bin/ps,/bin/hostname
transfer_output_files = myoutput.txt

arguments=-fv /etc/group myoutput.txt
output = ./test.out
error = ./test.err
log = ./test.log
queue

-- BruceThayre - 2009/06/11

 
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