rpc call leads to unnecerry exchange declaration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.messaging |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
https:/
"Default Exchange
The default exchange is a direct exchange with no name (empty string) pre-declared by the broker. It has one special property that makes it very useful for simple applications: every queue that is created is automatically bound to it with a routing key which is the same as the queue name. "
http://
"One of the standard message properties is Reply-To, which is designed specifically for carrying the name
of reply queues."
Normally for an rpc response do not need to declare a new exchange, the default exchange is for helping this very simple situation.
Based on my captured nova traffic currently the exchange_name == bind_key == queue_name,
so changing the code to just use the default exchange should be simple,
For example: 'reply_
Changed in oslo.messaging: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
assignee: | nobody → Mehdi Abaakouk (sileht) |
milestone: | none → next-liberty |
Changed in oslo.messaging: | |
milestone: | next-liberty → none |
Changed in oslo.messaging: | |
status: | In Progress → Fix Committed |
Changed in oslo.messaging: | |
status: | Fix Committed → Confirmed |
assignee: | Mehdi Abaakouk (sileht) → nobody |
Fix proposed to branch: master /review. openstack. org/179388
Review: https:/