On 5/2/19 4:08 PM, Daniel Gryniewicz wrote:
> Based on past experience with this issue in other projects, I would
> propose this:
>
> 1. By default (rgw frontends=beast), we should bind to both IPv4 and
> IPv6, if available.
>
> 2. Just specifying port (rgw frontends=beast port=8000) should
Daniel Gryniewicz writes:
> After discussing with Casey, I'd like to propose some clarifications to
> this.
>
> First, we do not treat EAFNOSUPPORT as a non-fatal error. Any other
> error binding is fatal, but that one we warn and continue.
>
> Second, we treat "port=" as expanding to
After discussing with Casey, I'd like to propose some clarifications to
this.
First, we do not treat EAFNOSUPPORT as a non-fatal error. Any other
error binding is fatal, but that one we warn and continue.
Second, we treat "port=" as expanding to "endpoint=0.0.0.0:,
endpoint=[::]".
Then,
Based on past experience with this issue in other projects, I would
propose this:
1. By default (rgw frontends=beast), we should bind to both IPv4 and
IPv6, if available.
2. Just specifying port (rgw frontends=beast port=8000) should apply to
both IPv4 and IPv6, if available.
3. If the
Currently RGW's beast frontend supports ipv6 via the endpoint
configurable. The port option will bind to ipv4 _only_.
http://docs.ceph.com/docs/master/radosgw/frontends/#options
Since many Linux systems may default the sysconfig net.ipv6.bindv6only
flag to true, it usually means that
