These hosts will replace dbproxy1020 and dbproxy1021
- dbproxy1028 to replace dbproxy1020
- dbproxy1029 to replace dbproxy1021
These hosts will replace dbproxy1020 and dbproxy1021
Change #1055428 had a related patch set uploaded (by Arnaudb; author: Arnaudb):
[operations/puppet@production] dbproxy: mirrors hieradata
Change #1055428 merged by Arnaudb:
[operations/puppet@production] dbproxy: mirrors hieradata
Change #1087369 had a related patch set uploaded (by Arnaudb; author: Arnaudb):
[operations/puppet@production] dbproxy: update grants with ip and fqdn
Change #1087374 had a related patch set uploaded (by Arnaudb; author: Arnaudb):
[operations/dns@master] dbproxy: switch CNAMEs
Seems that these hosts were "productionized" but silenced for 3 months as the grants were not added and were left in that state?. They just showed up in icinga with HAproxy being down for 70 days (I assume the downtime expired). In order not to play with grants in production one day before the holidays, I will silence them until we are back and fix them when we are back.
Change #1107883 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/puppet@production] dbproxy1028: Update hosts
Change #1107883 merged by Marostegui:
[operations/puppet@production] dbproxy1028: Update hosts
Change #1107884 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/puppet@production] production-m3.sql.erb: Replace dbproxy1020 with dbproxy1028
Change #1107884 merged by Marostegui:
[operations/puppet@production] production-m3.sql.erb: Replace dbproxy1020 with dbproxy1028
dbproxy1029 is up and running - will leave it a few days before doing the switchover.
Change #1107887 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/puppet@production] production-m5.sql.erb: Replace dbproxy1021 with dbproxy1029
Change #1107888 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/software@master] report_users.sh: Add dbproxy102[89]
Change #1107888 merged by jenkins-bot:
[operations/software@master] report_users.sh: Add dbproxy102[89]
Change #1107887 merged by Marostegui:
[operations/puppet@production] production-m5.sql.erb: Replace dbproxy1021 with dbproxy1029
Change #1108315 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/puppet@production] dbproxy1028: Enable notifications
Change #1108316 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/dns@master] wmnet: Switchover m3-master
Change #1108315 merged by Marostegui:
[operations/puppet@production] dbproxy1028: Enable notifications
Mentioned in SAL (#wikimedia-operations) [2025-01-06T07:13:22Z] <marostegui> dbmaint Switchover m3 (phabricator) eqiad master dbproxy1020 -> dbproxy1028 T368874
Change #1108316 merged by Marostegui:
[operations/dns@master] wmnet: Switchover m3-master
Change #1108539 had a related patch set uploaded (by Marostegui; author: Marostegui):
[operations/dns@master] wmnet: Switch m5-master proxy
Change #1108539 merged by Marostegui:
[operations/dns@master] wmnet: Switch m5-master proxy
Mentioned in SAL (#wikimedia-operations) [2025-01-07T05:40:41Z] <marostegui> Switchover m5 eqiad proxy dbmaint eqiad T368874
Drained the connections from dbproxy1021 and it is all now being sent through dbproxy1029
Change #1087374 abandoned by Marostegui:
[operations/dns@master] dbproxy: switch CNAMEs
Reason:
This is not needed anymore
Change #1087369 abandoned by Marostegui:
[operations/puppet@production] dbproxy: update grants with ip and fqdn
Reason:
This was done in a different patch