From 09e1b316f8b304915d9ad4868cb871119f022412 Mon Sep 17 00:00:00 2001 From: Matt Kassawara Date: Thu, 17 Apr 2014 21:45:07 -0600 Subject: [PATCH] Improved messaging server section I improved the messaging server section including structure and content to meet conventions. I also added links to each message broker for those who may consider using a different message broker than the one supported by their particular distribution. Change-Id: Ic046ae7ceee315a9da91f8530542c2e0cb3a66f9 Closes-Bug: #1309304 Closes-Bug: #1298153 --- doc/install-guide/section_basics-queue.xml | 157 +++++++++++++-------- 1 file changed, 101 insertions(+), 56 deletions(-) diff --git a/doc/install-guide/section_basics-queue.xml b/doc/install-guide/section_basics-queue.xml index c7c270805b..b7d7b88c7e 100644 --- a/doc/install-guide/section_basics-queue.xml +++ b/doc/install-guide/section_basics-queue.xml @@ -4,63 +4,108 @@ xml:id="basics-queue"> Messaging server - On the controller node, install the messaging queue server. - Typically this is RabbitMQ - - Qpid but - Qpid - RabbitMQ - and ZeroMQ (0MQ) are also available: - # apt-get install rabbitmq-server - # zypper install rabbitmq-server - # yum install qpid-cpp-server - Disable Qpid authentication by - editing /etc/qpidd.conf file and changing - the auth option to - no: - auth=no - - - To simplify configuration, the Qpid examples in this guide do not use - authentication. However, we strongly advise enabling authentication - for production deployments. For more information on securing Qpid - refer to the - Qpid Documentation. - - - After you enable Qpid authentication, you must update the configuration - file of each OpenStack service to ensure that the - qpid_username and qpid_password - configuration keys refer to a valid Qpid username and password, - respectively. - - - Start Qpid and set it to start - automatically when the system boots: - # service qpidd start + OpenStack uses a message broker to coordinate + operations and status information among services. The message broker + service typically runs on the controller node. OpenStack supports several + message brokers including RabbitMQ, + Qpid, and ZeroMQ. + However, most distributions that package OpenStack support a particular + message broker. This guide covers the message broker supported by each + distribution. If you prefer to implement a different message broker, + consult the documentation associated with it. + + + RabbitMQ + + + Qpid + + + ZeroMQ + + + + To install the message broker service + + Ubuntu and Debian use RabbitMQ. + # apt-get install rabbitmq-server + + + Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux, and + Fedora use Qpid. + + # yum install qpid-cpp-server + + + SUSE Linux Enterprise Server (SLES) and openSUSE use + RabbitMQ. + # zypper install rabbitmq-server + + + + To configure the message broker service + + To simplify installation of your test environment, we recommend + that you disable authentication. + Edit the /etc/qpidd.conf file and change + the following key: + auth=no + + For production environments, you should enable authentication. + For more information on securing the message broker, see the + documentation. + If you decide to enable authentication for your test + environment, you must configure the qpid_username + and qpid_password keys in the configuration file + of each OpenStack service that uses the message broker. + + + + Start the message broker service: + # service rabbitmq-server start + + + The message broker creates a default account that uses + guest for the username and password. To simplify + installation of your test environment, we recommend that you use this + account, but change the password for it. + Run the following command: + Replace RABBIT_PASS with a suitable + password. + # rabbitmqctl change_password guest RABBIT_PASS + You must configure the rabbit_password key + in the configuration file for each OpenStack service that uses the + message broker. + + For production environments, you should create a unique account + with suitable password. For more information on securing the + message broker, see the + documentation. + If you decide to create a unique account with suitable password + for your test environment, you must configure the + rabbit_userid and + rabbit_password keys in the configuration file + of each OpenStack service that uses the message broker. + + + + + To finalize installation + + Start the message broker service and configure it to start when + the system boots: + # service qpidd start # chkconfig qpidd on - Start the messaging service and set it to - start automatically when the system boots: - # service rabbitmq-server start -# chkconfig rabbitmq-server on - - Important security consideration - The rabbitmq-server package configures - the RabbitMQ service to start automatically and creates a - guest user with a default - guest password. The RabbitMQ examples in - this guide use the guest account, though it - is strongly advised to change its default password, especially - if you have IPv6 available: by default the RabbitMQ server - enables anyone to connect to it by using guest as login and - password, and with IPv6, it is reachable from the - outside. - To change the default guest password of RabbitMQ: - # rabbitmqctl change_password guest RABBIT_PASS - + + + Configure the message broker service to start when the system + boots: + # chkconfig rabbitmq-server on + + Congratulations, now you are ready to install OpenStack services!