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: Jakob Praher <jakob@xxxxxxxxxxx>
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 22:26:18 +0400
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 15 Aug 2011 11:26:34 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=22Nr1+o1VT4z8kRqIfU1/6jaxDXjk7qVLrzdQGbmGF8=; b=YBBk1p9eF5DlsgnYdSTMQMV9sd7YMFmkalG9CMlavK9iqXQikoaucYn/dMHlOxUygD e7Dl7ghqm5VA7VLiujPG2dX1tTwWZORDb52rNuOu8nSWIyd47N06nrffToI0Nnnt8Svz Ov/NkK8KW8To9kiECO8SzoZhb8d4W0ojj+CMU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E495F82.6000403@xxxxxxxxxxx>
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> <4E48EDA4.8090203@xxxxxxxxx> <4E48F452.1050508@xxxxxxxxxxx> <1313409429.1945.32.camel@mabase> <4E494896.3060007@xxxxxxxxxxx> <1313429260.1945.41.camel@mabase> <4E495F82.6000403@xxxxxxxxxxx>
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

FT/HA relationship more complificated then 'better/worse', they solves
different problems and asking for different price for this (f.e.
completely FT machine will run slower that normal one).
I have to look into the definition of these. Maybe I what I refer to FT
is just redundancy - so in that sense FT is already the thing I want to
achieve right now.

Ok, terms:

redundancy: your host consist of few parts: if one part is failed, other will continue to provide necessary data. Refer to: disks, network links, power units, even memory and processors. high availability: if one of your hosts down, other will be reconfigured automatically to continue/restart work of failed host. fault tolerance: your host tasks running simultaneously on two ore more hosts and failed host does not cause any (significant) delay in task execution.

Most web application works fine with HA, FT usually needed for some poorly written applications (like terminal servers).

Please note that XCP does not contain code for native XenServer HA - it
depends on Windows (as far as I understand), the 'HA' in XCP limited to
domain restart in case of crash/host reboot.
Okay. See above I just want the thing to be fault tolerant, I can live
with having to restart a VM in case of a host crash right now.
I only want to make sure I can start the system on the still running
server (given that I only utilize 50 % of both systems).

Cheers,


This is not FT, this is HA. If you don't need automatic restart (e.g. monitoring of health), XCP will works fine.

When one of the hosts is down, you simply saying:

xe vm-reset-power-state
xe vm-start

and VM staring on any other available host in the pool.

Note: XCP have no any technology to make storage HA/FT - you need to find/use separate solution.

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