-Condor Qpid Messaging System
+HTCondor Qpid Messaging System
-The Condor Qpid Messaging System can be divided into 3 units.
+The HTCondor Qpid Messaging System can be divided into 3 units.
1:Message Publisher (client producer)
1:broker where the messaging Queues are initialized (server)
@@ -20,9 +20,9 @@
Qpid Message Publisher:
-Event logs for jobs submitted with Condor are written by the Schedd and the Shadow. These log files are rotated over to maintain the latest 'X' event log entries. One of the ideas of the message publisher is to read and persistently forward Event log entries into the AMQP queue.
+Event logs for jobs submitted with HTCondor are written by the Schedd and the Shadow. These log files are rotated over to maintain the latest 'X' event log entries. One of the ideas of the message publisher is to read and persistently forward Event log entries into the AMQP queue.
-The message publisher uses Condor's log reader api.The publisher works as a wrapper on top of the log reader api, providing control to selectively include or exclude event types of the job whose logs are to be read and forwarded.
+The message publisher uses HTCondor's log reader api.The publisher works as a wrapper on top of the log reader api, providing control to selectively include or exclude event types of the job whose logs are to be read and forwarded.
The challenges faced by this system are
@@ -118,12 +118,12 @@
Figure 4
-CONDOR ADD-ON:
+HTCondor ADD-ON:
-The integration of the event log forwarder with the messaging system is added into the condor source code as a daemon ,condor job implementation.
+The integration of the event log forwarder with the messaging system is added into the HTCondor source code as a daemon ,HTCondor job implementation.
condor_qpid daemon:
-The qpid broker is run as a condor daemon – condor_qpid that is controlled by the condor_master.
+The qpid broker is run as a HTCondor daemon – condor_qpid that is controlled by the condor_master.
It performs the following functions:
1:Declare queues and bind them to the exchange
@@ -131,11 +131,11 @@
1:publish a class Ad containing meta details about the qpid broker such as port #, host name, queue name, routing key
-condor jobs:
+HTCondor jobs:
-The qpid clients that send messages to the broker queues as well and listen/retrieve messages run as condor jobs that poll for the condor_qpid daemon published classAd for meta details needed to connect to the broker queues.
+The qpid clients that send messages to the broker queues as well and listen/retrieve messages run as HTCondor jobs that poll for the condor_qpid daemon published classAd for meta details needed to connect to the broker queues.
-Figure 5 explains the control flow between the condor qpid broker daemon and client condor jobs.
+Figure 5 explains the control flow between the HTCondor qpid broker daemon and client HTCondor jobs.
@@ -146,13 +146,13 @@
---------
Example session:
-Once you've built Condor Pigeon, this is what an example session could look like (make sure you have $qpid/lib and $condor/lib in your LD_LIBRARY_PATH, and $condor/bin and $condor/sbin in your PATH):
+Once you've built HTCondor Pigeon, this is what an example session could look like (make sure you have $qpid/lib and $condor/lib in your LD_LIBRARY_PATH, and $condor/bin and $condor/sbin in your PATH):
{code}
# start the daemon
condor_pigeon
- # run the publisher, where myLog.log is an existing Condor user log file
+ # run the publisher, where myLog.log is an existing HTCondor user log file
condor_pigeon_topic_publisher myLog.log persist.dat
# run the example listener
