Siyao Meng created HDDS-16969:
---------------------------------

             Summary: Add an IPv6-only acceptance smoke test
                 Key: HDDS-16969
                 URL: https://issues.apache.org/jira/browse/HDDS-16969
             Project: Apache Ozone
          Issue Type: Sub-task
          Components: docker-compose, test
            Reporter: Siyao Meng


No test currently runs an Ozone cluster over IPv6 end to end. The individual 
IPv6 fixes under HDDS-15763 only have unit tests, so a regression in listener 
setup, peer addressing or a client path would not be caught.

Add a compose-based acceptance test that runs a non-secure HA cluster on an 
IPv6-only Docker network and reuses existing robot suites.

Requirements:
* Use a Docker network with IPv6 enabled and IPv4 disabled, so a test cannot 
silently fall back to IPv4.
* Set the bind-host properties to {{::}}. Keep the existing compose 
environments and their IPv4 defaults unchanged.
* Run SCM HA, OM HA, at least three datanodes, Recon and S3 Gateway.
* Reuse existing robot suites for: volume, bucket and key operations through 
the shell and {{ofs}}; S3 path-style requests; admin commands that contact SCM, 
OM and datanodes; an OM leader transfer.
* Cover both DNS names and one bracketed IPv6 literal for the OM and SCM 
addresses.
* Verify that the services listen on IPv6 and that the datanodes register with 
IPv6 addresses.
* If the environment cannot create an IPv6-only network, report the test as 
skipped, not passed.

Notes:
* GitHub-hosted runners have no outbound IPv6 route, but this test only needs 
traffic between containers on a local bridge. Confirm that it runs there.
* A secure variant (Kerberos with DNS names, including a delegation token round 
trip) is a separate subtask and depends on HDDS-16347.

Parent: HDDS-15779.



--
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