[ 
https://issues.apache.org/jira/browse/HDDS-15780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siyao Meng updated HDDS-15780:
------------------------------
    Description: 
Publish operator guidance for the supported IPv4, dual-stack, and IPv6-only 
profiles after the functional and qualification tasks are complete.

The documentation must cover:
* Existing IPv4 defaults and explicit IPv6 listener configuration.
* Host-only, host-and-port, URI authority, and HTTP Host-header formats.
* The distinction between bind and advertised addresses.
* Wildcard listener use and rejection of wildcard, link-local, or scoped 
advertised addresses.
* Operating-system IPV6_V6ONLY behavior and why binding to :: does not always 
provide IPv4 reachability.
* Stable DNS, forward and reverse DNS, Kerberos principal selection, and TLS 
DNS or IP subject alternative names.
* The ofs bracketed-literal form and the o3fs requirement to use an OM service 
ID or DNS name.
* S3 path-style access through a literal and virtual-host-style access through 
DNS with an AAAA record.
* The supported non-rolling software upgrade followed by IPv4 to dual-stack to 
IPv6-only migration.
* SCM and OM Ratis migration with stable DNS or stored IP literals, including 
rollback requirements.
* Datanode UUID retention, pipeline replacement, bounded migration batches, and 
hdds.datanode.use.datanode.hostname.
* The minimum supported Hadoop and Ratis versions and any remaining limitations.

Depends on the functional, migration, dependency-release, and qualification 
tasks under HDDS-15763.

Parent epic: HDDS-15763.

  was:
No IPv6 deployment documentation exists. Once the code items land, add operator 
guidance covering dual-stack and IPv6-only setups: JVM stack settings, bind 
addresses, address-format expectations for OzoneFS/S3 endpoints, and 
secure-mode certificate implications. Remove or update the stale "we do not 
support IPv6" note in ozone-env.sh.

Depends on the functional items in this epic.

Parent epic: HDDS-15763.


> Document IPv6 (dual-stack and IPv6-only) deployment for Ozone
> -------------------------------------------------------------
>
>                 Key: HDDS-15780
>                 URL: https://issues.apache.org/jira/browse/HDDS-15780
>             Project: Apache Ozone
>          Issue Type: Task
>            Reporter: Siyao Meng
>            Priority: Major
>
> Publish operator guidance for the supported IPv4, dual-stack, and IPv6-only 
> profiles after the functional and qualification tasks are complete.
> The documentation must cover:
> * Existing IPv4 defaults and explicit IPv6 listener configuration.
> * Host-only, host-and-port, URI authority, and HTTP Host-header formats.
> * The distinction between bind and advertised addresses.
> * Wildcard listener use and rejection of wildcard, link-local, or scoped 
> advertised addresses.
> * Operating-system IPV6_V6ONLY behavior and why binding to :: does not always 
> provide IPv4 reachability.
> * Stable DNS, forward and reverse DNS, Kerberos principal selection, and TLS 
> DNS or IP subject alternative names.
> * The ofs bracketed-literal form and the o3fs requirement to use an OM 
> service ID or DNS name.
> * S3 path-style access through a literal and virtual-host-style access 
> through DNS with an AAAA record.
> * The supported non-rolling software upgrade followed by IPv4 to dual-stack 
> to IPv6-only migration.
> * SCM and OM Ratis migration with stable DNS or stored IP literals, including 
> rollback requirements.
> * Datanode UUID retention, pipeline replacement, bounded migration batches, 
> and hdds.datanode.use.datanode.hostname.
> * The minimum supported Hadoop and Ratis versions and any remaining 
> limitations.
> Depends on the functional, migration, dependency-release, and qualification 
> tasks under HDDS-15763.
> 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]

Reply via email to