On Tue, Mar 22, 2011 at 02:08:00PM -0400, Laine Stump wrote:
> On 03/22/2011 12:23 PM, Daniel P. Berrange wrote:
> >The Open Nebula driver has been unmaintained since it was first
> >introduced. The only commits have been for tree-wide cleanups.
> >It also has a major design flaw, in that it only knows about guests
> >that it has created itself, which makes it of very limited use.
> >
> >Discussions wrt evolution of the VMWare ESX driver, concluded that
> >it should limit itself to single-node ESX operation and not try to
> >manage the multi-node architecture of VirtualCenter. Open Nebula
> >is a cluster like Virtual Center, not a single node system, so
> >reasoning applies.
> >
> >The DeltaCloud project includes an Open Nebula driver and is a much
> >better fit architecturally, since it is explicitly targetting the
> >distributed multihost cluster scenario.
> >
> >Thus this patch deletes the libvirt Open Nebula driver with the
> >recommendation that people use DeltaCloud for managing it instead.
>
> I knew nothing about Open Nebula, so I went searching. I noticed the
> following on its about page:
>
> *"User Interfaces*: Unix-like command line and libvirt interface for
> the management of the cloud infrastructure"
>
> (
http://opennebula.org/documentation:features)
>
> Since they're claiming the libvirt driver as a feature, they will
> probably have something to say about this removal. At the very least
> they'll want to point to the DeltaCloud driver instead of libvirt.
Agreed, we really need to give them a heads-up, which Eric is doing
but that sounds premature for 0.9.0, unless they comment accordingly
within a few days.
Given that they have now confirmed it can be removed, and is already
broken with current Open Nebula releases, any objections to me pushing
the patch for 0.9.0 ?
Daniel
--
|: