This task will track the migration of the ps1 and ps2 to be replaced with new PDUs in rack A6-eqiad.
Each server & switch will need to have potential downtime scheduled, since this will be a live power change of the PDU towers.
These racks have a single tower for the old PDU (with and A and B side), with the new PDUs having independent A and B towers.
- - schedule downtime for the entire list of switches and servers.
- - Wire up one of the two towers, energize, and relocate power to it from existing/old pdu tower (now de-energized).
- - confirm entire list of switches, routers, and servers have had their power restored from the new pdu tower
- - Once new PDU tower is confirmed online, move on to next steps.
- - Wire up remaining tower, energize, and relocate power to it from existing/old pdu tower (now de-energized).
- - confirm entire list of switches, routers, and servers have had their power restored from the new pdu tower
- - confirm serial works to the new PDU (it does not as of 2019-10-22 @ 17:08 GMT)
- - setup PDU following directions on https://wikitech.wikimedia.org/wiki/Platform-specific_documentation/ServerTech#Initial_Setup
- - update PDU model in puppet per T233129.
List of routers, switches, and servers
device | role | SRE team coordination | notes |
asw2-a6-eqiad | asw | @ayounsi | |
pc1007 | parsercache | DBA | can be failed over easily @Marostegui to depool this host |
wtp1027 | parsoid | serviceops | fine to do at any time |
wtp1026 | parsoid | serviceops | fine to do at any time |
wtp1025 | parsoid | serviceops | fine to do at any time |
an-master1001 | Analytics | fine to do any time | |
dbproxy1013 | dbproxy | DBA | not active |
elastic1045 | cirrus-search | Discovery-Search | @Gehel good to go |
elastic1044 | cirrus-search | Discovery-Search | @Gehel good to go |
elastic1048 | cirrus-search | Discovery-Search | @Gehel good to go |
mc1023 | mc | serviceops @elukey | fine to do at any time outside of deployment windows |
mc1022 | mc | serviceops @elukey | fine to do at any time outside of deployment windows |
mc1021 | mc | serviceops @elukey | fine to do at any time outside of deployment windows |
mc1020 | mc | serviceops @elukey | fine to do at any time outside of deployment windows |
mc1019 | mc | serviceops @elukey | fine to do at any time outside of deployment windows |
aqs1007 | Analytics | fine to do any time | |
weblog1001 | fine to do any time but it may disrupt some webrequest monitoring that we rely on, Cc: @godog | ||
restbase1021 | restbase | @jijiki | ok with power loss |
labsdb1012 | labsdb | Analytics | Analytics to confirm if MySQL can be stopped |
db1066 | db | DBA | Host powered off, DO NOT POWER ON - pending on-site decommissioning steps T233071 |
db1116 | db | DBA | backup source, nothing to be done |
db1115 | db | DBA | tendril host, nothing to be done |
labmon1002 | labmon | cloud-services-team | can be done anytime |
druid1004 | Analytics | fine to do any time | |
wdqs1004 | wdqs | Discovery-Search | @Gehel good to go |
ores1001 | ores | @akosiaris | fine to do at any time |
restbase-dev1004 | can be done at any time | ||
cloudcontrol1003 | openstack control node | cloud-services-team | can be done at any time |
mw1312 | mw | serviceops | fine to do at any time outside of deployment windows |
mw1311 | mw | serviceops | fine to do at any time outside of deployment windows |
mw1310 | mw | serviceops | fine to do at any time outside of deployment windows |
mw1309 | mw | serviceops | fine to do at any time outside of deployment windows |
mw1308 | mw | serviceops | fine to do at any time outside of deployment windows |
mw1307 | mw | serviceops | fine to do at any time outside of deployment windows |
ganeti1006 | ganeti node | @akosiaris | will need to be emptied in advance |
db1096 | db | DBA | @Marostegui to depool this host |