]> review.fuel-infra Code Review - openstack-build/neutron-build.git/commit
Don't instantiate RPC clients on import
authorIhar Hrachyshka <ihrachys@redhat.com>
Tue, 3 Jun 2014 11:30:58 +0000 (13:30 +0200)
committerIhar Hrachyshka <ihrachys@redhat.com>
Tue, 17 Jun 2014 19:56:24 +0000 (21:56 +0200)
commit469a1ca64b2c64fe270859ce927f0c0eba6ee8bd
treefd07ab7a0373c42d04433a5502f950747aa2f7ba
parentc0db9c23e307a000af5e8fed6960ccd55c0e3a38
Don't instantiate RPC clients on import

In oslo.messaging port, we'll need to make sure no RPC clients or
servers or notifiers are created before RPC layer is initialized using
n_rpc.init(). This means that there should be no global objects that
create those objects on __init__.

There should also be no such class attributes because in that case
import will itself instantiate the object, probably before RPC layer is
ready.

blueprint oslo-messaging

Change-Id: Ia8a9fd39777c75e4253f5518c2de6be551cc365b
neutron/api/rpc/agentnotifiers/l3_rpc_agent_api.py
neutron/db/l3_db.py
neutron/plugins/brocade/NeutronPlugin.py
neutron/plugins/cisco/n1kv/n1kv_neutron_plugin.py
neutron/plugins/linuxbridge/lb_neutron_plugin.py
neutron/plugins/ml2/drivers/l2pop/mech_driver.py
neutron/plugins/ml2/drivers/l2pop/rpc.py
neutron/plugins/mlnx/mlnx_plugin.py
neutron/plugins/oneconvergence/plugin.py
neutron/plugins/openvswitch/ovs_neutron_plugin.py
neutron/services/l3_router/l3_router_plugin.py