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] New API Document and C Bindings

To: Gareth S Bestor <bestor@xxxxxxxxxx>
Subject: Re: [Xen-API] New API Document and C Bindings
From: Ronald Perez <ronpz@xxxxxxxxxx>
Date: Fri, 15 Sep 2006 10:07:56 -0400
Cc: xen-api-bounces@xxxxxxxxxxxxxxxxxxx, Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 15 Sep 2006 07:08:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <OFEF081C64.B61B9289-ON882571EA.004C7507-882571EA.004CB2C2@LocalDomain>
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

Gareth S Bestor/Beaverton/IBM wrote on 09/15/2006 09:57:44 AM:

> certainly the CIM model supports the notion of 'recursive' virtualization hosting.
> However, I'm unclear how much of that we want to try and slap into the API for
> xend; in particular, are you thinking the host system will now running multipe
> xend's, in different Domains?

> - G


You're correct to point out the differences between the CIM modeling goals and the Xen API (thanks, at this early stage, I often confuse the two).

I guess I'm saying that the Xen API should not preclude such a direct mapping from model -> implementation. In practical terms, this could include the existence of multiple xend's (or equivalent) on a platform. This could be for the parent -> child scenario I mentioned before, or it could just be a high availability issue (e.g., sort of a dom0 hot back-up). Granted, there's a lot of clever engineering needed to make any of these scenarios a reality :-)

So in summary, I tend to agree more with John's and Dan's approach (but I'd like to see some details in regard to the capabilities Dan mentions).

xen-api mailing list