@jcrespo how do you want to approach the backup sources migration?
My plan is, once codfw is back as secondary, start the migration there.
We should probably get all the replicas migrated, and right before switching the master, migrate the backup sources.
Would you feel comfortable with that?

Obviously the current backup source for s6 is db2141 which also holds s1 too so...what would like to do there?

Your general plan seems good to me.

Regarding the shared instances we can do 2 things:

• Ignore the backup sources, because backups from 10.4 should be very quickly usable for 10.6
• Start moving instances around and upgrade the right ones (assuming there is an order of what will be upgraded next)

#2 is more time consuming, and may block you more, but #1 may be less ideal (I accept suggestions)

Mostly it will affect dbprov hosts, as they currently can only prepare snapshots with 1 version.

In an ideal world, we could install 10.6 and 10.4 packages on the same system, side by side.

for more context, there are 2 backup sources for enwiki in codfw:

• db2141:3311
• db2097:3311

In T334650#8778609, @jcrespo wrote:

Your general plan seems good to me.

Regarding the shared instances we can do 2 things:

• Ignore the backup sources, because backups from 10.4 should be very quickly usable for 10.6
• Start moving instances around and upgrade the right ones (assuming there is an order of what will be upgraded next)

#2 is more time consuming, and may block you more, but #1 may be less ideal (I accept suggestions)

Both plans are ok with. Whatever you feel more comfortable with I am happy to adapt to.

My suggestions if for you to do what you did here: announce your plans (and if possible, what the next section would be in advance), and do things at your own pace- if I see something that will cause me issues I will shout as early as possible 0:-)

Sounds good. So for now I am going to go only for codfw normal replicas (once codfw is back as secondary, so after the 26th April). I will ping you before doing the candidate master and of course the master switch.

Yes, but what is going to be the next section (even if it will take a lot of time?). This way, I can put it there together with s6 in the backup source.

I'd say s2 and x1.

In T334650#8779103, @Marostegui wrote:

I'd say s2 and x1.

Thank you, that helps me plan ahead of time!

Change 914717 had a related patch set uploaded (by Marostegui; author: Marostegui):

[operations/puppet@production] db2124: Migrate to 10.6

https://gerrit.wikimedia.org/r/914717

Change 914717 merged by Marostegui:

[operations/puppet@production] db2124: Migrate to 10.6

https://gerrit.wikimedia.org/r/914717

Change 918240 had a related patch set uploaded (by Marostegui; author: Marostegui):

[operations/puppet@production] db2151: Migrat to 10.6

https://gerrit.wikimedia.org/r/918240

Change 918240 merged by Marostegui:

[operations/puppet@production] db2151: Migrat to 10.6

https://gerrit.wikimedia.org/r/918240

Change 918355 had a related patch set uploaded (by Marostegui; author: Marostegui):

[operations/puppet@production] db2117: Migrate to 10.6

https://gerrit.wikimedia.org/r/918355

Mentioned in SAL (#wikimedia-operations) [2023-05-10T07:42:37Z] <marostegui@cumin1001> dbctl commit (dc=all): 'Depool db2117 T334650', diff saved to https://phabricator.wikimedia.org/P48080 and previous config saved to /var/cache/conftool/dbconfig/20230510-074237-root.json

Change 918355 merged by Marostegui:

[operations/puppet@production] db2117: Migrate to 10.6

https://gerrit.wikimedia.org/r/918355

Change 918363 had a related patch set uploaded (by Marostegui; author: Marostegui):

[operations/puppet@production] db2187: Migrate to 10.6

https://gerrit.wikimedia.org/r/918363

Change 918363 merged by Marostegui:

[operations/puppet@production] db2187: Migrate to 10.6

https://gerrit.wikimedia.org/r/918363

For now this looks like the tracking issue: https://jira.mariadb.org/browse/MDEV-30531