Russell BryantandMatt Riedemann
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>
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast