Browse code
Fix proper oslo.messaging object for zeromq driver
Currently, as almost all the rpc driver of projects
have been switched to oslo.messaging, the object should
be imported via oslo.messaging rather than its own rpc lib.
Change-Id: I9633446e78cb5af21f61a26f6fb365a8ed57a85f
Partially-Implements: blueprint zeromq
Closes-Bug: #1395721
Li Ma authored on 2014/12/21 17:46:34Showing 1 changed files
| ... | ... |
@@ -221,9 +221,9 @@ function iniset_rpc_backend {
|
| 221 | 221 |
local file=$2 |
| 222 | 222 |
local section=$3 |
| 223 | 223 |
if is_service_enabled zeromq; then |
| 224 |
- iniset $file $section rpc_backend ${package}.openstack.common.rpc.impl_zmq
|
|
| 224 |
+ iniset $file $section rpc_backend "zmq" |
|
| 225 | 225 |
iniset $file $section rpc_zmq_matchmaker \ |
| 226 |
- ${package}.openstack.common.rpc.matchmaker_redis.MatchMakerRedis
|
|
| 226 |
+ oslo.messaging._drivers.matchmaker_redis.MatchMakerRedis |
|
| 227 | 227 |
# Set MATCHMAKER_REDIS_HOST if running multi-node. |
| 228 | 228 |
MATCHMAKER_REDIS_HOST=${MATCHMAKER_REDIS_HOST:-127.0.0.1}
|
| 229 | 229 |
iniset $file matchmaker_redis host $MATCHMAKER_REDIS_HOST |