[
https://issues.apache.org/jira/browse/HDDS-15778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-15778:
------------------------------
Description:
Existing IPv4 listener defaults must remain unchanged. Ozone must allow
operators to opt into IPv6 listeners without treating a successful IPv6 bind as
proof of IPv4 reachability.
Requirements:
* Preserve the existing IPv4 defaults, including 0.0.0.0.
* Accept DNS names, IPv4 literals, IPv6 literals, and :: in the applicable
bind-host settings.
* Cover SCM, OM, datanode, Recon, S3 Gateway, HTTPFS Gateway, HTTP/HTTPS, gRPC,
and Ratis listeners.
* Construct listeners from separate host and port values.
* Keep bind addresses separate from advertised peer and client addresses.
* Reject wildcard, link-local, and scoped IPv6 addresses in advertised-endpoint
settings.
* Reject invalid advertised addresses before startup, registration, or
publication.
* Verify the address families accepted by :: on each supported operating
system; do not assume dual-stack behavior.
* Add component tests for listener construction and advertised-address
validation.
Operator guidance is tracked by HDDS-15780.
Parent epic: HDDS-15763.
was:
All service bind defaults are the IPv4 wildcard 0.0.0.0, which does not bind on
IPv6-only hosts:
- HddsConfigKeys.HDDS_DATANODE_CLIENT_BIND_HOST_DEFAULT
(HddsConfigKeys.java:373)
- ScmConfigKeys client/block-client/datanode/scm bind defaults
(ScmConfigKeys.java:179,187,202,218)
- OMConfigKeys.OZONE_OM_BIND_HOST_DEFAULT (OMConfigKeys.java:76)
- S3GatewayConfigKeys.OZONE_S3G_HTTP_BIND_HOST_DEFAULT
(S3GatewayConfigKeys.java:52)
- ozone-default.xml RPC address defaults such as 0.0.0.0:9862.
Proposed: decide the dual-stack vs IPv6-only binding behavior (for example
supporting :: wildcard), document operator guidance, and update
ozone-default.xml accordingly.
Parent epic: HDDS-15763.
Summary: Support explicit IPv6 listeners and advertised-address
validation (was: Review and support IPv6-capable bind-address defaults)
> Support explicit IPv6 listeners and advertised-address validation
> -----------------------------------------------------------------
>
> Key: HDDS-15778
> URL: https://issues.apache.org/jira/browse/HDDS-15778
> Project: Apache Ozone
> Issue Type: Task
> Reporter: Siyao Meng
> Priority: Major
>
> Existing IPv4 listener defaults must remain unchanged. Ozone must allow
> operators to opt into IPv6 listeners without treating a successful IPv6 bind
> as proof of IPv4 reachability.
> Requirements:
> * Preserve the existing IPv4 defaults, including 0.0.0.0.
> * Accept DNS names, IPv4 literals, IPv6 literals, and :: in the applicable
> bind-host settings.
> * Cover SCM, OM, datanode, Recon, S3 Gateway, HTTPFS Gateway, HTTP/HTTPS,
> gRPC, and Ratis listeners.
> * Construct listeners from separate host and port values.
> * Keep bind addresses separate from advertised peer and client addresses.
> * Reject wildcard, link-local, and scoped IPv6 addresses in
> advertised-endpoint settings.
> * Reject invalid advertised addresses before startup, registration, or
> publication.
> * Verify the address families accepted by :: on each supported operating
> system; do not assume dual-stack behavior.
> * Add component tests for listener construction and advertised-address
> validation.
> Operator guidance is tracked by HDDS-15780.
> Parent epic: HDDS-15763.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
