c7bfdbb44f
Provide a script for interpreting the "only" directives and splitting the existing content up into standalone files for each OS to make it easier for project teams to copy the parts they need into their own project documentation trees without requiring separate platform builds. The files have been hand-edited to pass the niceness check and to allow the install guide to build. The script for building the guide has been changed to not build separate copies per OS. Change-Id: Ib88f373190e2a4fbf14186418852d971b33dca85 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
21 lines
769 B
ReStructuredText
21 lines
769 B
ReStructuredText
Message queue
|
|
~~~~~~~~~~~~~
|
|
|
|
OpenStack uses a :term:`message queue` to coordinate operations and
|
|
status information among services. The message queue service typically
|
|
runs on the controller node. OpenStack supports several message queue
|
|
services including `RabbitMQ <https://www.rabbitmq.com>`__,
|
|
`Qpid <https://qpid.apache.org>`__, and `ZeroMQ <http://zeromq.org>`__.
|
|
However, most distributions that package OpenStack support a particular
|
|
message queue service. This guide implements the RabbitMQ message queue
|
|
service because most distributions support it. If you prefer to
|
|
implement a different message queue service, consult the documentation
|
|
associated with it.
|
|
|
|
The message queue runs on the controller node.
|
|
|
|
.. toctree::
|
|
:glob:
|
|
|
|
environment-messaging-*
|