]> review.fuel-infra Code Review - openstack-build/neutron-build.git/commit
Use RPC instead of neutron client in metadata agent
authorOleg Bondarev <obondarev@mirantis.com>
Wed, 27 Aug 2014 11:19:18 +0000 (15:19 +0400)
committerOleg Bondarev <obondarev@mirantis.com>
Tue, 28 Oct 2014 11:52:37 +0000 (15:52 +0400)
commita19ec4a7320dead0ea138697b8785638c6dd4307
treed2cc1ca5665c9abae07ab2abb5e681565211b2bb
parent4a28612f60f863ac97d67d4ee48fe8ac8345966d
Use RPC instead of neutron client in metadata agent

RPC is a standard way of interacting between Neutron server and agents
Using neutron client is also  inefficient as it results in unneeded
keystone load and may become a bottleneck at scale

DocImpact
When upgrading, one should upgrade neutron server first,
then metadata agent. However there is a fallback in case
metadata agent fails to get info from server by rpc -
it will return to using neutron client.

Closes-Bug: #1092043

Change-Id: Ib75568643e6062543c0ff8cf80fba1b40b4fe82f
14 files changed:
neutron/agent/metadata/agent.py
neutron/api/rpc/handlers/metadata_rpc.py [new file with mode: 0644]
neutron/plugins/bigswitch/plugin.py
neutron/plugins/brocade/NeutronPlugin.py
neutron/plugins/cisco/n1kv/n1kv_neutron_plugin.py
neutron/plugins/hyperv/hyperv_neutron_plugin.py
neutron/plugins/midonet/plugin.py
neutron/plugins/ml2/plugin.py
neutron/plugins/mlnx/mlnx_plugin.py
neutron/plugins/nec/nec_plugin.py
neutron/plugins/oneconvergence/plugin.py
neutron/plugins/ryu/ryu_neutron_plugin.py
neutron/plugins/vmware/dhcpmeta_modes.py
neutron/tests/unit/test_metadata_agent.py