WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: LAST_CHECKPOINT and save/restore/migrate compatibility (was Re: [Xen

To: rshriram@xxxxxxxxx
Subject: Re: LAST_CHECKPOINT and save/restore/migrate compatibility (was Re: [Xen-devel] [PATCH 3 of 4] libxc: provide notification of final checkpoint to restore end)
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Mon, 4 Apr 2011 10:42:31 +0100
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 04 Apr 2011 02:43:18 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0epA2uvAcwjamXOd5T2kd3b5DGJkTYxggGErZYqwxzU=; b=TyzCFbv7iur4WVb4Av/kQsLjvfP4YVhxuldTjYc4zqhthnXdSYxJcbm2yLUhDh6KUa 4K2tdJGbepvSnB+AW1acvVlFkmDc2wlqrKFKbuGUOPJgszf4GLh7h0k+SmRxhTKNyDRd cZypD/U7m7LqxD/xlJgMlgokyn2spH0veAMsI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=OL8CTM+JwqDNaRqeaaLa38vJMe2mLs16yhWGJqQKUkif6SnBv9S4G5kEk1rSlCaeCm l4DAhilC2c1rWNN0P9bo+kO/viZ5YtBnOLJjcbwRjPFhbMWBZig4oiYf+vQgis9IAi+6 zqNnnYlDo6Bv1aWlRGaPQGvJBtquWyca+TsTs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTinDgLbzL7EHtysSoanHws7dka3Q7w@xxxxxxxxxxxxxx>
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: <AANLkTik=XfbVbDzEGb3KL-UyN3oWVBvkrj4t+G9Fj_hf@xxxxxxxxxxxxxx> <1301659093.27123.227.camel@xxxxxxxxxxxxxxxxxxxxxx> <068F4087-A4CD-4EB7-B752-780A663D1BC1@xxxxxxxxx> <1301731990.3516.6.camel@xxxxxxxxxxxxxxxxxxxxx> <BANLkTinDgLbzL7EHtysSoanHws7dka3Q7w@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, Apr 2, 2011 at 3:03 PM, Shriram Rajagopalan <rshriram@xxxxxxxxx> wrote:
> I agree with George's suggestion on MORE_CHECKPOINTS, for backwards
> compatibility
> wrt live migration.

It turns out that there actually isn't (I don't believe) a
compatibility issue with live migration. the issue I was seeing was
due to a modification I'd made to libxc to get the XenServer / XCP
toolstack (xapi) working with Xen 4.1.  As long as you're using only
open-source tools, you should still be able to migrate 4.0->4.1 --
there will just be a short delay while the toolstack waits for more
checkpoints.

> But for HA, it doest make much sense if a user is able
> to do HA only
> one way and cannot failback. This is not a upgrade scenario. So, that would
> require some
> exception to be thrown when a version incompatibility is detected. IMO, its
> better to
> let the user handle this limitation than letting him/her do the N->N+1 HA
> and then finding out
> that they cannot failback.

Well, you can't actually do HA while one of the two hosts is being
rebooted anyway. :-)  So I think with backwards compatibility, you
could do it with 3 hosts: run on A with B as a fallback while
upgrading C, then run on A with C as a fallback while upgrading B,
then migrate to C (or just pull the plug on A and let it fall back
normally) and run on C with B as a fallback while upgrading A.
Without backwards compatibility, I think you could do it with 4 (so
you always have 2 hosts of a given version).

Or you could just run it in non-HA mode while the hosts are upgraded
serially; for XenServer / XCP, it normally wouldn't take more than 20
minutes to do both, after which point you could turn on HA again.

 -George

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