Description of problem:
Add a section about the new Absent Nodes feature:

Enabling Absent Node detection:
The event trigger service is able detect nodes that are expected to be in the pool, but which are not actually running.  These are called absent nodes.  This feature requires all machines in the pool to be configured to work with the MRG Management Console (reference Mgmt Console installation Guide section 4.1) and the remote configuration feature (reference section 4).

A node that has been configured with remote configuration is expected to be in the pool.  If the trigger service is unable to find a node, it will raise an event specifying the name of the node that was not found and the time when the event was raised.

To enable absent nodes detection, add the following to condor's configuration:
QMF_BROKER_HOST = <broker>
ENABLE_ABSENT_NODES_DETECTION = TRUE

Where QMF_BROKER_HOST is the name or ip address of an AMQP broker communicating with all the nodes in the pool and the remote configuration store.


Also, in step 1 add the following to the configuration:
DATA = $(SPOOL)

and remove it from the list of other params in step 2.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: