openstack
/
devstack-plugin-amqp1
Code Issues Proposed changes
DevStack plugin to configure AMQP1.
21 Commits 1 Branch 5 Tags 346 KiB
Shell 100%
Go to file
Andrew Smith a9891fe766 Enable Dual Messaging System Backends 
This patch enables the AMQP 1.0 plugin to deploy either a single
broker (RPC and Notifications) or a dual dispatch-router (RPC) and
broker (Notification) configuration.

Change-Id: I8e52c58a3f7f9aa1bce55bd91bf9b71d504da813
 		2016-11-17 13:05:39 -05:00
devstack Enable Dual Messaging System Backends 2016-11-17 13:05:39 -05:00
.gitignore Initial commit 2015-06-19 11:45:30 -04:00
.gitreview Added tox.ini, gitreview and update README 2015-09-30 21:26:18 -04:00
LICENSE Initial commit 2015-06-19 11:45:30 -04:00
README.rst Enable Dual Messaging System Backends 2016-11-17 13:05:39 -05:00
tox.ini Set oslo_messaging_amqp section for qpid user 2016-02-17 11:31:24 -05:00

README.rst

Enabling in Devstack

Devstack plugin for AMQP 1.0 olso.messaging driver - This plugin supports the QPID C++ broker for RPC and Notification backends and the QPID Dispatch Router messaging system for the RPC backend. Additional information on these messaging systems can be found at the Apache QPID homepage (https://qpid.apache.org).

  1. Download DevStack

  2. Add this repo as an external repository:

    cat > local.conf
[[local|localrc]]
enable_plugin amqp1 https://git.openstack.org/openstack/devstack-plugin-amqp1

  3. Set username and password variables if needed and they will be added to configuration:

    AMQP1_USERNAME=queueuser
AMQP1_PASSWORD=queuepassword

  4. Optionally set the service variable for the configuration. The default is for the broker to provide both the RPC and Notification backends. If dual backends are to be used as an alternative AMQP1 service:

    AMQP1_SERVICE=qpid-dual

  5. run stack.sh