openstack
/
congress
Code Issues Proposed changes

Some updations in congress docs 

Change-Id: I1afa04efafc0681f5ce1eeaec88c723a2d9d7b5c
This commit is contained in:
Anusha Ramineni 2016-09-21 10:18:25 +05:30
parent 8fd5ca3c35
commit f66eb9a601
2 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.rst
View File

@ -200,6 +200,13 @@ Add the following line to [DEFAULT] section in /etc/congress/congress.conf
Also, might want to delete/comment [keystone_authtoken] section in
/etc/congress/congress.conf
To use RabbitMQ with Congress,
Set the transport_url in [DEFAULT] section in /etc/congress/congress.conf according to your setup.
.. code-block:: text
transport_url = rabbit://$RABBIT_USERID:$RABBIT_PASSWORD@$RABBIT_HOST:5672
A bare-bones congress.conf is as follows (adapt MySQL root password):
.. code-block:: text

11
doc/source/deployment.rst
View File

@ -64,10 +64,13 @@ One of Congress's new experimental features is distributing its services
across multiple services and even hosts. Here are the options for using
that feature.
``node_id``
Unique ID of this Congress instance. Can be any string. Useful if
you want to create multiple, distributed instances of Congress. Appears
in the [DSE] section.
``bus_id``
Unique ID of DSE bus. Can be any string. Defaults to 'bus'.
ID should be same across all the processes of a single congress instance
and should be unique across different congress instances.
Used if you want to create multiple, distributed instances of Congress and
can be ignored if only one congress instance is deployed as single process
in rabbitMQ cluster. Appears in the [dse] section.
Here are the most often-used, but standard OpenStack options. These
are specified in the [DEFAULT] section of the configuration file.