Update OpenStack to a version which supports IPv6 and enable it (cf. also T73218).
Description
Details
- Reference
- bz35947
Event Timeline
Persisting here some notes from @chasemp for future reference:
- This comes from around Kilo time when IPv6 was first being introduced and it was described as planning to be ready for general deploy in Newton. This is just a note I have from that time.
- BGP for Neutron routers and an upstream is seemingly only a serious option starting in Mitaka and I believe we talked about not wanting to plan on implementing both at once so probably that doubled down on the Newton narrative.
- At the time we started kicking this around it was unclear what the relationship was going to be between VXLAN (or other overlays) and IPv6. AFAICT overlays still require the host to use IPv4 even if the tenants are on IPv6, which is OK. It seems like ironically IPv6 within the Cloud is tested much better than IPv6 for control plane components.
- I have a note that indicates Router HA is not viable for IPv6 in Mitka with prefix designation https://docs.openstack.org/mitaka/networking-guide/config-ipv6.html. Whether this seriously matters probably depends on what the ideal model is here but in some dusty corner of my brain the idea that each tenant has globally unique IPv6 space via some overlay mechanism with HA software routers wouldn't work out it seems.
TLDR pre-Neutron things were very unclear what would even be possible
CloudVPS now uses a version of openstack that fully supports IPv6. Research/PoC work on IPv6 can be seen at T245495: CloudVPS: IPv6 in codfw1dev
Obviously, no one has come up with this idea since 2012, and it's still the same after 11 years, which is sad.
Change 975826 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/software/netbox-extras@master] Remove cloud hosts except clouddb from the "no IPv6 hostname" list
Change 975826 merged by jenkins-bot:
[operations/software/netbox-extras@master] Remove cloud hosts except clouddb from the "no IPv6 hostname" list
What is the status on this? The lack of IPv6 support of the webservice seems to be one of the reasons for slow connections from some internet providers. T362822
Just wanted to add this is still a source of trouble for us when trying to use cloud VPS to have test machines. We keep having to work around it a lot in different contexts just like many years ago.
It has been suggested by @cmooney that we introduce support for IPv6 while on the migration for T364725: Migrate Cloud VPS instances to VXLAN based networks, which I agree, and I'll try to do.
additional tracking of the project happening in https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/IPv6/initial_deploy
We are targeting to announce/start the user-facing migration on 2025-01-06, see also https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_VXLAN_IPv6_migration
Change #1112268 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/homer/public@master] Modifications to CR BGP policy for eqiad cloud-private IPv6 aggregate
Change #1112268 merged by jenkins-bot:
[operations/homer/public@master] Modifications to CR BGP policy for eqiad cloud-private IPv6 aggregate
Change #1112273 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/homer/public@master] Add WMCS cloud-private eqiad ranges to private6 prefix list
Change #1112273 merged by jenkins-bot:
[operations/homer/public@master] Add WMCS cloud-private eqiad ranges to private6 prefix list
Change #1117538 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/homer/public@master] Add semicolon to end of prefix in cloud6 prefix list
Change #1117538 merged by jenkins-bot:
[operations/homer/public@master] Add semicolon to end of prefix in cloud6 prefix list
Change #1138758 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/dns@master] Update GeoIP maps for new WMCS ranges
Change #1138758 merged by Majavah:
[operations/dns@master] Update GeoIP maps for new WMCS ranges