e912f5e547
Previously, the OVS bridge name only came from nova.conf. It will be helpful to allow Neutron to specify the name. In particular, this has come up as a requirement for implementing Neutron's "vlan-aware-vms" spec, which will require a separate bridge per port, at least for the existing default ML2+OVS backend. This patch will allow Neutron to customize the bridge name on a per-port basis. The implementation is quite simple, as the use of the config value was already localized to a small area of code. That code just has to prefer a name in vif_details, but fall back to the config value, otherwise. While not immediately needed, it seems convenient to go ahead and apply the same change for VIF_TYPE_BRIDGE (linux bridge) and VIF_TYPE_VHOSTUSER, since it's a trivial addition to the patch. The test cases just follow the same pattern as several other test cases for this code, but makes sure that a custom bridge name in vif_details is honored. Implements blueprint neutron-ovs-bridge-name. Change-Id: I66c25e0c9d971163d0ddad186a0c49f20a77aaa9 Signed-off-by: Russell Bryant <rbryant@redhat.com>
5 lines
135 B
YAML
5 lines
135 B
YAML
---
|
|
features:
|
|
- Add support for allowing Neutron to specify the
|
|
bridge name for the OVS, Linux Bridge, and vhost-user VIF types.
|