How to handle virtual networking effectively in the cloud

Registered by Nick Barcet on 2010-10-20

Current network topologies in the cloud bring a set of limitations which are bothering for the people implementing them:
- VLAN Tagging to separate multiple tenants have a 4096 limit that can be easily reached at ISPs
- Amazon public address redirection don't allow proper advertisement of services
- Security tunnels use complicated or less efficients models
New projects, such as openvswitch, could bring additional answers for people building virtual infrastructure on top of Ubuntu. This session has for goal to define which should be enabled withing our OS to lead the way in that space.

Blueprint information

Status:
Not started
Approver:
Robbie Williamson
Priority:
Medium
Drafter:
Nick Barcet
Direction:
Approved
Assignee:
Chuck Short
Definition:
Approved
Series goal:
None
Implementation:
Deferred
Milestone target:
None

Related branches

Sprints

Whiteboard

 * VLAN Tagging to separate multiple tenants have a 4096 limit that can be easily reached at ISPs
 Address space can be extended, but it's a hack.
 OpenStack is looking to integrate openvswitch. Openvswitch will also be in Xen.It isn't packaged in Ubuntu yet."It is the default switch in the Xen Cloud Platform and also supports Xen, XenServer, KVM, and VirtualBox." http://openvswitch.org/
 Tinc (http://openvswitch.org/) and n2n (http://www.ntop.org/n2n/). The latter gives you a mesh structure, each node of which knows about a super-server, which acts as a switch. Tinc uses a discovery mechanism and dynamic switching.

 * Security tunnels use complicated or less efficients models
 Tinc?

Note that openvswitch landed in Ubuntu recently through Debian unstable imports: https://launchpad.net/ubuntu/+source/openvswitch

ACTIONS:
[zulcss] Write openvswitch to the checkbox inteface: POSTPONED

(?)

Work Items