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]Change default network schema in network-bridge

To: Zhigang Wang <zhigang.x.wang@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH]Change default network schema in network-bridge
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 23 Jun 2009 10:01:58 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 23 Jun 2009 02:02:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A40630C.4010708@xxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4A40630C.4010708@xxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, Jun 23, 2009 at 01:07:24PM +0800, Zhigang Wang wrote:
> hi,
> 
> the default network-bridge renames network interfaces and often confuse 
> people.
> 
> this patch changes the network-bridge schema to:
> 
> # start:
> # Creates the bridge
> # Copies the IP and MAC addresses from netdev to bridge
> # Enslaves netdev to bridge
> #
> # stop:
> # Removes netdev from the bridge
> # Transfers addresses, routes from bridge to netdev
> # Deletes bridge
> 
> No rename will be performed.  Eg.
> 
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.000e0cd85dfe       no              eth0
> 
> IP/route will be transfered to xenbr0 at start.
> 
> I also add a extra script network-bridges to perform on all ethernet cards.
> and network-dummy if user doesn't want to xend to manage dom0 networking.
> 
> This patch obsolete my last patch, titled: [PATCH]Fix network-bridge ifup 
> problem.
> 
> CC to Daniel for comments.



I agree with your thought that it makes more sense to just leave the 
original device name alone, and not rename anything. The reason it
currently does renaming is that this was closer to the previous version
of network-bridge using netloop, and so made upgrades slightly easier
for existing Xen users. 

I don't really have a strong opinion on whether network-bridge should  now 
be changed again to not do renaming of eth0. These days my recommendation
is for people to set '(network-script /bin/true)' and then just use their 
OS distributions network scripts to add a bridge device.  The end result 
is the same, but this has the advantage that the  network is setup correctly
right from start, rather than having to modify it on the fly when apps may 
already have started using the network. We've got docs for Fedora/RHEL/
Debian/Ubuntu here

http://wiki.libvirt.org/page/Networking#Bridged_networking_.28aka_.22shared_physical_device.22.29

Regards,
Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

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