x/vmware-nsx
Code Issues Proposed changes
vmware-nsx/neutron/plugins/cisco
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
..
cfg_agent
Merge "Supply missing cisco_cfg_agent.ini file"
2014-09-24 16:07:23 +00:00
common
Empty files should not contain copyright or license
2014-10-20 00:50:32 +00:00
db
Merge "Cisco N1kv: Fix update network profile for add tenants"
2014-10-22 00:29:30 +00:00
extensions
Empty files should not contain copyright or license
2014-10-20 00:50:32 +00:00
l3
nit : missing a "%s" in a log message
2014-10-02 17:25:16 +02:00
models
Empty files should not contain copyright or license
2014-10-20 00:50:32 +00:00
n1kv
Use RPC instead of neutron client in metadata agent
2014-10-28 15:52:37 +04:00
service_plugins
Remove @author(s) from copyright statements
2014-09-15 21:40:09 +09:00
__init__.py
Empty files should not contain copyright or license
2014-10-20 00:50:32 +00:00
l2device_plugin_base.py
Remove @author(s) from copyright statements
2014-09-15 21:40:09 +09:00
network_plugin.py
Remove @author(s) from copyright statements
2014-09-15 21:40:09 +09:00
README
Rename Quantum to Neutron
2013-07-06 15:02:43 -04:00

README 

Cisco Neutron Virtual Network Plugin

This plugin implements Neutron v2 APIs and helps configure
topologies consisting of virtual and physical switches.

For more details on use please refer to:
http://wiki.openstack.org/cisco-neutron