As part of the move from per-row to per-rack redundancy model hosts in codfw rows A-D need to be configured / moved to new per-rack vlans/subnets. This work can be tackled once we have completed the physical move of all hosts in those rows from old 'asw' switch devices to new 'lsw' ones.
In discussion on irc we touched on some of the challenges for these hosts, which as I understand may use IP addresses as identifiers. We also need to consider how clusters function with hosts on different subnets that were previous layer-2 adjacent.
Having tested the migration process on ms-be2075, we know that it works thus:
- Drain node
- Remove node from rings
- Reimage node (with --move-vlan)
- Make sure the swift ring manager knows about the relevant per-rack subnet
- Add node back to rings
Newer nodes automatically get added to new-style subnets (ms-be2081 and later); so start with the newest node with old-style networking and move backwards, meaning that the oldest nodes get done last (and might have been aged out in the mean time).
- ms-be2080
- ms-be2079
- ms-be2078
- ms-be2077 (draining)
- ms-be2076 (draining)
- ms-be2075
- ms-be2074 (draining)
- ms-be2073
- ms-be2072
- ms-be2071
- ms-be2070
Below this point, nodes are using old-style storage, so we might want to fix that at the same time
- ms-be2069
- ms-be2068
- ms-be2067
- ms-be2066
- ms-be2065
- ms-be2064
- ms-be2063
- ms-be2062
- ms-be2061
- ms-be2060
- ms-be2059
- ms-be2058
- ms-be2057