Install the pre-release package(s) as normal.
-Add the following lines to your HTCondor configuration (maybe in =config.d/80annexd=). If you don't want your instances to show up in us-east-1 by default, edit the URLs in the last three lines appopriately.
+Add the following lines to your HTCondor configuration (maybe in =config.d/80annexd=). If you don't want your instances to show up in us-east-1 by default, edit the URLs in the last three lines appropriately.
{verbatim}
# Turn the annex daemon on.
@@ -39,7 +39,7 @@
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. Start a Spot Fleet request for the instance types and other configuration you'd like; on the last page before you submit the request, there's a button in the upper-right labelled "JSON config"; click it and save the file (the default name is =config.json=, which is fine).
-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?)
+After you save the config, open it in your favorite text editor and remove the two lines containing "ValidFrom" and "ValidUntil".
Now you're ready to run =condor_annex=. If you've been using the example's filenames, the command will look something like the following. The [-count] flag is optional; =condor_annex= will otherwise request the target capacity you specify in the JSON file.
