This task is to track the migration for instances from the cloud-instances2 VLAN based network to a VXLAN based approach. The current plan is to finish T326373: Migrate Cloud VPS to Neutron Open vSwitch agent first and then work on this.
Description
Details
Event Timeline
It has been mentioned by @cmooney that doing T37947: Enable IPv6 on CloudVPS while doing this VXLAN transition might be the perfect opportunity. I agree, and I will try to do it.
the script being developed in T377346: openstack: develop a script to migrate a VM instance from the old network setting (vlan) to the new (vxlan, IPv6) is proving to be challenging for a number of reasons.
I wonder if instead of force-migrating VMs to the new network, we could use a different strategy:
- use the IPv6 as incentive for users do to the migration
- make the new VXLAN/IPv6 network the default via horizon (but make them both available, which may be important, for Toolforge for example)
- announce the availability of the new network to the community
- for users to move to the new network, they need to re-create their VMs
per https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_VXLAN_IPv6_migration this migration is expected to start on 2025-01-06.
leaving ticket as stalled until then.
Change #1136980 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/homer/public@master] Cloud network: update policy to support /17 IPv4 aggregates
Change #1136980 merged by jenkins-bot:
[operations/homer/public@master] Cloud network: update policy to support /17 IPv4 aggregates
Change #1136991 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/homer/public@master] WMCS: fix typo in updated cloud-in policy
Change #1136991 merged by jenkins-bot:
[operations/homer/public@master] WMCS: fix typo in updated cloud-in policy
Change #1136993 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/homer/public@master] WMCS: fix typo in updated cloud-in policy #2
Change #1136993 merged by jenkins-bot:
[operations/homer/public@master] WMCS: fix typo in updated cloud-in policy #2
Change #1137002 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/homer/public@master] WMCS: Remove cloud-instances2-b specific ranges from BGP policy
Change #1137002 merged by jenkins-bot:
[operations/homer/public@master] WMCS: Remove cloud-instances2-b specific ranges from BGP policy
I think we can consider this ticket as resolved.
We won't be "migrating" VMs into the VXLAN setup, but rebuilding them into VXLAN over time.