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 specifying a v6 endpoint will bind to both v4 and v6. But this also means that deployment systems must be aware of this while configuring depending on whether both v4 and v6 endpoints need to work or not. Specifying both a v4 and v6 endpoint or a port (v4) and endpoint with the same v6 port will currently lead to a failure as the system would've already bound the v6 port to both v4 and v6. This leaves us with a few options. 1. Keep the implicit behaviour as it is, document this, as systems are already aware of sysconfig flags and will expect that at a v6 endpoint will bind to both v4 and v6. 2. Be explicit with endpoints & configuration, Beast itself overrides the socket option to bind both v4 and v6, which means that v6 endpoint will bind to v6 *only* and binding to a v4 will need an explicit specification. (there is a pr in progress for this: https://github.com/ceph/ceph/pull/27270) Any more suggestions on how systems handle this are also welcome. -- Abhishek _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |