Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com, Azeez Ahamed <azeez.ahamed@rediffmail.com>
Subject: Re: [Drbd-dev] DRBD contribution
Date: Tue, 22 Apr 2008 11:29:22 +0200	[thread overview]
Message-ID: <200804221129.22532.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20080422075743.16073.qmail@f5mail-236-217.rediffmail.com>

> I need some clarification on the activities you suggested me to
> develop.
>
> >   3 Change drbdadm so that it allows multiple "on" sections per
> >     resource. -- One has to specify the peer he means on the
> >     commandline when use drbdadm connect.
> >     [for DRBD-8.2]
>
>   Here you are looking for 1 to n node replication? When we use
> drbdadm connect command, it uses this command internally
>
> drbdsetup /dev/drbd0 net 10.1.40.33:1234 10.1.40.41:1234 C --set-defaults
> --create-device
>
>   Do i need to modify drbdsetup command to support multiple nodes?
> Please correct me if i am wrong.
>

Hi Azeez,

What I suggest is that the DRBD-driver and drbdsetup should stay as
they are. I suggest that you modify drbdadm so that one can specify
multiple on sections in a resource section.

As the driver and drbdsetup are two nodes only, one will then have
to select a peer node when calling drbdadm connect. So the command
line syntax of drbdadm will have to change as well. Maybe

drbdadm --to foo-node connect r0

Phil
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria        http://www.linbit.com :

      reply	other threads:[~2008-04-22  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22  7:57 [Drbd-dev] DRBD contribution Azeez Ahamed
2008-04-22  9:29 ` Philipp Reisner [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=200804221129.22532.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=azeez.ahamed@rediffmail.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