openstack team mailing list archive

[Ewan Mellor <Ewan.Mellor@xxxxxxxxxxxxx>]

> -----Original Message-----
> From: openstack-bounces+ewan.mellor=citrix.com@xxxxxxxxxxxxxxxxxxx
> [mailto:openstack-bounces+ewan.mellor=citrix.com@xxxxxxxxxxxxxxxxxxx]
> On Behalf Of Thierry Carrez
> Sent: Thursday, February 02, 2012 12:53 AM
> To: openstack@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Openstack] [Nova] Essex dead wood cutting
> 
> Thierry Carrez wrote:
> > Just as Nova enters feature freeze, it sounds like a good moment to
> > consider removing deprecated, known-buggy-and-unmaintained or useless
> > feature code from the Essex tree.
> >
> > Here are my suggestions for removal:
> >
> > - Ajaxterm (unmaintained, security issues, replaced by VNC console)
> > - Hyper-V support (known broken and unmaintained)
> 
> While we are at it (and since I'm getting used to press coverage),
> what's the state of the "VMWareAPI" support ?
> 
> I knew Hyper-V was not working because bugs were reported against it...
> but I don't really know how functional vmwareapi actually is.

The VMware support is in _much_ better shape than the Hyper-V support.  We haven't done much to it in the last few weeks (focusing on XenServer support right now) but we've been actively using it from stable/diablo and early essex.  Sateesh did some fixups to it when the multinic support went in, and it was in good shape then.

There's certainly no need to remove it.  It's clearly not tier 1 like XenServer and KVM, but it's in decent enough shape.

Cheers,

Ewan.