{section: Monitor your Annex}
-You can find out if that instance has successfully joined the pool in the following way.
+You can find out if that instance has successfully joined the pool in the following way:
+
+{term}
+$ condor_annex status
+Name OpSys Arch State Activity Loa
+
+slot1@ip-172-31-48-84.ec2.internal LINUX X86_64 Unclaimed Benchmarking 0.
+slot2@ip-172-31-48-84.ec2.internal LINUX X86_64 Unclaimed Idle 0.
+
+ Total Owner Claimed Unclaimed Matched Preempting Backfill Drain
+
+ X86_64/LINUX 2 0 0 2 0 0 0 0
+ Total 2 0 0 2 0 0 0 0
+{endterm}
+
+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 may instead use =condor_status=:
{term}
$ condor_status -annex MyFirstAnnex
@@ -79,7 +96,6 @@
Total 2 0 0 2 0 0 0 0
{endterm}
-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:
@@ -127,6 +143,29 @@
The ellipsis in the last column (=INSTANCES...=) is to indicate that it's a very wide column and may wrap (as it will for NamelessTestB on an 80-column terminal), not that it has been truncated.
+The following command combines these two reports:
+
+{term}
+$ condor_annex status
+Name OpSys Arch State Activity Loa
+
+slot1@ip-172-31-48-84.ec2.internal LINUX X86_64 Unclaimed Benchmarking 0.
+slot2@ip-172-31-48-84.ec2.internal LINUX X86_64 Unclaimed Idle 0.
+
+ Total Owner Claimed Unclaimed Matched Preempting Backfill Drain
+
+ X86_64/LINUX 2 0 0 2 0 0 0 0
+ Total 2 0 0 2 0 0 0 0
+
+Instance ID not in Annex Status Reason (if known)
+i-075af9ccb40efb162 NamelessTestA running -
+i-0bc5e90066ed62dd8 NamelessTestA running -
+i-02e69e85197f249c2 NamelessTestB running -
+i-0385f59f482ae6a2e NamelessTestB running -
+i-06191feb755963edd NamelessTestB running -
+i-09da89d40cde1f212 NamelessTestC running -
+{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.
