Update all memcached servers across both datacentres to Debian Trixie.
How?
We will reimage on of the hosts we are retiring from eqiad (mc1054) to trixie, add it to the pool for a while (2 days, maybe more), and if there is nothing odd, we can proceed with the upgrade.
eqiad
- mc1055.eqiad.wmnet
- mc1056.eqiad.wmnet
- mc1057.eqiad.wmnet
- mc1058.eqiad.wmnet
- mc1059.eqiad.wmnet
- mc1060.eqiad.wmnet
- mc1061.eqiad.wmnet
- mc1062.eqiad.wmnet
- mc1063.eqiad.wmnet
- mc1064.eqiad.wmnet
- mc1065.eqiad.wmnet
- mc1066.eqiad.wmnet
- mc1067.eqiad.wmnet
- mc1068.eqiad.wmnet
- mc1069.eqiad.wmnet
- mc1070.eqiad.wmnet
- mc1071.eqiad.wmnet
- mc1072.eqiad.wmnet
- mc-gp1004.eqiad.wmnet
- mc-gp1005.eqiad.wmnet need to be re-IPed T421711: ServiceOps: Re-IP eqiad private baremetal hosts to new per-rack vlans/subnets
- mc-gp1006.eqiad.wmnet need to be re-IPed T421711: ServiceOps: Re-IP eqiad private baremetal hosts to new per-rack vlans/subnets
- mc-wf1001.eqiad.wmnet
- mc-wf1002.eqiad.wmnet
codfw
- mc2038.codfw.wmnet
- mc2039.codfw.wmnet
- mc2040.codfw.wmnet
- mc2041.codfw.wmnet
- mc2042.codfw.wmnet
- mc2043.codfw.wmnet
- mc2044.codfw.wmnet
- mc2045.codfw.wmnet
- mc2046.codfw.wmnet
- mc2047.codfw.wmnet
- mc2048.codfw.wmnet
- mc2049.codfw.wmnet
- mc2050.codfw.wmnet
- mc2051.codfw.wmnet
- mc2052.codfw.wmnet
- mc2053.codfw.wmnet
- mc2054.codfw.wmnet
- mc2055.codfw.wmnet
- mc-gp2004.codfw.wmnet
- mc-gp2005.codfw.wmnet
- mc-gp2006.codfw.wmnet
- mc-wf2001.codfw.wmnet
- mc-wf2002.codfw.wmnet
Notes
- codfw can wait for Q2 when we will also refresh the memcached cluster
- @RLazarus we have two mc-wf servers per DC, what should we do in order to not disrupt the application using them?
- For mc-gp servers needing to be re-IPed, the process will be to
- Degrade the gutter pool to 1 server (ie remove the two hosts from profile::mediawiki::mcrouter_wancache::shards
- run puppet on deployment servers and re-deploy mw-mcrouter in both DCs
- Reimage/re-IP (--move-vlan)
- rinse