Re: xend deprecation

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Thu, Sep 05, 2013 at 10:12:51AM +0100, George Dunlap wrote:
> On 04/09/13 17:33, Konrad Rzeszutek Wilk wrote:
> >On Wed, Sep 04, 2013 at 04:34:30PM +0100, Ian Campbell wrote:
> >>On Wed, 2013-09-04 at 16:18 +0100, George Dunlap wrote:
> >>>On Wed, Sep 4, 2013 at 3:04 PM, Konrad Rzeszutek Wilk
> >>><konrad.wilk@oracle.com> wrote:
> >>>>On Wed, Sep 04, 2013 at 08:29:07AM +0100, Ian Campbell wrote:
> >>>>>On Tue, 2013-09-03 at 23:06 -0700, Matt Wilson wrote:
> >>>>>>On Tue, Sep 03, 2013 at 09:03:46AM +0100, Ian Campbell wrote:
> >>>>>>>On Mon, 2013-09-02 at 13:32 -0700, Matt Wilson wrote:
> >>>>>>>>Live migration between a system running xend to a system that doesn't
> >>>>>>>>support xend would be a nice-to-have. That probably means some support
> >>>>>>>>for SXP parsing either in libxl or in some compatibility tool.
> >>>>>>>This already works by using xl on the source side, e.g. a guest started
> >>>>>>>with xend on 4.1 can be migrated with 4.1's xl to 4.2.
> >>>>>>>
> >>>>>>>http://lists.xen.org/archives/html/xen-devel/2012-08/msg02191.html
> >>>>>>xl doesn't run everywhere that we need it to.
> >>>>>Details please, or we aren't going to be able to even think about how to
> >>>>>solve this for you.
> >>>>>
> >>>>>BTW You can also do a xend migration to e.g. 4.2 (using the xend whichis
> >>>>>in 4.2) and the use 4.2's xl to do a localhost migrate or a second
> >>>>>remote migrate to another 4.2 system.
> >>>>>
> >>>>>xend's deprecation has been on the cards, and widely known, for several
> >>>>>releases now. It is time to quit stalling and start moving. I intend to
> >>>>>post a patch deleting it as soon as 4.4 is out the door.
> >>>>And I think I might have to lobby hard against removing it.
> >>If by lobby you mean "step up to maintain" then please do.
> >I can surely do that, but I would prefer to have the issues fixed.
> 
> You mean you prefer to have the xl issues fixed? I think we all do;
> so instead of lobbying hard to remove xend, you can lobby hard to
> get the outstanding issues fixed. :-)

Of course I would love to have the issues fixes. But I am running
in a time management problem and I don't thing we will get them all
(along with the other changes we (Oracle) would like to get done)
by the deadline.

Hence as a safety net I am proposing that if we don't get them done,
we postpone the killing of xend.