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: Mike Day <ncmike@xxxxxxxxxxx>
Subject: [Xen-devel] Re: Announcing: Open OVF project source code availibility
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 12 Aug 2008 16:42:36 +0100
Cc: "Mike D. Day" <ncmike@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, smoser@xxxxxxxxxx
Delivery-date: Tue, 12 Aug 2008 08:43:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080812152634.GA8457@xxxxxxxxxxxxxxxxxxxxxx>
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: <20080812143432.GA8431@xxxxxxxxxxxxxxxxxxxxxx> <20080812144656.GQ13067@xxxxxxxxxx> <20080812152634.GA8457@xxxxxxxxxxxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, Aug 12, 2008 at 11:26:34AM -0400, Mike Day wrote:
> On 12/08/08 15:46 +0100, Daniel P. Berrange wrote:
> > 
> > Why was the Eclipse Public License chosen ?  This license is not
> > compatible with the GPL[1], so no GPL licensed app can make use of
> > this code :-( For example it makes it impossible to use this code to
> > assist in supporting OVF in virt-manager, virt-install or virt-image
> > 
> >   http://en.wikipedia.org/wiki/Eclipse_Public_License
> > 
> >   "The EPL 1.0 is not compatible with the GPL, and a work created by
> >    combining a work licensed under the GPL with a work licensed under
> >    the EPL cannot be lawfully distributed."
> > 
> As a file format, the output from open-ovf can be used by any
> code of any license. That is, any code can consume an OVF file.

Yep, that's not what I'm concerned with.

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

But perhaps you don't intend to maintain the python libraries as an
official 'public' API for other apps to use ?

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