13b85cc38f
This patch refactor zaqar doc according to the doc-migration spec. api, cli, configuration and reference should be added in the next few patches if need. Change-Id: I74a4949f4eace423c06ab6e8d95838df1f312d93
36 lines
1.1 KiB
ReStructuredText
36 lines
1.1 KiB
ReStructuredText
.. _install:
|
|
|
|
Install and configure
|
|
~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
This section describes how to install and configure the Messaging service,
|
|
code-named zaqar.
|
|
|
|
This section assumes that you already have a working OpenStack environment with
|
|
at least Identity service installed.
|
|
|
|
Note that installation and configuration vary by distribution.
|
|
|
|
.. toctree::
|
|
|
|
install-obs.rst
|
|
install-rdo.rst
|
|
install-ubuntu.rst
|
|
|
|
Possible Minimum Scalable HA Setup
|
|
----------------------------------
|
|
|
|
Scalable HA (High availability) setup is out of scope in this chapter.
|
|
|
|
For a HA setup, a load balancer has to be placed in front of the web servers.
|
|
|
|
To provide high availability with minimum administration overhead for storage
|
|
use ``MongoDB`` driver and for transport use ``wsgi`` driver.
|
|
|
|
To have a small footprint while providing HA, you can use two web servers which
|
|
will host the application and three ``MongoDB`` servers (configured as
|
|
replica-set) which will host Messaging service's management store and
|
|
message store databases. At larger scale, the management store database and the
|
|
message store database are advised to be hosted on different ``MongoDB``
|
|
replica sets.
|