Hi, The scenario you describe is already supported by OpenNebula. If you use any of the network isolation drivers [1], users can create new isolated networks using the VLAN=YES attribute in the VNet template [2].
To make things even easier, we recently released a virtual router appliance [3]. Users can include it in each one of their isolated networks, and it will take care of the DHCP and routing to the exterior. Cheers [1] http://opennebula.org/documentation:rel3.6:nm [2] http://opennebula.org/documentation:rel3.6:vnet_template [3] http://opennebula.org/documentation:rel3.6:router -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmar...@opennebula.org> On Tue, Jul 17, 2012 at 10:14 PM, Ricardo Duarte <rjt...@hotmail.com> wrote: > Hi there, > > Sorry for the email storm. > I'm not sure how to request a new feature, so I'm doing it on the mailing > list. > > It would be amazing if OpenNebula could support "VLAN Leases". > An administrator would set a pool of VLANs, or set the number of VLANs > available. No IP addressing would be set on One. > Then, a regular user could "hold" a VLAN for himself, and attach instances > to it. > The VLANs shouldn't be routable. OpenNebula could even create them > automatically, if using Openvswitch. For regular bridges, the administrator > would only have to add the VLAN range to the host uplinks, without setting > any IP address on the switch (pure L2 bridged VLANs). > > The use case would be the following: > - user would hold a VLAN > - user creates a template with a router image that has two interfaces. One > connects to a public lease (one fo the IPs curently supported) and the > other one connects to the holded VLAN > - user then creates instances on the new VLAN, and adds whatever IP he > wants. User just have to ensure it sets up the router properly > - no IP collisions will ever occur, because layer 2 is isolated with VLAN > and layer 3 is isolated with NAT/router/nwfilters > > Regards, > Ricardo > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org