get_transport mis-use when messaging backends are separated
Bug #1680192 reported by
Andy Smith
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.messaging |
Fix Released
|
Medium
|
Andy Smith |
Bug Description
With the ability to separate RPC and Notification messaging backends, the API should be uniform with respect to retrievel of associated transports:
get_rpc_transport
get_notifiation
The current get_transport has the potential for mis-use based on configuration or an incorrect association to notifier.
Changed in oslo.messaging: | |
assignee: | nobody → Andy Smith (ansmith-t) |
Changed in oslo.messaging: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/454194 /git.openstack. org/cgit/ openstack/ oslo.messaging/ commit/ ?id=ec4d6639bc7 556afaf439d261b 716818b02a1605
Committed: https:/
Submitter: Jenkins
Branch: master
commit ec4d6639bc7556a faf439d261b7168 18b02a1605
Author: Andrew Smith <email address hidden>
Date: Thu Apr 6 09:47:34 2017 -0400
Add get_rpc_transport call
The get_rpc_transport wraps get_transport to unify the API in
anticipation of comprehensive separation of RPC and Notification
messaging backends.
Related-Bug: 1680192 06c2af38a3ba129 991f1e0ec86
Change-Id: Ic6af07b98ff438