Support external physical bridge mapping in linuxbridge
The linuxbridge-agent currently creates a bridge for each physical network used as a flat network, moving any existing IP address from the interface to the newly created bridge. This is very helpful in some cases, but there are other cases where the ability to use a pre-existing (user-defined) bridge. For instance, the same physical network might need to be bridged for other purposes, or the agent moving the system's IP might not be desired or cause some unexpected error for the pre-defined environment.
In this proposal, bridge_mapping is introduced to use the existing physical bridge in the linuxbridge-agent, instead of creating a new one.
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- Low
- Drafter:
- Li Ma
- Direction:
- Approved
- Assignee:
- Li Ma
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
-
Implemented
- Milestone target:
-
7.0.0
- Started by
- Li Ma
- Completed by
- Kyle Mestery
Related branches
Related bugs
| Bug #1105488: linuxbridge agent needs ability to use pre-configured physical network bridges (nova-related) | Won't Fix |
Sprints
Whiteboard
sept-1-2015(armax): no meaningful reviews up until now...optimisti
Gerrit topic: https:/
Addressed by: https:/
Implement external physical bridge mapping in linuxbridge
# NOTE: Nova hard-code 'brq' + net-id as bridge name in libvirt configuration, so it is impossible for neutron to define bridge name for instances. A good design is that Neutron should send bridge name to Nova and Nova just make it effective.
Addressed by: https:/
Implement external physical bridge mapping in linuxbridge
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Merge remote-tracking branch 'origin/master' into merge-pecan-
Gerrit topic: https:/
Addressed by: https:/
Merge remote-tracking branch 'origin/master' into walnut
