f697cddda6
This patch follows up on the Nova work that allows Neutron to pass an OVS 'bridge_name' in a port's vif_details [1] and the os-vif work that ensures the OVS bridge passed in as 'bridge_name' (or the config default of 'br-int') is created [2]. If the port is a trunk's parent port, then bridge_name will be set to a generated trunk bridge name for vlan-aware VMs. Otherwise, the bridge_name field will remain empty. Note: until Nova integrates os-vif [3] and uses a release that contains the change in [2], the trunk bridge will not actually be created by Nova/os-vif. It is expected to be integrated for the Newton release. Until then, this Nova-equivalent patch can be used for testing purposes [4]. [1] https://review.openstack.org/#/c/260700/ [2] https://review.openstack.org/#/c/330818/ [3] https://review.openstack.org/#/c/269672/ [4] https://review.openstack.org/#/c/332474/ Partially-implements: blueprint vlan-aware-vms Change-Id: Iad72d163bc406df65866f6d962abcb78596828e7
Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
- Neutron Administrator Guide
- Neutron Developer Guide
- Networking Guide
- Neutron API Reference:
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.