RE: [PATCH] network -> network-bridge rename WAS: Re: [Xen-devel] RE: help with bugs

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

> > 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.


Ian 

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