Page MenuHomePhabricator

Migrate Cumin hosts to Buster
Open, MediumPublic


Tentatively scheduled for next quarter (as it's blocked on the decision whether to proceed with Mariadb 10.4).

High level steps involved:

  • Reimage cumin2001
  • Test workflows and adapt any potential tweaks on the OS/Python side
  • Tell everyone to move to cumin2001 and reimage cumin1001

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 13 2020, 8:56 AM
Volans added a subscriber: Volans.Feb 13 2020, 8:59 AM
jbond triaged this task as Medium priority.Feb 13 2020, 11:47 AM
jbond added a subscriber: jbond.

Cumin should for the most part be able to be upgraded to 10.4 with ease as it only holds the client, not the server, and that is why easier to upgrade (and it should be transparent).

The main issue on db/backups side is that snapshots are scheduled from cumin, and we should make sure those continue uninterrupted (mostly and the maria backup scripts).

I have checked the 10.4.12 mariadb client (and previos 10.4.11) on buster (on db1107) for the last few weeks without encountering any issues.

Noticed in T236576 that cumin is not packaged for buster. Is that going to change soon or should I make a new stretch instance?

Volans added a comment.Mar 6 2020, 9:44 AM

@Krenair sure, we'll need to make the buster package anyway for the prod migration. If you have a date in mind for your migration let me know so that I can adjust on when doing the buster package. Should be pretty trivial.

Thanks Volans. I'm planning to do it as soon as the package is available.