From: Ken Dreyer <kdreyer@redhat.com>
To: Sage Weil <sage@newdream.net>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: firewall questions
Date: Thu, 21 May 2015 09:36:17 -0600 [thread overview]
Message-ID: <555DFB71.6050602@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1505201551450.23818@cobra.newdream.net>
On 05/20/2015 04:53 PM, Sage Weil wrote:
>> 2. I talked recently with Sam about the possible ports an OSD could use,
>> and our conversation made me think that our firewall docs for OSDs and
>> MDSs might need to be updated: http://tracker.ceph.com/issues/11688
>>
>> Currently the docs say "calculate the number of OSDs or MDSs you're
>> running and that will tell you what ports to open". That makes it hard
>> to write a service definition for firewalld, since those are just a list
>> of static ports.
>
> Yeah, I'm afraid it should just be teh full range we allow... I think
> 6800-7100 by default?
src/common/config_opts.h from master says:
OPTION(ms_bind_port_min, OPT_INT, 6800)
OPTION(ms_bind_port_max, OPT_INT, 7300)
I think that would mean we'd want to open 6800-7300 by default?
And for this firewalld service name, I was thinking of naming this
6800-7300 rule "ceph", since it encompasses both the OSD and MDS
services. Does that name sound ok? (And I'd name the 6789 rule "ceph-mon".)
- Ken
next prev parent reply other threads:[~2015-05-21 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 20:07 firewall questions Ken Dreyer
2015-05-20 22:53 ` Sage Weil
2015-05-21 15:36 ` Ken Dreyer [this message]
2015-05-21 15:37 ` Sage Weil
2015-05-21 20:33 ` Ken Dreyer
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=555DFB71.6050602@redhat.com \
--to=kdreyer@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.