The network stacks in eqiad rows C and D are being upgraded to all 10G capable switches. Part of this migration will require all systems on the old switches to be moved to the new switch stack.
In previous migrations, we've stepped through the racks on by one, requiring each sub-team to be present for all affected hosts on the day of the migration. In an effort to better scale with the needs and schedules of multiple teams, we're planning to do this migration slightly different. Rather than a single date for each rack, we're providing a listing to each sub-team of all affected hosts, and that sub-team can then provide feedback with the priority and scheduling of the migration of hosts.
Scheduling Options and Considerations:
- Provide priority groups for the hosts below, and we can move group 1, then 2, etc...
- Provide specific dates and times for the migrations and we can coordinate the migration of the required host(s)
- A mix of the above for easier hosts could be in groups where high priority or critical hosts could have specific date/times set.
The checklist for each hosts migration steps are being developed and won't be pasted in to each task for each host in advance of the move (since if there is an adjustment it is a lot of tasks to update.)
The host list is also available on the Google Sheet listing of all affected hosts.
Host(s) List:
aux-k8s-worker1006 D4
aux-k8s-worker1007 D7
bast1003 D1
ganeti1024 C5
ganeti1027 C4
ganeti1028 C7
ganeti1033 D2
ganeti1034 D4
ganeti1037 C7
ganeti1038 D4
ganeti1045 C4
ganeti1046 C4
ganeti1047 C7
ganeti1048 C7
ganeti1049 D2
ganeti1050 D2
ganeti1051 D7
ganeti1052 D7
maps1009 C3 (decommissioned)
maps1010 D3 (decommissioned)
maps1013 C2
maps1014 D2
pki-root1001 D3
pki1002 C6
puppetserver1001 C5
krb1002 C3