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-devel] [PATCH] remus: support DRBD disk backends

To: Shriram Rajagopalan <rshriram@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] remus: support DRBD disk backends
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Fri, 20 May 2011 18:21:58 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 20 May 2011 10:22:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <666dd2576bc41ccb9f4c.1305604440@xxxxxxxxxxxxxxxxxxx>
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>
Newsgroups: chiark.mail.xen.devel
References: <666dd2576bc41ccb9f4c.1305604440@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Shriram Rajagopalan writes ("[Xen-devel] [PATCH] remus: support DRBD disk 
> remus: support DRBD disk backends
> DRBD disk backends can be used instead of tapdisk backends for Remus.
> This requires a Remus style disk replication protocol (asynchronous
> replication with output buffering at backup), that is not available in
> standard DRBD code. A modified version that supports this new replication
> protocol is available from git://aramis.nss.cs.ubc.ca/drbd-8.3-remus

Normally, "drbd:" disk strings would be handled by
/etc/xen/scripts/block-drbd, I think ?  Why does remus need to do
something different ?

The block device handling in libxl is in a bit of a state of flux but
perhaps it would be useful to start thinking about whether remus could
use it ?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>