All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: heinzm@redhat.com, device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH v3 0/4] dm-replicator: introduce new remote replication target
Date: Wed, 9 Dec 2009 13:38:31 -0500	[thread overview]
Message-ID: <20091209183830.GC30947@redhat.com> (raw)
In-Reply-To: <1260382357.2532.201.camel@mulgrave.site>

On Wed, Dec 09 2009 at  1:12pm -0500,
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:

> On Wed, 2009-12-09 at 05:39 -0500, Christoph Hellwig wrote:
> > On Tue, Dec 08, 2009 at 12:42:27PM -0600, James Bottomley wrote:
> > > Could I just echo Lars' statement.  With the upstream inclusion of drbd,
> > > dm-replicator becomes a *third* replication system asking to be in
> > > kernel.  It is definitely a kernel policy question of whether we want
> > > three separate replicators, and so should be Cc'd to lkml so that people
> > > interested in that can weigh in.
> > 
> > And unliley the previous two this one actually offers the benefit of
> > beeing integrated with our major block device management framework.
> 
> md/nbd *is* integrated with a major block management framework.  The
> fact that it's md not dm reflects the fact that it leverages the md
> raid1 framework to perform the replication and merely uses nbd as a
> remote block transmission pipe.  I'd submit this is the correct way to
> do things.

Yes and no...

As someone who producticized md+nbd for a previous proprietary employer
(standing on the shoulders of the work that was done by steeleye) I can
say that md+nbd can provide the core plumbing but you need quite a bit
of higher-level tools integration to make it _really_ approachable for
the enterprise.  command line and UI interface and backend DB to store
all relations, etc... And all sorts of nasty corner cases (e.g. split
brain and double failure scenarios) are left as an exercise to the
md+nbd user.

> The problem now is that the md raid framework isn't integrated into dm,
> but I think someone else is looking at that ...
> 
> > Interesting that the question comes up now after I was shot down for it
> > in the drbd discussion.
> 
> So the value add of drbd over md/nbd is symmetric active.  I think that
> could be pulled into the md raid infrastructure as well, but someone has
> to figure out how.

md+nbd really isn't the way forward here IMHO..  if anything I think we
need to focus on melding drbd and dm-replicator into the DM framework.

A single system management tool-chain and interface is increasingly
important in the enterprise.

Mike

  reply	other threads:[~2009-12-09 18:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 16:05 [PATCH v3 0/4] dm-replicator: introduce new remote replication target heinzm
2009-12-01 16:05 ` [PATCH v3 1/4] dm-replicator: documentation and module registry heinzm
2009-12-01 16:05   ` [PATCH v3 2/4] dm-replicator: replication log and site link handler interfaces and main replicator module heinzm
2009-12-01 16:05     ` [PATCH v3 3/4] dm-replicator: ringbuffer replication log handler heinzm
2009-12-01 16:05       ` [PATCH v3 4/4] dm-replicator: blockdev site link handler heinzm
2009-12-01 16:41 ` [PATCH v3 0/4] dm-replicator: introduce new remote replication target Lars Marowsky-Bree
2009-12-01 17:18   ` Heinz Mauelshagen
2009-12-08 18:42     ` James Bottomley
2009-12-09 10:39       ` Christoph Hellwig
2009-12-09 18:03         ` Heinz Mauelshagen
2009-12-09 18:14           ` James Bottomley
2009-12-09 18:12         ` James Bottomley
2009-12-09 18:38           ` Mike Snitzer [this message]
2009-12-09 18:46             ` James Bottomley
2009-12-09 19:14               ` Mike Snitzer

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=20091209183830.GC30947@redhat.com \
    --to=snitzer@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dm-devel@redhat.com \
    --cc=heinzm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.