041703c004
Fixes bug 1250969
This fix addresses improper behavior with the Cisco Nexus plugin's
selection of Nexus switch on which to place a Switch Virtual Interface
(SVI) when round-robin switch placement is enabled.
The expected behavior when round-robin SVI switch selection is configured
via the cisco_plugins.ini file, i.e.:
[cisco]
nexus_l3_enable = True
svi_round_robin = True
is that when a virtual router interface is created, the Nexus plugin should
select the Nexus switch with the least number of SVI interfaces configured
for creating the new SVI. The current selection is based on the first
entry in a dictionary, and is therefore indeterminate.
Similarly, this fix also addresses incorrect behavior when round-robin
selection is disabled. In this case, the desired behavior is that
the plugin should select the first switch which appears in the Nexus
switch configuration. Instead, the current selection is also based on the
first entry in a dictionary, and is likewise indeterminate.
Change-Id: I548c1efaa8b54695246251b6823ab59e077836fe
|
||
|---|---|---|
| .. | ||
| common | ||
| db | ||
| extensions | ||
| models | ||
| n1kv | ||
| nexus | ||
| test | ||
| __init__.py | ||
| l2device_plugin_base.py | ||
| network_plugin.py | ||
| 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