Libvirt: New VIF type to allow routing VM data instead of bridging it
We propose to add a new VIF type, VIF_TYPE_TAP, whose meaning is
that data to/from VMs may be routed by their immediate compute host
instead of being bridged. This approach enables various alternative
approaches to providing connectivity between VMs - particularly in
deployments where those VMs only require services at layer 3 (IP) and
above - and it is still possible to implement, through iptables and
route distribution filters, all of the detailed connectivity and
security policies that are implied by any given set of OpenStack's
networking, security group and router configurations.
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- Nell Jerram
- Direction:
- Approved
- Assignee:
- Nell Jerram
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
- Implemented
- Milestone target:
- 12.0.0
- Started by
- Nell Jerram
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
Addressed by: https:/
New VIF type for routing VM data instead of bridging it
Addressed by: https:/
New VIF type to allow routing VM data instead of bridging it
Only just approved, but seems like all the code is up, so keeping this in kilo for now. --johnthetubaguy 26th Jan 2015
Sorry, we have now hit the non-priority feature freeze for kilo. Please resubmit your spec for the L release. --johnthetubaguy 5th Feb 2015
Approved for liberty. --johnthetubaguy 20th April 2015
Gerrit topic: https:/
Addressed by: https:/
Add new VIF type VIF_TYPE_TAP