WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] network -> network-bridge rename WAS: Re: RE: help with bugs
From: Sean Dague <sean@xxxxxxxxx>
Date: Fri, 5 Aug 2005 08:18:28 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 05 Aug 2005 12:17:14 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D28297D@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Mail-followup-to: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Nivedita Singhvi <niv@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <A95E2296287EAD4EB592B5DEEFCE0E9D28297D@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Fri, Aug 05, 2005 at 01:55:19AM +0100, Ian Pratt wrote:
> > > 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).

I'd disagree with that (unless I am misunderstanding the definition of
active).  Every pizza box server I've seen ship in the last 3 years has had
dual onboard nics.  Dual nic setup for server (one for production and one
for administration) is best practice for any reasonable size server
environment.

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

-- 
__________________________________________________________________

Sean Dague                                       Mid-Hudson Valley
sean at dague dot net                            Linux Users Group
http://dague.net                                 http://mhvlug.org

There is no silver bullet.  Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________

Attachment: pgpd6MFActiGo.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>