Open vSwitch to use patch ports in place of veth pairs for vlan n/w
The current implementation for connecting openvswtich bridges is via veth pairs when not using vxlan or gre tunnels.
This blueprint proposes the use of openvswitch patch-ports for local, flat and vlan deployments.
Utilizing patch-ports in place of veth pairs enables the use of performant user space virtual switches, example, NFV context, whilst providing some general performance benefits due to the reduced number of lookups.
A fall back to veth pairs shall be implemented in the eventuality patch-ports are not supported.
* changes to neutron/
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- Medium
- Drafter:
- David Mahony
- Direction:
- Needs approval
- Assignee:
- David Mahony
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- David Mahony
Related branches
Related bugs
Bug #1285335: Openvswitch agent should use ovs patch ports instead veths | Fix Released |
Bug #1331569: Open vSwitch Agent should use ovs_lib to list bridges not ip_lib | Fix Released |
Sprints
Whiteboard
12-June (mestery): Removing Juno target for now as the specification isn't approved. Once it's approved, we can retarget this.
28-May (mestery): Moving this to Juno-2, as the BP is not approved and Juno-1 is only 2 weeks out.
code has been developed, and to be released shortly
Gerrit topic: https:/
Addressed by: https:/
enable patch ports when availble for connecting openvswitch bridges
Gerrit topic: https:/
Addressed by: https:/
enables patch ports when availble for connecting openvswitch bridges
code has been abandoned and will be addressed by the following bugs
Addressed by: https:/
Openvswitch agent should use ovs patch ports instead veths
Addressed by: https:/
Open vSwitch Agent should use ovs_lib to list bridges not ip_lib
this feature should now be supported with the completion of both bugs above (1331569,1285335)