[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] 802.1Q VLAN support


  • From: Luis Vinay <luisvinay@xxxxxxxxx>
  • Date: Tue, 11 Dec 2007 10:28:48 -0300
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 11 Dec 2007 05:35:26 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=xf9ptBQ1Cki1GXfEDDOENoy8TC+n6QhkMjYkGkfuvtbNsDDbkSj7mD2Fvvca7tzEoro0BogAChlzjfBbgbM96SO0feiDy3lhe3CJUgfanzkXQIfLHMHDi4EbBJcLBusg0Rr344VF5TZMrPob5vmMpYq7QdFf39I51F6/SwOpCG0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

In my particulary case I'm developing a solution to an ISP that provides
the VM with some other services like IP PBX, file servers, etc., that
integrates to the client LAN, and instead of using firewalls and routers
to separate clients, they use VLANS, the customers can buy their VMs via
a web page, and all the process must be automatic all that plus some
other are the reasons why I'm doing such effort as add this kind of
behavior to Xen.

On Fri, 2007-12-07 at 01:10 +0100, Maximilian Wilhelm wrote:
> Am Wednesday, den  5 December hub Luis Vinay folgendes in die Tasten:
> 
> Hi!
> 
> >   I'm working on adding the 802.1Q vlan suport to Xen. Half of the work
> > is done. The idea is that we can specify something like this on the domU
> > configuration file:
> 
> > vlan = [ 'pdev=eth1, vlanid=123, bridge=xenbr1123',
> >          'pdev=eth1, vlanid=100 ' ]
> 
> What should that actualy do?
> I guess you want to connect vlan 123 from a trunk on eth1 to
> xenbr1123. And the next line?
> 
> Why not just use the linux way and create vlan interfaces?
> e.g. 
> # vconfig add eth1 123
> # vconfig add eth1 100
> 
> and then put eth1.123 to xenbr123 and use this?
> 
> > perhaps even specify an IP address (I founded this usefull in some
> > implementations), and then, as allways:
> 
> What's the purpose of the IP here?
> 
> [...]
> > I'll check if the bridge is already created before connecting the VIF,
> > at domU creation, if not bring it up, and when destroying the domU, also
> > check if other domU is using the same bridge before shuting it down.
> 
> I just create all the vlan interfaces, bondings and bridges via the
> networking setup of my OS on bootup so everything is just there.
> No need to think about networking stuff after setup once.
> 
> > All this raises me some questions:
> 
> >   - Suggestions/advices regarding on where/how put my code?
> >   - Could it bring problems if I add this code in 'xen/xm/create.py'?
> 
> > gopts.var('vlan', val="iface=IFACE,vlanid=VLANID,vlanbridge=VLANBRIDGE",
> >           fn=append_value, default=[],
> >           [...]
> 
> I don't speak parseltongue :)
> 
> Ciao
> Max


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.