*: Your jobs' requirements must allow them to run on Amazon's cloud. When =condor_annex= acquires resources from AWS, they will by default run an EL6-like operating system, but they won't have =OpSysMajorVer= set.
*: Intentionally or otherwise, other users of =condor_annex= on the CHTC may run jobs they don't own, including yours, on their resources. We're working on a solution to this, but if that possibility worries you, don't use =condor_annex= for now.
-These restrictions will be covered in the following instructions, but if you haven't run a particular job with =condor_annex= before, you should probably add just a single resource and make sure you job actually works there before adding a useful number of resources.
+Working with these restrictions will be covered in the following instructions.
In these instructions, we've included sample output after the commands. Lines you should execute start with the dollar sign (=$=) character; do not include the dollar sign (=$=) when copying the line.
@@ -118,7 +118,7 @@
{section: 3 Add Resources to the Pool}
-Entering the following on =annex-cm.chtc.wisc.edu= will add resources for your jobs to the pool. We call the set of resources you added an "annex". You have to supply a name for each annex you create; the example below uses 'MyFirstAnnex'. When you run =condor_annex=, it will print out what it's going to do, and then ask you if that's OK. You must type 'yes' (and hit enter) at the prompt to start an annex; if you do not, =condor_annex= will print out instructions about how to change whatever you may not like about what it said it was going to do, and then exit.
+Entering the following on =annex-cm.chtc.wisc.edu= will add resources for your jobs to the pool. We call the set of resources you added an "annex". You have to supply a name for each annex you create; the example below uses 'MyFirstAnnex'. When you run =condor_annex=, it will print out what it's going to do, and then ask you if that's OK. You must type 'yes' (and hit enter) at the prompt to start an annex; if you do not, =condor_annex= will print out instructions about how to change whatever you may not like about what it said it was going to do, and then exit. The following command adds one resource (an "instance") for one hour; you should increase that if the job you want to run takes longer. Don't increase the number of resources if you haven't tested your job with =condor_annex= yet; you can easily add resources after you've verified that everything should work.
{term}
$ condor_annex -count 1 -annex-name MyFirstAnnex -idle 1 -duration 1
@@ -157,12 +157,13 @@
(MayUseAWS == true) && stringListMember(Owner,"tlmiller")
{endterm}
-There are {wiki: HowToUseCondorAnnexWithOnDemandInstancesEightSevenFour additional instructions} for general annex use. For now, we'll move on to actually running on your new resources.
+The =tlmiller= above should be your login.
+
+There are {wiki: HowToUseCondorAnnexWithOnDemandInstancesEightSevenFour additional instructions} for general annex use. For now, we'll move on to actually running on your new resource.
{section: 4 Run Jobs on Those Resources}
-It might take a while for =submit-4.chtc.wisc.edu= to try the other possibilities before giving the annex a chance to run the job. Run condor_q in the terminal logged in to that machine to keep track of the test job; it should eventually run. (Check its log
-if it's gone when you check; the job may have run and finished.)
+It might take a while for =submit-4.chtc.wisc.edu= to try the other possibilities before giving the annex a chance to run the job. Run condor_q in the terminal logged in to that machine to keep track of the test job; it should eventually run. (Check its log if it's gone when you check; the job may have run and finished.)
You can make use of the annex resources for your own jobs in two ways: by submitting new jobs and by editing existing ones.
@@ -174,6 +175,8 @@
You can also edit existing jobs by using =condor_q=. More on using this tool will be forthcoming.
+Once you've gotten one job running, you may want to add additional resources to your annex. While repeating the command from section 3 will add another instance to the "MyFirstAnnex" annex, for simplicity we recommend using another name. (Using an existing name updates the lease for all instances in the annex, existing and new; but only new instances will respect the new max idle time. If you've used the name of your annex in your job requirements, this might be worth the trouble.)
+
{section: 5 Cleaning Up (Optional)}
The resources =condor_annex= rents for you from Amazon will, as we mentioned before, shut themselves down after the duration, or if they're idle for longer than the time-out. At that point, no more charges will accrue -- it costs you nothing to leave your account set-up to use =condor_annex=.
