From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] remus: support DRBD disk backends
Date: Sun, 22 May 2011 13:21:14 -0400 [thread overview]
Message-ID: <BANLkTinmZbDMprR9NmP9E7JvKVidF8wg9A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimDzk29jGgzz9-O7fk3=skugbAROQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2096 bytes --]
On Fri, May 20, 2011 at 9:23 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>wrote:
> On Fri, May 20, 2011 at 10:21 AM, Ian Jackson <Ian.Jackson@eu.citrix.com>wrote:
>
>> Shriram Rajagopalan writes ("[Xen-devel] [PATCH] remus: support DRBD disk
>> backends"):
>> > 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 ?
>>
>> Yep. So, remus does use that. But DRBD does not have the replication
> protocol
> that remus needs. Its asynchronous/synchronous replication does not
> fit Remus'
> requirement's of a checkpoint based replication, wherein, the backup has to
> "buffer"
> the disk writes in memory and release them only when the checkpoint is
> being made.
>
> So, the DRBD version supplied in the link above supports a new protocol D,
> that does
> just that. Now, in order to send the tell to the backup that it can "flush"
> the buffered
> disk writes to disk, some sort signalling has to be done from remus, after
> VM is
> suspended. And this patch does just that.
>
>> 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 ?
>>
>> Dont understand. I do realize that libxl style of block device handling is
> not stabilized,
> and it doesnt support DRBD at the moment. But I am working on remus patches
> for
> libxl support :). I ll start a separate discussion soon on that, but I
> wanted to get this
> one out of the way first.
>
> thanks
> shriram
>
>> Thanks,
>> Ian.
>>
>>
> Ian, is there anything else you would like to know before pulling in this
patch?
shriram
[-- Attachment #1.2: Type: text/html, Size: 3420 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-22 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 3:54 [PATCH] remus: support DRBD disk backends Shriram Rajagopalan
2011-05-20 17:21 ` Ian Jackson
2011-05-21 1:23 ` Shriram Rajagopalan
2011-05-22 17:21 ` Shriram Rajagopalan [this message]
2011-05-26 14:04 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinmZbDMprR9NmP9E7JvKVidF8wg9A@mail.gmail.com \
--to=rshriram@cs.ubc.ca \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).