vmware-nsx

History

Oleg Bondarev 647d925f84 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
..
agent	Empty files should not contain copyright or license	2014-10-20 00:50:32 +00:00
common	Empty files should not contain copyright or license	2014-10-20 00:50:32 +00:00
db	Empty files should not contain copyright or license	2014-10-20 00:50:32 +00:00
__init__.py	Empty files should not contain copyright or license	2014-10-20 00:50:32 +00:00
agent_notify_api.py	Moved rpc_compat.py code back into rpc.py	2014-06-24 10:35:39 +02:00
mlnx_plugin.py	Use RPC instead of neutron client in metadata agent	2014-10-28 15:52:37 +04:00
README	Rename Quantum to Neutron	2013-07-06 15:02:43 -04:00
rpc_callbacks.py	Fix a bug in Mellanox plugin RPC caused by secgroup RPC refactoring	2014-09-01 22:41:57 +09:00

README

Mellanox Neutron Plugin

This plugin implements Neutron v2 APIs with support for
Mellanox embedded switch functionality as part of the
VPI (Ethernet/InfiniBand) HCA.

For more details on the plugin, please refer to the following link:
https://wiki.openstack.org/wiki/Mellanox-Quantum