HTCondorWiki: Experimental Annex Daemon

 
 {section: usage}
 
-In this prototype, the =condor_annex= tool requires a JSON file describing the kind of instances you'd like.  The easiest way to generate this JSON file is using the AWS web console; when you request a Spot Fleet, on the last page before you submit the request, there's a button in the upper-right labelled "JSON config"; click it to download a file.  Save the file (the default name is =config.json=, which is fine).
+In this prototype, the =condor_annex= tool requires a JSON file describing the kind of instances you'd like.  The easiest way to generate this JSON file is using the AWS web console; when you request a Spot Fleet, on the last page before you submit the request, there's a button in the upper-right labelled "JSON config"; click it to download a file.  Save the file (the default name is =config.json=, which is fine).  FIXME: If you're not familiar with Spot Fleet, the prototype includes a reasonable example =config.json= you can use to get started.  It uses an image maintained by HTCondor (Amazon Linux with HTCondor pre-installed).
 
 After you save the config, open it in your favorite text editor and remove the two lines containing "ValidFrom" and "ValidUntil".  (FIXME: If =condor_annex= were to just ignore these entries, would it need to support additional CLI flags to set them?)
 
@@ -51,5 +51,19 @@
    # FIXME: Leaving this out entirely doesn't produce a reasonable error message.
    # FIXME: The daemon crashes on restart after the above failure.
    -lease-function-arn <LeaseFunctionARN string> \
+   # FIXME: Add a CL flag to override this file's count.
    config.json
 {endverbatim}
+
+The tool will print out the Spot Fleet request ID generated by the daemon if it was successful.
+
+{subsection: options}
+
+*: Like most other HTCondor tools, you can specify which daemon =condor_annex= should contact using the =-pool= and =-name= flags.  This is probably not useful in this version.
+*: You may specify the endpoints with the =-service-url=, =-events-url=, and =-lambda-url= flags.
+*: If you'd like to change (or specify) the user data from the command line, use the =-user-data[-file]= and =-default-user-data[-file]= flags.  The =-file= form specifies a file containing the user data.  The default flag will set an instance's user data as specified only if the JSON configuration file did not; the normal form sets it unconditionally.
+*: The tool also support the =-debug-] and =-help= flags.
+
+{section: advanced usage}
+
+The basic usage, above, possibly in conjuction with some of the other options, should suffice for the efficient provisioning of many instance from pre-existing images.  If you'd like to use the prototype