Bug 889485 - AMQP defaults are inconsistent
Summary: AMQP defaults are inconsistent
Keywords:
Status: CLOSED DUPLICATE of bug 887822
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-quantum
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Bob Kukura
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-21 11:22 UTC by Zane Bitter
Modified: 2014-02-27 23:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-21 15:27:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Zane Bitter 2012-12-21 11:22:44 UTC 
Nova uses the Qpid AMQP driver by default as the RPC backend, but Quantum uses the Kombu (RabbitMQ) driver which is the upstream default. The Quantum default should be changed to Qpid also, since that is the supported AMQP implementation.
Comment 2 Alan Pevec 2012-12-21 13:17:04 UTC 
Indeed, quantum.conf distributed in RPM doesn't set rpc_backend, so cfg default applies, quantum.openstack.common.rpc.impl_kombu

But quantum-{node|dhcp|server}-setup scripts do set rpc_backend to quantum.openstack.common.rpc.impl_qpid along with qpid_hostname.

Anyway, I agree we should make configs consistent out of the box.
Comment 3 Alan Pevec 2012-12-21 15:27:32 UTC 

*** This bug has been marked as a duplicate of bug 887822 ***
Note You need to log in before you can comment on or make changes to this bug.