As described in the original description, we dont have full ipv6 support. Currently, we only have partial ipv6 support where we have control and dataplane deployed over ipv6 network, but the underlying networks are still ipv4.

This initiative is to consider if we should work on this tech depth or not. I.e. is there customer value to invest on updating the testing infrastructure to by fully ipv6. Hence mimicking a customer who has pure ipv6 deployment
------------------------- Original description-------------------------------------
Current OSP18.0 Ipv6 Deployment job[1][2] runs with Control Plane/Dataplane on Ipv6. But it currently configure Ipv4 subnets as public network[3] which is being used by tempest tests.

In order to get the Ipv4 Floating network to work it requires some changes in underlying networks, it's done in [4]

This Epic is specifically to explore Ipv6 setup which Customers usually runs with Ipv6(PM/Field/Support input required on the Cu Ipv6 scenarios) and have the coverage in our CI by having a Full ipv6 only job.

Also to see if we have any job for this scenario already running for previous OSP releases. What all tempest coverage could be added as seems many of the tests rely on Floating IPs.

 [1] https://issues.redhat.com/browse/OSPRH-7414

[2] https://sf.hosted.upshift.rdu2.redhat.com/zuul/t/tripleo-ci-internal/builds?job_name=uni04delta-rhel9-rhoso18.0-ipv6&project=tripleo-ci

[3] https://github.com/openstack-k8s-operators/ci-framework/blob/1772ae61044c07219157043143a0eef0a7492dfb/roles/os_net_setup/defaults/main.yml#L4-L17

[4] https://gitlab.cee.redhat.com/ci-framework/ci-framework-jobs/-/merge_requests/833