From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] More than two nodes in one level
Date: Thu, 4 Oct 2012 14:54:49 +0200 [thread overview]
Message-ID: <20121004125449.GQ26479@soda.linbit> (raw)
In-Reply-To: <60051.ac1412ad.1349200050.nsm@goliat6.ugr.es>
On Tue, Oct 02, 2012 at 07:47:30PM +0200, raulhp@ugr.es wrote:
> Hello,
>
> I have seen in the Roadmap in www.drbd.org, that DRBD version 9 will
> include support for "More than two nodes in one level (ie without stacking
> device)." Is an implementation is similiar to "Three-way replication" of
> version 8.4?
The goal is obviously to *avoid* the stacking,
and still be able to support several peers "natively".
> Where I can see more information including the implementation of more than
> two nodes in one level.
We do not have it publicly available yet,
as it is not yet ready for general consumption.
Once we have a "beta", we'll announce it.
Don't ask for ETAs ;-)
Any specific reason you ask,
what is it you are trying to do?
Cheers,
Lars
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
prev parent reply other threads:[~2012-10-04 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 17:47 [Drbd-dev] More than two nodes in one level raulhp
2012-10-04 12:54 ` Lars Ellenberg [this message]
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=20121004125449.GQ26479@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.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