The =condor_annex= tool rents computational resources from Amazon's cloud service and joins them to an HTCondor pool for your jobs to use. These instructions document how to use =condor_annex= for CHTC jobs. Some restrictions apply:
*: At the moment, you can only use =condor_annex= for jobs on =submit-4.chtc.wisc.edu=.
+*: You will need a log-in on =annex-cm.chtc.wisc.edu=. (Ask your RCF about this.)
*: Your jobs must have =MayUseAWS= set in their ads.
*: Your jobs must have =WantFlocking= set in their ads.
*: Your jobs' requirements must, of course, allow them to run on Amazon's cloud.
@@ -30,7 +31,7 @@
In order to use AWS, =condor_annex= needs a pair of security tokens (like a user name and password). Like a user name, the "access key" is (more or less) public information; the corresponding "secret key" is like a password and must be kept a secret. To help keep both halves secret, =condor_annex= (and HTCondor) are never told these keys directly; instead, you tell HTCondor which file to look in to find each one.
-Log into =submit-4.chtc.wisc.edu= and create those two files now; we'll tell you how to fill them in shortly. By convention, these files exist in your =~/.condor= directory, which is where =condor_annex -setup= will store the rest of the data it needs.
+Log into =annex-cm.chtc.wisc.edu= and create those two files now; we'll tell you how to fill them in shortly. By convention, these files exist in your =~/.condor= directory, which is where =condor_annex -setup= will store the rest of the data it needs.
{term}
$ mkdir ~/.condor
