neutron/neutron/api/rpc/handlers
Oleg Bondarev a19ec4a732 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
2014-10-28 15:52:37 +04:00
..
__init__.py RPC additions to support DVR 2014-07-17 11:45:45 -07:00
dhcp_rpc.py Fix KeyError in dhcp_rpc when plugin.port_update raise exception 2014-10-15 13:14:40 +05:30
dvr_rpc.py Remove redundant initialization and check from DVR RPC mixin 2014-10-19 13:56:00 +00:00
l3_rpc.py Add L3 VRRP HA base classes 2014-09-10 12:06:13 +00:00
metadata_rpc.py Use RPC instead of neutron client in metadata agent 2014-10-28 15:52:37 +04:00
securitygroups_rpc.py Fix comments in api.rpc.handlers 2014-09-10 06:13:49 +00:00