[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Xend vnet support to be removed


  • To: "Ewan Mellor" <ewan@xxxxxxxxxxxxx>, "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Fri, 9 Dec 2005 16:20:47 -0000
  • Delivery-date: Fri, 09 Dec 2005 16:21:44 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcX82x/jXPjN8tB+Su6P5bNlZLSOtAAARUvA
  • Thread-topic: [Xen-devel] Xend vnet support to be removed

> Unless someone speaks up, Xend vnet support will be removed.  
> It is broken, unused, and unloved (as far as I know).  This 
> is the xm vnet-list, vnet-create, and vnet-delete commands, 
> as well as all the Xend support behind that (XendVnet.py, 
> SrvVnetDir.py, plus plumbing in xm/main.py and XendClient.py).

That's a shame, but unless someone steps up to maintain it then I'm
agree it makes sense to pull it. 

We should certianly hide it from the usage message. Perhaps we need a
special environment variable or command line option to un-hide broken or
under-development features? I think this would be generally useful.

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.