Utilizing the nat64/dns64 disk image, create the libvirt networks and enable the routing to emulate external IPv6 connectivity from libvirt IPv6 network.
Proposed design:
╭──────────────╮ ╭─────│ IPv4 Network │─────╮ IPv4 Traffic ───── │ ╰──────────────╯ │ IPv6 Traffic ═════ │ │ │ │ NAT64-Appliance is ╭─────────────────╮ ╭────────────╮ default IPv6 router │ NAT64-Appliance │ │ Controller │ and external DNS ╰─────────────────╯ ╰────────────╯ server/forwarder for ║ ║ everything attached ╚═════════════╗ ╔═════════╝ to the IPv6 network. ║ ║ ╭───────────────╮ May need DNS server ╔══════│ IPv6-Networks │══════╗ on Controller with ║ ╰───────────────╯ ║ wildcard entries for ║ ║ RHOSO domains. ║ ║ ╭───────────╮ ╭────────────────────────────╮ │ CRC / OCP │ │ EDPM Compute/Networker etc │ ╰───────────╯ ╰────────────────────────────╯
The "Controller" is the "jump" host into the IPv6 only lab, this host must have ansible and inventory of the nodes inside the lab "bubble" - run cifmw playbooks to deploy RHOSO on the controller. Alternatively we could try to configure an IPv6 address on the hypervisor bridges, and add manage the routes etc on the hypervisor.