5aab6a5779
This option provides another way to attach to a specific bridge that is not quite equivalent with how bridge_mappings work in the L2 agent. This creates inconsistencies between how the L3 agent behaves when configured with a bridge_mapping and provider properties of the Neutron network vs. when it just ignores all L2 stuff and plugs itself directly into the bridge. See the bug report for more info. Change-Id: I37de3cd6eaaf34856fa72753f471f4f0a9381836 Closes-Bug: #1491668
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
- Networking Guide
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- 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.