I've added the network containers as discussed on the previous task in Netbox now:

https://netbox.wikimedia.org/ipam/prefixes/?within_include=2a02%3Aec80%3Aa100%3A%3A%2F40

@arturo /64s for VM usage I guess can be allocated from 2a02:ec80:a100::/56. We still need to decide how to set the routing (and firealling on cloudgw) up, and make the neccecary adjustments on our edge (RIR DB entries, RPKI objects and route policies) to make it usable on the internet. But you can probably get going with seeing how Neutron can assign some of that to VMs and get it to the point of pinging between two VMs etc.

In T374712#10163608, @cmooney wrote:

@arturo /64s for VM usage I guess can be allocated from 2a02:ec80:a100::/56. We still need to decide how to set the routing (and firealling on cloudgw) up, and make the neccecary adjustments on our edge (RIR DB entries, RPKI objects and route policies) to make it usable on the internet. But you can probably get going with seeing how Neutron can assign some of that to VMs and get it to the point of pinging between two VMs etc.

I'm tracking this at T375847: openstack: initial IPv6 support in neutron