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

[Xen-API] Network class

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Network class
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Fri, 13 Apr 2007 09:25:05 -0400
Delivery-date: Fri, 13 Apr 2007 06:23:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx

Hello!

  is the network class representing a network 'bridge' with VIFs and PIFs in case bridging is configured in domain-0? Or is the intention to get rid of the explicit configuration of xend to use routing or bridging and rely on the programmatic configuration of the VIFs to either configure them for bridging or routing?

  Stefan
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api
<Prev in Thread] Current Thread [Next in Thread>