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


Re: [Xen-API] FT for XCP

To: Mike McClurg <mike.mcclurg@xxxxxxxxxx>
Subject: Re: [Xen-API] FT for XCP
From: R J <torushikeshj@xxxxxxxxx>
Date: Tue, 27 Sep 2011 01:11:33 +0530
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 26 Sep 2011 12:41:51 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3+Z5+0vboLooyUDMZq6IyoNl/CM1QFHtozRE4webwcE=; b=Twd9Bd+9KCfprljwApHpuW4ADfalcKekPqaSoIvFCeSTXD2/ss/YwlhiVNALQDn/AQ aWauRVAsr5E7sKtFJFhF96gPMKN2CaCmxaefdRxQ+e5IQJFbOaZ8Q7WiRsazjNlnownR kI8yZZRdmfn6QZ0UHTXgAnTD6BDSD7eZ3Psgg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E80B233.3030106@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <CAO14VsP9by7CYgSiVN-hY0rJpDk0MYjuJ+FD5Tp3i8w+BcNYHw@xxxxxxxxxxxxxx> <4E8024E5.9020406@xxxxxxxxxx> <CAO14VsMXGyNjbgF0PiJ5MLH_HGwMA6M8yN0Z3Vq5e7tE-tW1bw@xxxxxxxxxxxxxx> <4E80B233.3030106@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Mike.

I'll study on remus and will see what can be done.
From reading the paper, remus seems to be a good option to go with.


On Mon, Sep 26, 2011 at 10:41 PM, Mike McClurg <mike.mcclurg@xxxxxxxxxx> wrote:
[Dropping xen-users and xen-devel]

On 26/09/11 16:58, R J wrote:
> Hello Mike,
> Thank you for suggestion. I would love to incorporate remus in xapi if
> thats possible.
> Remus as its inbuilt logic of detecting checkpoint failure and taking
> decisions accordingly.
> I think there is remus support for xen 3.4
> What do you suggest as my next step ?
I don't know much more about Remus than you do, actually. I think I'd
probably try to figure out how it works on plain Xen first, and then
think about what things xapi would need to do in order to control its

If you get to the point where you'd like to hack on xapi, then you will
probably want to follow along with Project Kronos
(http://wiki.xensource.com/xenwiki/XAPI_on_debian). That's probably the
easiest way to build xapi, and it's how we want to encourage
contributors to develop code. Also, it works on Xen 4.1, which might be
better for Remus integration anyway.


xen-api mailing list
<Prev in Thread] Current Thread [Next in Thread>