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-api

Re: [Xen-API] One resource pool and local lvm SR mirrored using DRBD

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] One resource pool and local lvm SR mirrored using DRBD
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Mon, 15 Aug 2011 13:57:56 +0400
Delivery-date: Mon, 15 Aug 2011 02:59:04 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/VXAzopvDtuacYF9m67n7WVbNtMyo79SSbn6tsV2lr8=; b=LBBos/YlukUwyhT0XBIkvHnu7jo1e69fEAEqdBspdTgkSmSqBVPEdSpknI+C8sQuGz Ygf0GWomncLl9empMLOBiMnPgenPn2nvVAiQVSNWE/LbiixjNjj8buBkhYsb2wxNxmB6 qwKX7hWvQZB2g5873ky+FBXb1uZe9c84qW17s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <j2ape2$r6v$1@xxxxxxxxxxxxxxx>
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: <j2ape2$r6v$1@xxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Icedove/3.1.11
Right now we running last tests before product deployment of DRBD-backed iscsi target with multipath. I found no specific problem at this moment (except the need to patching ISCSISR.py for complete multipath support). But I don' understand, why you need to do cross-pool migration for FT. In any way you can not achive FT with current XCP state, only HA.

The difference between FT and HA: If server broken, FT-machine continue to run without any traces of fault, in case of HA machine just (almost instantly) restarting on other available hosts in the pool. FT is not magic key, because if VM do some bad thing (crashed) HA restart it, and FT will do nothing.

On 15.08.2011 13:38, Jakob Praher wrote:
Dear List,

I have a question regarding a fault-tolerant setup of XCP.
We have two hosts that are in one resource pool.
Furthermore we are trying to make two SRs (storage repos) as local lvm
volume groups where one volume group is active (owned) by one server,
and the other volume group is active on the other server.

In case of failure because of the common resource pool all the meta
information concerning VMs are still available. After degrading the
system to one host the SR is still owned by the failed server. Is there
an easy way to migrate the SR? Is anybody using a similar solution or
what are your best practices?

I think CrossPool-Migration is not an option for us since we want to
keep only one resource pool for both servers.

Another question: I am currently using 1.1 of XCP - what is the best way
to compile system (like DRBD) RPMs for this version. Since the DDK is
not available I also have troubles getting the XCP distribition
installed into a guest VM so that I can add development packages to it
and compile the package there. Is there a base image that I can use so
that I have the right devel rpms? From yum repos.d I see that it is a
CentOS 5.

Any help is appreaciated.

Cheers,
Jakob


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api