Htc test grid: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=== HTC grid submission test === First create a proxy and copy it into your home directory: <pre> voms-proxy-init --voms beapps cp -a -p /tmp/x509up_u`id -u` ./ </pre> Why is...") |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 23: | Line 23: | ||
# File transfer behavior | # File transfer behavior | ||
should_transfer_files = yes | |||
when_to_transfer_output = ON_EXIT | |||
# Resource requests | |||
request_cpus = 1 | |||
request_memory = 1024 | |||
request_disk = 10240 | |||
# Optional resource requests | # Optional resource requests | ||
Line 35: | Line 40: | ||
queue | queue | ||
</pre> | </pre> | ||
Don't forget to create the shell script mentioned in the *.sub: | |||
<pre> | |||
#!/bin/bash | |||
sleep 180 | |||
id | |||
pwd | |||
date | |||
/usr/bin/hostname | |||
env | |||
</pre> | |||
And then you submit exactly the same way as for a local submission: | |||
<pre> | |||
condor_submit ce_test.sub | |||
</pre> | |||
The official documentation explaining in details job submission is available [https://htcondor.readthedocs.io/en/latest/users-manual/submitting-a-job.html here]. |
Latest revision as of 10:09, 16 September 2021
HTC grid submission test
First create a proxy and copy it into your home directory:
voms-proxy-init --voms beapps cp -a -p /tmp/x509up_u`id -u` ./
Why is it needed to have your proxy in your homedir? Because it must be available to the schedd and that the /user has also been mounted on the schedd machine for this reason. (The picture that you have to keep in mind here is that you are using a remote schedd that will submit the job on your behalf to the CE.)
Now let's create the *.sub file (ce_test.sub):
# Required for remote HTCondor-CE submission universe = grid use_x509userproxy = true x509userproxy = /user/sgerard/x509up_u20533 grid_resource = condor testumd-htcondorce.iihe.ac.be testumd-htcondorce.iihe.ac.be:9619 # Files executable = ce_test.sh output = ce_test.out error = ce_test.err log = ce_test.log # File transfer behavior should_transfer_files = yes when_to_transfer_output = ON_EXIT # Resource requests request_cpus = 1 request_memory = 1024 request_disk = 10240 # Optional resource requests #+xcount = 4 # Request 4 cores #+maxMemory = 4000 # Request 4GB of RAM #+maxWallTime = 120 # Request 2 hrs of wall clock time #+remote_queue = "osg" # Request the OSG queue # Run job once queue
Don't forget to create the shell script mentioned in the *.sub:
#!/bin/bash sleep 180 id pwd date /usr/bin/hostname env
And then you submit exactly the same way as for a local submission:
condor_submit ce_test.sub
The official documentation explaining in details job submission is available here.