$ condor_annex -count 1 -annex-name MyFirstAnnex
Will request 1 m4.large on-demand instance for 0.83 hours. Each instance will terminate after being idle for 0.25 hours.
Is that OK? (Type 'yes' or 'no'): yes
-Starting annex. Once started, it will take about three minutes for the new machines to join the pool. (Please wait.)
-Annex started. Its identity with the cloud provider is 'TestAnnex0_f2923fd1-3cad-47f3-8e19-fff9988ddacf'.
+Starting annex...
+Annex started. Its identity with the cloud provider is
+'TestAnnex0_f2923fd1-3cad-47f3-8e19-fff9988ddacf'. It will take about three minutes for the new machines to join the pool.
{endterm}
You won't need to know the annex's identity with the cloud provider unless something goes long.
@@ -71,6 +72,18 @@
This example shows that the annex instance you requested has joined your pool. (The default annex image configures one static slot for each CPU it finds on start-up.)
+You can also get a report about the instances which have not joined your pool:
+
+{term}
+$ condor_annex -annex MyFirstAnnex -status
+STATE COUNT
+pending 1
+TOTAL 1
+
+Instances not in the pool, grouped by state:
+pending i-06928b26786dc7e6e
+{endterm}
+
{section: Run a Job}
Starting in v8.7.1, the default behaviour for an annex instance is to run only jobs submitted by the user who ran the =condor_annex= command. If you'd like to allow other users to run jobs, list them (separated by commas; be sure to include yourself) as arguments to the =-owner= flag when you start the instance. If you're creating an annex for general use, use the =-no-owner= flag to run jobs from anyone.
@@ -87,7 +100,7 @@
The following command shuts HTCondor off on each instance in the annex; if you're using the default annex image, doing so causes each instance to shut itself down.
{term}
-$ condor_off -master -annex MyFirstAnnex
+$ condor_off -annex MyFirstAnnex
Sent "Kill-Daemon" command for "master" to master ip-172-31-48-84.ec2.internal
{endterm}
