openstack/training-guides
Code Issues Proposed changes

cleanup of module001-ch008-queues-messaging

Browse Source 
changed to marshaling to stick to convention in above sentence
corrected run on sentence
capitalized after new para
RabbitMQ is "a" function - added "a"
the hostname, the added
added the before sake
Consumers changed to consumers

Change-Id: I87858d666b201d1bbc24c9fcf17507fc897432fb
This commit is contained in:
Shilla Saebi
2014-02-28 17:39:06 -05:00
parent b402b16f67
commit f00111fd3e
1 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
module001-ch008-queues-messaging.xml
View File

@@ -51,7 +51,7 @@
<para>Nova implements RPC (both request+response, and one-way,
respectively nicknamed ‘rpc.call’ and ‘rpc.cast’) over AMQP by
providing an adapter class which take cares of marshaling and
un-marshalling of messages into function calls. Each Nova service,
un-marshaling of messages into function calls. Each Nova service,
such as Compute, Scheduler, and so on, creates two queues at the
initialization time, one which accepts messages with routing keys
‘NODE-TYPE.NODE-ID’, for example, compute.hostname, and another,
@@ -155,24 +155,24 @@
operation:</para>
<orderedlist>
<listitem>
<para>a Topic Publisher is instantiated to send the message
<para>A Topic Publisher is instantiated to send the message
request to the queuing system; immediately before the
publishing operation, a Direct Consumer is instantiated to
publishing operation. A Direct Consumer is instantiated to
wait for the response message.</para>
</listitem>
<listitem>
<para>once the message is dispatched by the exchange, it is
<para>Once the message is dispatched by the exchange, it is
fetched by the Topic Consumer dictated by the routing key
(such as ‘topic.host’) and passed to the Worker in charge of
the task.</para>
</listitem>
<listitem>
<para>once the task is completed, a Direct Publisher is
<para>Once the task is completed, a Direct Publisher is
allocated to send the response message to the queuing
system.</para>
</listitem>
<listitem>
<para>once the message is dispatched by the exchange, it is
<para>Once the message is dispatched by the exchange, it is
fetched by the Direct Consumer dictated by the routing key
(such as ‘msg_id’) and passed to the Invoker.</para>
</listitem>
@@ -210,7 +210,7 @@
</figure>
<para><guilabel>AMQP Broker Load</guilabel></para>
<para>At any given time the load of a message broker node running
either Qpid or RabbitMQ is function of the following
either Qpid or RabbitMQ is a function of the following
parameters:</para>
<itemizedlist>
<listitem>
@@ -248,19 +248,19 @@
</itemizedlist>
<orderedlist>
<listitem>
<para>compute.phantom (phantom is hostname)</para>
<para>compute.phantom (phantom is the hostname)</para>
</listitem>
<listitem>
<para>compute</para>
</listitem>
<listitem>
<para>network.phantom (phantom is hostname)</para>
<para>network.phantom (phantom is the hostname)</para>
</listitem>
<listitem>
<para>network</para>
</listitem>
<listitem>
<para>scheduler.phantom (phantom is hostname)</para>
<para>scheduler.phantom (phantom is the hostname)</para>
</listitem>
<listitem>
<para>scheduler</para>
@@ -274,7 +274,7 @@
order to instantiate a Connection object that connects to the
RabbitMQ server (please note that most of the following material
can be also found in the Kombu documentation; it has been
summarized and revised here for sake of clarity):</para>
summarized and revised here for the sake of clarity):</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">Hostname:</emphasis> The hostname to
@@ -318,7 +318,7 @@
to the server. The default is False.</para>
</listitem>
</itemizedlist>
<para>More precisely Consumers need the following parameters:</para>
<para>More precisely consumers need the following parameters:</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">Connection:</emphasis> the above
@@ -407,8 +407,8 @@
<para><emphasis role="bold">Auto_declare:</emphasis>if this is
True and the exchange name is set, the exchange will be
automatically declared at instantiation. Auto declare is on by
default. Publishers specify most the parameters of Consumers
(such as they do not specify a queue name), but they can also
default. Publishers specify most the parameters of consumers
(they do not specify a queue name), but they can also
specify the following:</para>
</listitem>
<listitem>