openstack/openstack-manuals
Code Issues Proposed changes

[config-ref] Remove references to Qpid

Browse Source 
The support has been dropped from Oslo, don't suggest it is still
usable.

Change-Id: I2ec090b5f093bbf45d19210bf07fe302ad8e07ba
This commit is contained in:
Gauvain Pocentek
2016-03-19 16:32:34 +01:00
parent ac2b77a186
commit 52d0cfb940
9 changed files with 14 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
doc/common/get_started_compute.rst
View File

@@ -104,8 +104,7 @@ OpenStack Compute consists of the following areas and their components:
The queue
A central hub for passing messages between daemons. Usually
implemented with `RabbitMQ <http://www.rabbitmq.com/>`__, but can be
implemented with an AMQP message queue, such as `Apache
Qpid <http://qpid.apache.org/>`__ or `Zero
implemented with an AMQP message queue, such as `Zero
MQ <http://www.zeromq.org/>`__.
SQL database

2
doc/common/get_started_logical_architecture.rst
View File

@@ -20,7 +20,7 @@ distinct processes.
For communication between the processes of one service, an AMQP message
broker is used. The service's state is stored in a database. When
deploying and configuring your OpenStack cloud, you can choose among
several message broker and database solutions, such as RabbitMQ, Qpid,
several message broker and database solutions, such as RabbitMQ,
MySQL, MariaDB, and SQLite.
Users can access OpenStack via the web-based user interface implemented

2
doc/config-reference/source/compute/cells.rst
View File

@@ -260,7 +260,7 @@ The ``transport_url`` has the following form:
rabbit://USERNAME:PASSWORD@HOSTNAME:PORT/VIRTUAL_HOST
The scheme can be either ``qpid`` or ``rabbit``, as shown previously.
The scheme can only be ``rabbit``.
The following sample shows this optional configuration:
.. code-block:: json

58
doc/config-reference/source/compute/rpc.rst
View File

@@ -5,7 +5,7 @@ Configure the Oslo RPC messaging system
OpenStack projects use AMQP, an open standard for messaging middleware.
This messaging middleware enables the OpenStack services that run on
multiple servers to talk to each other. OpenStack Oslo RPC supports
three implementations of AMQP: ``RabbitMQ``, ``Qpid``, and ``ZeroMQ``.
two implementations of AMQP: RabbitMQ and ZeroMQ.
Configure RabbitMQ
~~~~~~~~~~~~~~~~~~
@@ -31,58 +31,6 @@ number of seconds from zero to sixty.
.. include:: ../tables/nova-rabbitmq.rst
Configure Qpid
~~~~~~~~~~~~~~
Use these options to configure the ``Qpid`` messaging system for
OpenStack Oslo RPC. ``Qpid`` is not the default messaging system,
so you must enable it by setting the ``rpc_backend`` option in the
``nova.conf`` file.
.. code-block:: ini
rpc_backend=qpid
.. warning::
The Qpid driver has been deprecated.
The driver is planned to be removed during the Mitaka development cycle.
This critical option points the compute nodes to the ``Qpid`` broker (server).
Set ``qpid_hostname`` to the host name where the broker runs in the
``nova.conf`` file.
.. note::
The :option:`--qpid_hostname` parameter accepts a host name or IP address value.
.. code-block:: ini
qpid_hostname=hostname.example.com
If the ``Qpid`` broker listens on a port other than the AMQP default of
``5672``, you must set the ``qpid_port`` option to that value:
.. code-block:: ini
qpid_port=12345
If you configure the ``Qpid`` broker to require authentication,
you must add a user name and password to the configuration:
.. code-block:: ini
qpid_username=username
qpid_password=password
By default, TCP is used as the transport.
To enable SSL, set the ``qpid_protocol`` option:
.. code-block:: ini
qpid_protocol=ssl
Configure ZeroMQ
~~~~~~~~~~~~~~~~
@@ -95,8 +43,8 @@ it by setting the ``rpc_backend`` option in the ``nova.conf`` file.
Configure messaging
~~~~~~~~~~~~~~~~~~~
Use these options to configure the ``RabbitMQ`` and ``Qpid``
messaging drivers in the ``nova.conf`` file.
Use these options to configure the ``RabbitMQ`` messaging driver in the
``nova.conf`` file.
.. include:: ../tables/nova-amqp.rst
.. include:: ../tables/nova-rpc.rst

2
doc/config-reference/source/database-service/databaseservice_rpc.rst
View File

@@ -26,7 +26,7 @@ in the ``trove.conf`` file:
Configure messaging
~~~~~~~~~~~~~~~~~~~
Use these common options to configure the RabbitMQ, Qpid, and ZeroMq
Use these common options to configure the RabbitMQ and ZeroMq
messaging drivers in the ``trove.conf`` file:
.. include:: ../tables/trove-amqp.rst

4
doc/config-reference/source/image-service/image_service_rpc.rst
View File

@@ -5,8 +5,8 @@ Configure the RPC messaging system
OpenStack projects use an open standard for messaging middleware known
as AMQP. This messaging middleware enables the OpenStack services that
run on multiple servers to talk to each other. The OpenStack common
library project, oslo, supports three implementations of AMQP: RabbitMQ,
Qpid, and ZeroMQ.
library project, oslo, supports two implementations of AMQP: RabbitMQ and
ZeroMQ.
The following tables contain settings to configure the messaging middleware
for the Image service. Use these options to configure the messaging drivers

4
doc/config-reference/source/networking/networking_options_reference.rst
View File

@@ -151,7 +151,7 @@ Configure the Oslo RPC messaging system
OpenStack projects use an open standard for messaging middleware known
as AMQP. This messaging middleware enables the OpenStack services that
run on multiple servers to talk to each other. OpenStack Oslo RPC
supports three implementations of AMQP: RabbitMQ, Qpid, and ZeroMQ.
supports two implementations of AMQP: RabbitMQ and ZeroMQ.
Configure RabbitMQ
------------------
@@ -190,7 +190,7 @@ the ``neutron.conf`` file.
Configure messaging
-------------------
Use these common options to configure the RabbitMQ, Qpid, and ZeroMq
Use these common options to configure the RabbitMQ and ZeroMq
messaging drivers in the ``neutron.conf`` file.
.. include:: ../tables/neutron-rpc.rst

2
doc/config-reference/source/orchestration/orchestration_rpc.rst
View File

@@ -44,7 +44,7 @@ must enable it by setting the ``rpc_backend`` option in the
Configure messaging
~~~~~~~~~~~~~~~~~~~
Use these common options to configure the RabbitMQ, Qpid, and ZeroMq
Use these common options to configure the RabbitMQ and ZeroMq
messaging drivers in the ``heat.conf`` file.
.. include:: ../tables/heat-amqp.rst

4
doc/config-reference/source/shared-file-systems/rpc.rst
View File

@@ -5,8 +5,8 @@ Configure the RPC messaging system
OpenStack projects use an open standard for messaging middleware known
as AMQP. This messaging middleware enables the OpenStack services that
run on multiple servers to talk to each other. The OpenStack common
library project, oslo, supports three implementations of AMQP: RabbitMQ,
Qpid, and ZeroMQ.
library project, oslo, supports two implementations of AMQP: RabbitMQ and
ZeroMQ.
The following tables contain settings to configure the messaging
middleware for the Shared File System service: