This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [PATCH] network -> network-bridge rename WAS: Re: [Xen-devel] RE: he

To: "Nivedita Singhvi" <niv@xxxxxxxxxx>
Subject: RE: [PATCH] network -> network-bridge rename WAS: Re: [Xen-devel] RE: help with bugs
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 5 Aug 2005 01:55:19 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Sean Dague <sean@xxxxxxxxx>
Delivery-date: Fri, 05 Aug 2005 00:53:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWZUcL08jeZZYtaTomDT5tfIfX0pQAA7Swg
Thread-topic: [PATCH] network -> network-bridge rename WAS: Re: [Xen-devel] RE: help with bugs
> > Next, I'd make it such that it's possible to have multiple 
> > network-script lines, each with parameters e.g. something like:
> I started this - but it became less than desirable to stick 
> all of this into xend. That is, what I was thinking was - we 
> simply point the tools to a configuration file that's a top 
> level script, and hide all of the meat of the work inside 
> those scripts. If we change the syntax, we wouldn't require a 
> change to the tools, would be one advantage.
> > (network-script ( network-bridge ( bridge xen-br0 ) ( 
> netdev eth0 ) ) 
> > ) (network-script ( network-bridge ( bridge xen-br1 ) ( 
> netdev eth1 ) 
> > ) )

I guess we could just point it at a top-level script, but it seems a bit
of a cop out, and rather different to the way we configure and invoke
other helper scripts. 

I think at the very least we should allow the 'netdev' to be cloned and
added to the bridge to be specified in xend-config.sxp. I guess this
could be another top-level variable, or better specified as a parameter
to the network-script (as above).

I guess setups with multiple active NICs are relatively rare and can be
dealt with using a top-level script (or configured manually).

NB: The default for 'network-script' should be to run no script at all.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>