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


[Xen-devel] Re: Announcing: Open OVF project source code availibility

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: [Xen-devel] Re: Announcing: Open OVF project source code availibility
From: Mike Day <ncmike@xxxxxxxxxxx>
Date: Tue, 12 Aug 2008 12:59:11 -0400
Cc: "Mike D. Day" <ncmike@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, smoser@xxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Aug 2008 09:59:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080812154236.GS13067@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>
Organization: Ultra Adventures http://www.ncultra.org
References: <20080812143432.GA8431@xxxxxxxxxxxxxxxxxxxxxx> <20080812144656.GQ13067@xxxxxxxxxx> <20080812152634.GA8457@xxxxxxxxxxxxxxxxxxxxxx> <20080812154236.GS13067@xxxxxxxxxx>
Reply-to: ncmike@xxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.17+20080114 (2008-01-14)
On 12/08/08 16:42 +0100, Daniel P. Berrange wrote:

> > For runtime integration, we are planning on implementing an XML-RPC
> > interface into and out of the ovf library, which will allow any other
> > runtime code to interact with it. 
> It is the runtime integration I was refering to. The open-ovf tools
> are all python. So is virt-manage/install/image. If these tools were
> under a license that were compatible with usage from a GPL  licensed
> app, then I could simply call into the OVF APIs. Building an XML-RPC
> interface just to call into functions for manipulating OVF files is
> rather overkill. 

Perhaps locally, but certainly not overkill for remote access. Local
access to XML-RPC via the loopback is still pretty efficient within
the realm of interpreted languages. And the original OVA environment
specification requires a remote API. (The DMTF did not adopt the
environment services in its standard.) For example, a software
appliance running in a guest needs to query the OVF daemon for
information about its hosting hypervisor. This is best done by remote
procedure calls.
> But perhaps you don't intend to maintain the python libraries as an
> official 'public' API for other apps to use ?

We hope to establish remote APIs for use by guests at
runtime. Whatever else comes about is up to the community.

Mike Day
AIM: ncmikeday |  Yahoo IM: ultra.runner
PGP key: http://www.ncultra.org/ncmike/pubkey.asc

Xen-devel mailing list