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: [Xen-API] Xen Management API draft

To: "Mike D. Day" <ncmike@xxxxxxxxxx>
Subject: Re: [Xen-API] Xen Management API draft
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Mon, 26 Jun 2006 16:18:37 +0100
Cc: Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 26 Jun 2006 08:18:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <449BEFAD.7000008@xxxxxxxxxx>
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>
References: <20060622170130.GI25606@xxxxxxxxxxxxxxxxxxxxxx> <449BEE61.1040401@xxxxxxxxxx> <449BEFAD.7000008@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Jun 23, 2006 at 09:42:05AM -0400, Mike D. Day wrote:

> Mike D. Day wrote:
> >Ewan Mellor wrote:
> >>Attached is a draft Xen Management API.  This document presents our 
> One item I forgot in the previous email:
> The NIC field of the Network class should be a list (Set) so that we can 
> signify NIC teaming. (Combining physical NICs in a single host interface 
> to achieve greater bandwidth).

Is that better than specifying the NIC as "bond0" or whatever and relying on
out-of-band mechanisms to get the device bonding set up?  I'm worried that
simply specifying the NIC list is not going far enough, so actually what we
need to do is a) throw our hands up and say that we don't handle it or b)
put in an awful lot of network-related modelling.

I don't really know how much effort and complexity is involved in b).  Perhaps
someone who understands networking better than me can tell us how much
complexity you need before things start to be useful.


xen-api mailing list