From: Al Boldi <a1426z@gawab.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Philipp Reisner <philipp.reisner@linbit.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <jens.axboe@oracle.com>, Greg KH <gregkh@suse.de>,
Neil Brown <neilb@suse.de>, Sam Ravnborg <sam@ravnborg.org>,
Dave Jones <davej@redhat.com>,
Nikanth Karthikesan <knikanth@suse.de>,
Lars Marowsky-Bree <lmb@suse.de>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Kyle Moffett <kyle@moffetthome.net>,
Bart Van Assche <bart.vanassche@gmail.com>,
drbd-dev@lists.linbit.com,
Lars Ellenberg <lars.ellenberg@linbit.com>
Subject: Re: [PATCH 00/15] drbd: a block device for HA clusters
Date: Fri, 26 Jun 2009 21:42:30 +0300 [thread overview]
Message-ID: <200906262142.30895.a1426z@gawab.com> (raw)
In-Reply-To: <1246032541.3925.53.camel@mulgrave.site>
James Bottomley wrote:
> On Fri, 2009-06-26 at 18:43 +0300, Al Boldi wrote:
> > James Bottomley wrote:
> > > On Fri, 2009-06-26 at 17:15 +0300, Al Boldi wrote:
> > > > Philipp Reisner wrote:
> > > > > Short Description
> > > > >
> > > > > DRBD is a shared-nothing, synchronously replicated block device.
> > > >
> > > > What do you mean by "shared-nothing"?
> > >
> > > If you actually type "shared nothing" into google, the first hit will
> > > be the wikipedia article describing this.
> >
> > Sure, but the point here is to choose a description that is clear and
> > self-explanatory, and "shared-nothing" is neither clear nor
> > self-explanatory.
>
> It is clear because everyone agrees on the definition.
Everyone involved in the project maybe, but not everyone interested in "a
block device for HA clusters". And you don't want to turn them of by using
terminology to explain terminology, especially when it's misleading. Many
OpenSource projects fail merely for this reason.
> And it is self
> explanatory because it's an art term for a well defined concept which
> forms one of the building blocks of the nomenclature used in clustering.
> Even if you're not familiar with clustering terminology, the definitions
> are easy to find via search engines.
>
> If you want to find useful quibbles, the term synchronously is wrong:
> DRBD is capable of both synchronous and asynchronous replication.
Ok, so maybe change the description to reflect this capability.
Something like: DRBD is an independent, synch/async replicated block device.
Thanks!
--
Al
next prev parent reply other threads:[~2009-06-26 18:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 12:01 Philipp Reisner
2009-06-26 12:01 ` [PATCH 01/15] lru_cache: track a fixed size cache of equal sized objects Philipp Reisner
2009-06-26 12:01 ` [PATCH 02/15] drbd: tracking of active extents Philipp Reisner
2009-06-26 12:01 ` [PATCH 03/15] drbd: dirty bitmap Philipp Reisner
2009-06-26 12:01 ` [PATCH 04/15] drbd: request state processing Philipp Reisner
2009-06-26 12:01 ` [PATCH 05/15] drbd: user space interface (based upon connector/netlink) Philipp Reisner
2009-06-26 12:01 ` [PATCH 06/15] drbd: internal data structures Philipp Reisner
2009-06-26 12:01 ` [PATCH 07/15] drbd: device state engine Philipp Reisner
2009-06-26 12:01 ` [PATCH 08/15] drbd: network IO threads Philipp Reisner
2009-06-26 12:01 ` [PATCH 09/15] drbd: the /proc/drbd interface Philipp Reisner
2009-06-26 12:01 ` [PATCH 10/15] drbd: worker thread Philipp Reisner
2009-06-26 12:01 ` [PATCH 11/15] drbd: variable length integer encoding Philipp Reisner
2009-06-26 12:01 ` [PATCH 12/15] drbd: String constants Philipp Reisner
2009-06-26 12:01 ` [PATCH 13/15] drbd: tracepoint probes Philipp Reisner
2009-06-26 12:01 ` [PATCH 14/15] drbd: documentation Philipp Reisner
2009-06-26 12:01 ` [PATCH 15/15] drbd: Kconfig and Makefile bits Philipp Reisner
2009-06-26 14:15 ` [PATCH 00/15] drbd: a block device for HA clusters Al Boldi
2009-06-26 14:25 ` James Bottomley
2009-06-26 15:43 ` Al Boldi
2009-06-26 16:09 ` James Bottomley
2009-06-26 18:42 ` Al Boldi [this message]
2009-06-26 19:32 ` david
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=200906262142.30895.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bart.vanassche@gmail.com \
--cc=davej@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=gregkh@suse.de \
--cc=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--cc=kyle@moffetthome.net \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=nab@linux-iscsi.org \
--cc=neilb@suse.de \
--cc=philipp.reisner@linbit.com \
--cc=sam@ravnborg.org \
/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
all inboxes | Powered by JetHome®