All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Bartos <nick@pistoncloud.com>
To: Sage Weil <sage@newdream.net>
Cc: Greg Farnum <gregory.farnum@dreamhost.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] Statically binding ports for ceph-osd
Date: Tue, 10 Apr 2012 17:13:14 -0700	[thread overview]
Message-ID: <CAPud5_55jJ1tfxD_XVQGJE+5wZe2jhYnwmv3aqXOgT1tbCXOkw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1204101651270.18921@cobra.newdream.net>

Good enough for me, I'll just patch it for the short term.

Thanks!

On Tue, Apr 10, 2012 at 4:51 PM, Sage Weil <sage@newdream.net> wrote:
> On Tue, 10 Apr 2012, Nick Bartos wrote:
>> Awesome, thanks so much!  Can I assume this will make it into the next
>> ceph stable release?  I'll probably just backport it now before we
>> actually start using it, so I don't have to change the config later.
>
> v0.45 is out today/tomorrow, but it'll be in v0.46.
>
> sage
>
>
>>
>> On Tue, Apr 10, 2012 at 4:16 PM, 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!). :)
>> > Thanks for the report!
>> > -Greg
>> >
>> >
>> > On Tuesday, April 10, 2012 at 12:56 PM, Nick Bartos wrote:
>> >
>> >> After doing some more looking at the code, it appears that this option
>> >> is not supported. I created a small patch (attached) which adds the
>> >> functionality. Is there any way we could get this, or something like
>> >> this, applied upstream? I think this is important functionality for
>> >> firewalled environments, and seems like a simple fix since all the
>> >> other services (including ones for ceph-mon and ceph-mds) already
>> >> allow you to specify a static port.
>> >>
>> >>
>> >> On Mon, Apr 9, 2012 at 5:27 PM, Nick Bartos <nick@pistoncloud.com (mailto:nick@pistoncloud.com)> wrote:
>> >> > I'm trying to get ceph-osd's listening ports to be set statically for
>> >> > firewall reasons. I am able to get 2 of the 3 ports set statically,
>> >> > however the 3rd one is still getting set dynamically.
>> >> >
>> >> > I am using:
>> >> >
>> >> > [osd.48]
>> >> > host = 172.16.0.13
>> >> > cluster addr = 172.16.0.13:6944
>> >> > public addr = 172.16.0.13:6945
>> >> >
>> >> > The daemon will successfully bind to 6944 and 6945, but also binds to
>> >> > 6800. What additional option do I need? I started looking at the
>> >> > code and thought "hb addr = 172.16.0.13:6946" would do it, but
>> >> > specifying that option seems to have no effect (or at least does not
>> >> > achieve the desired result).
>> >>
>> >>
>> >>
>> >> Attachments:
>> >> - ceph-0.41-osd_hb_port.patch
>> >>
>> >
>> >
>> >
>> --
>> 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
>>
>>
--
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

  reply	other threads:[~2012-04-11  0:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  0:27 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 [this message]
2012-04-11 17:13           ` Greg Farnum
2012-04-12 18:42     ` Tommi Virtanen

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=CAPud5_55jJ1tfxD_XVQGJE+5wZe2jhYnwmv3aqXOgT1tbCXOkw@mail.gmail.com \
    --to=nick@pistoncloud.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gregory.farnum@dreamhost.com \
    --cc=sage@newdream.net \
    --subject='Re: [PATCH] Statically binding ports for ceph-osd' \
    /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

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.