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:
alert1002 C7
kafka-logging1002 C2
kafka-logging1003 D4
logging-hd1003 D7
logstash1034 C2
logstash1035 D4
mwlog1002 C6
prometheus1007 D7
prometheus1008 C7
titan1002 D2