All in the title, mwmaint were the only servers including that profile, should it move to deployment servers?
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| O:kubernetes::deployment_server: mariadb client | operations/puppet | production | +1 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | dancy | T392693 Drop support for Debian Buster | |||
| Resolved | Clement_Goubert | T341560 Migrate mwmaint server functionality to mw-on-k8s | |||
| Resolved | Clement_Goubert | T397017 Turn down mwmaint production servers | |||
| Resolved | Clement_Goubert | T397847 Should deployment servers include mariadb::maintenance profile |
Event Timeline
Comment Actions
The puppet file for this profile is empty (reading modules/profile/manifests/mariadb/maintenance.pp) I think it's safe to drop it (but make sure to keep profile::mariadb::client installed on deployment servers). If one day we decide to add some stuff, it certainly won't be using puppet on mediawiki maint host. It made sense back then but not today.
Comment Actions
Change #1164139 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):
[operations/puppet@production] O:kubernetes::deployment_server: mariadb client
Comment Actions
Change #1164139 merged by Clément Goubert:
[operations/puppet@production] O:kubernetes::deployment_server: mariadb client