rpc_backend is wrong in trove install manual

Bug #1327273 reported by Navneet Grewal
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Opinion
Undecided
Anastasia Martynova

Bug Description

Document on webpage states

DEFAULT rpc_backend qpid

Correct text is

DEFAULT rpc_backend trove.openstack.common.rpc.impl_qpid

This is referenced several times in the document.

Thanks,

-----------------------------------
Built: 2014-06-06T07:41:59 00:00
git SHA: ff792f3fd84ee6c4f1c1540c910cce90f856b8f4
URL: http://docs.openstack.org/icehouse/install-guide/install/yum/content/trove-install.html
source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_trove-install.xml
xml:id: trove-install

Changed in openstack-manuals:
assignee: nobody → Anastasia Martynova (anastasia-martynova)
Revision history for this message
Anastasia Martynova (anastasia-martynova) wrote :

This bug is no longer valid: according to the log of the file section_trove-install.xml, a change has been submitted, approved and merged, which replaces Qpid specific setup for Fedora by RabbitMQ.

Text "DEFAULT rpc_backend qpid" does no longer exist on the source files.

commit 0a4ade13d849653a157204bc658a7f20db6bd607
Author: Andreas Jaeger <email address hidden>
Date: Wed Jun 4 21:28:37 2014 +0200

    Install Guide: One message broker to rule them all

    Remove Qpid specific setup for Fedora etc, use RabbitMQ everywhere.

    Change-Id: I75a45f070c4a5ed3770504b296824d7dc6075c23
    Implements: blueprint installation-guide-improvements
    backport: none

Revision history for this message
Anastasia Martynova (anastasia-martynova) wrote :

excerpt from command line:

cat section_trove-install.xml | grep rpc_backend
  DEFAULT rpc_backend rabbit</userinput>
  DEFAULT rpc_backend rabbit</userinput>
  DEFAULT rpc_backend rabbit</userinput>

Revision history for this message
Navneet Grewal (yellowcirclenet) wrote :

My setup is based on centos, and I have been following centos instructions. All steps within centos use qpid as rpc back end , and do not use rabbit.

There is no rabbit mq installed in my environment. Bug I reported is requesting update to docs to include full name of qpid instead of just the name 'qpid'

Revision history for this message
Anastasia Martynova (anastasia-martynova) wrote :

Hi Navneet,

I filed this question at Ask.openstack.org, let us see what community has to say:

https://ask.openstack.org/en/question/31821/qpid-vs-rabbitmq-for-trove-installation/

Otherwise, the changed has already been implemented and I'm not sure I have the right to change everything back..

Revision history for this message
Anastasia Martynova (anastasia-martynova) wrote :

Hi Navneet,

I've read once again closer into the Change description (https://review.openstack.org/#/c/97890/) and found out that this change was discussed and agreed on during the design sessions on Juno summit. Apparently, this change is not going away or planned to be updated to offer either one of Qpid and RabbitMQ.

With respect to this, can you please close this bug as invalid?:

https://blueprints.launchpad.net/openstack-manuals/+spec/installation-guide-improvements

"Improve the Installation Guide primarily using results of the audit and session at the Juno summit."

Changed in openstack-manuals:
status: New → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.