RPC layer should support multiple rabbit exchanges
Bug #1055483 reported by
Eoghan Glynn
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo-incubator |
Fix Released
|
Wishlist
|
Eoghan Glynn | ||
| Grizzly |
Fix Released
|
Wishlist
|
Eoghan Glynn | ||
Bug Description
The RPC rabbit support is predicated on an AMQP client only being ever interested in a single exchange (i.e. exchange name is a single config option).
However in some cases, a single client is interested in interacting with multiple different exchanges.
A case in point is the glance notification handler currently being added to ceilometer, where out-of-the-box glance notifications are sent via a glance-specific exchange. Whereas the ceilometer collector also needs to continue to pull from the nova exchange (and cinder etc. too in the future ...).
| Changed in openstack-common: | |
| assignee: | nobody → Eoghan Glynn (eglynn) |
| Changed in openstack-common: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to openstack-common (master) | #1 |
| Changed in openstack-common: | |
| status: | Confirmed → Fix Committed |
| affects: | openstack-common → oslo |
| Changed in oslo: | |
| milestone: | none → grizzly-1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit 83b4cce116ec2f1
Author: Julien Danjou <email address hidden>
Date: Wed Sep 26 17:03:37 2012 +0200
Add exchange_name parameter to TopicConsumer
In Ceilometer, we need to consume messages from different exchanges of type
'topic', so being able to specify the exchange name rather than using the
default in TopicConsumer is necessary.
This fixes bug #1055483
Change-Id: Ibbaec8496f24c0
Signed-off-by: Julien Danjou <email address hidden>