Change Details

Similar to {T334641} but with more servers. cloudsw2-d5-eqiad has been brought up as a stopgap solution as cloudsw1-d5 was becoming full due to servers using two uplinks. Thanks to {T319184} cloudsw1-d5-eqiad now have 8 free switch ports, 10 more once the last 10 cloudvirt servers will be migrated to 1 NIC. Those are the cloudsw2 servers: * cloudcephosd1023 (2 ports) - sync with @dcaro, we need to do T334641 first (or after) * cloudcephosd1024 (2 ports) - sync with @dcaro, we need to do T334641 first * cloudvirt1047 - ready * cloudcephosd1015 (2 ports) - sync with @dcaro, we need to do T334641 first * cloudcephmon1002 (2 ports) - ready * cloudvirtlocal1001 - ready As it's a total of 10 ports, we will first need T319184 to be completed first. Until then make sure no new servers go to cloudsw2. Moving them to cloudsw1-d5 will allow us to decom cloudsw2-d5 and thus cleanup the configuration, help to keep a stable infra, free up (U & cabling) space in the rack. As it's the same vlan on both switches there is no re-numbering needed, the process is straightforward (and they don't need to move physically): # Configure the new switch ports # Move the cables # Un-configure the old switch ports # Update the cables in Netbox They can also be done one at a time if needed.

Similar to {T334641} but with more servers. cloudsw2-d5-eqiad has been brought up as a stopgap solution as cloudsw1-d5 was becoming full due to servers using two uplinks. Thanks to {T319184} cloudsw1-d5-eqiad now have 8 free switch ports, 10 more once the last 10 cloudvirt servers will be migrated to 1 NIC. Those are the cloudsw2 servers: * ~~cloudcephosd1023 (2 ports) - sync with @dcaro, we need to do T334641 first (or after)~~ * cloudcephosd1024 (2 ports) - sync with @dcaro, we need to do T334641 first * cloudvirt1047 - ready * cloudcephosd1015 (2 ports) - sync with @dcaro, we need to do T334641 first * cloudcephmon1002 (2 ports) - ready * cloudvirtlocal1001 - ready As it's a total of 10 ports, we will first need T319184 to be completed first. Until then make sure no new servers go to cloudsw2. Moving them to cloudsw1-d5 will allow us to decom cloudsw2-d5 and thus cleanup the configuration, help to keep a stable infra, free up (U & cabling) space in the rack. As it's the same vlan on both switches there is no re-numbering needed, the process is straightforward (and they don't need to move physically): # Configure the new switch ports # Move the cables # Un-configure the old switch ports # Update the cables in Netbox They can also be done one at a time if needed.

Similar to {T334641} but with more servers. cloudsw2-d5-eqiad has been brought up as a stopgap solution as cloudsw1-d5 was becoming full due to servers using two uplinks. Thanks to {T319184} cloudsw1-d5-eqiad now have 8 free switch ports, 10 more once the last 10 cloudvirt servers will be migrated to 1 NIC. Those are the cloudsw2 servers: * ~~cloudcephosd1023 (2 ports) - sync with @dcaro, we need to do T334641 first (or after)~~ * cloudcephosd1024 (2 ports) - sync with @dcaro, we need to do T334641 first * cloudvirt1047 - ready * cloudcephosd1015 (2 ports) - sync with @dcaro, we need to do T334641 first * cloudcephmon1002 (2 ports) - ready * cloudvirtlocal1001 - ready As it's a total of 10 ports, we will first need T319184 to be completed first. Until then make sure no new servers go to cloudsw2. Moving them to cloudsw1-d5 will allow us to decom cloudsw2-d5 and thus cleanup the configuration, help to keep a stable infra, free up (U & cabling) space in the rack. As it's the same vlan on both switches there is no re-numbering needed, the process is straightforward (and they don't need to move physically): # Configure the new switch ports # Move the cables # Un-configure the old switch ports # Update the cables in Netbox They can also be done one at a time if needed.