All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommi Virtanen <tommi.virtanen@dreamhost.com>
To: Greg Farnum <gregory.farnum@dreamhost.com>
Cc: Nick Bartos <nick@pistoncloud.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] Statically binding ports for ceph-osd
Date: Thu, 12 Apr 2012 11:42:51 -0700	[thread overview]
Message-ID: <CAORUGqB-onNKsFt7-ra9u4LmwEFXpZRdARv3-axaW=ZeKooVDQ@mail.gmail.com> (raw)
In-Reply-To: <C1A5CCB0C744475E8F129F38DAE60867@dreamhost.com>

On Tue, Apr 10, 2012 at 16:16, Greg Farnum <gregory.farnum@dreamhost.com> wrote:
> Yep, you're absolutely correct. Might as well let users specify the whole address rather than just the port, though — since your patch won't apply to current upstream due to some heartbeating changes I whipped up another one which adds the "osd heartbeat addr" option. It's pushed it to master in commit 6fbac10dc68e67d1c700421f311cf5e26991d39c, but you'll want to backport (easy) or carry your change until you upgrade (and remember to change the config!). :)

We're trying to push the "public addr" and "cluster addr" to have a
"public network" and "cluster network" alternatives that don't require
per-node IP address changes.. Adding more "addr" variants without
"network" ones is probably not the most awesome idea.

Now, because this is about port allocation, it runs into problems
trying to run multiple OSDs per machine without per-osd [osd.42]
sections, so I guess that's not as relevant here. I don't have a good
suggestion as to what to do for port allocation, apart from ensuring
that the port range being used is configurable (or even easily
discoverable).
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2012-04-12 18:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  0:27 Statically binding ports for ceph-osd Nick Bartos
2012-04-10 19:56 ` [PATCH] " Nick Bartos
2012-04-10 23:16   ` Greg Farnum
2012-04-10 23:45     ` Nick Bartos
2012-04-10 23:51       ` Greg Farnum
2012-04-10 23:51       ` Sage Weil
2012-04-11  0:13         ` Nick Bartos
2012-04-11 17:13           ` Greg Farnum
2012-04-12 18:42     ` Tommi Virtanen [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='CAORUGqB-onNKsFt7-ra9u4LmwEFXpZRdARv3-axaW=ZeKooVDQ@mail.gmail.com' \
    --to=tommi.virtanen@dreamhost.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gregory.farnum@dreamhost.com \
    --cc=nick@pistoncloud.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.