[09:51:24] <gehel>	 Lunch
[12:04:17] <pfischer>	 lunch
[14:23:26] <pfischer>	 gehel: would you know who has +2 permission for MW config changes? https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/+/952346/
[14:25:51] <pfischer>	 Looks like some of the previous CRs got merged by their owner, but some got merged by TrainBranchBot
[14:27:26] <gehel>	 https://gerrit.wikimedia.org/r/admin/repos/operations/mediawiki-config,access
[14:28:02] <gehel>	 pfischer: you probably need to be added to https://gerrit.wikimedia.org/r/admin/groups/3fdcf8fd0d569e90a3e9b39788a29f2c50d33be9,members
[14:28:04] <ebernhardson>	 pfischer: mw-config needs to be merged during the daily deployment windows
[14:28:21] <gehel>	 yes, as ebernhardson says :) I'm too slow!
[14:29:01] <ebernhardson>	 i guess we call them backport windows (names are hard :P) https://wikitech.wikimedia.org/wiki/Backport_windows
[14:30:47] <pfischer>	 Okay, so I have to request membership for wmf-deployment first. And I also need production shell access.
[14:31:04] <ebernhardson>	 pfischer: well, normally you just put the patch on the list and someone else doe sthe merge/deploy
[14:31:30] <ebernhardson>	 pfischer: in the backport window sections here: https://wikitech.wikimedia.org/wiki/Deployments
[14:31:42] <ebernhardson>	 you mostly only need be available and in the #wikimedia-operations room
[14:33:55] <pfischer>	 Okay, so I’d schedule it for tomorrow: https://wikitech.wikimedia.org/wiki/Deployments#deploycal-item-20230830T0700
[14:36:20] <ebernhardson>	 yea, that should work.  jouncebot will ping you in the #wikimedia-operations room when it's time for deploy if you use the normal template of `{{ircnick|pfischer}} {{gerrit|12345}} Some reason`
[14:37:06] <ebernhardson>	 i guess we usually prefix [config] to mw-config patches in the deployment calendar too, either [config] or the release version of mediawiki patches are being deployed into like [wmf23]
[14:46:58] <pfischer>	 Alright, it’s scheduled, thank you! I’ll set my alarm clock so I won’t miss the window tomorrow: https://wikitech.wikimedia.org/wiki/Deployments#deploycal-item-20230830T0700
[17:34:09] <Trey314159>	 Reindexing slowdown stats are in, and they are suprisingly regular and linear. Apostrophe handling is surprisingly expensive at 5% increase in run time.. I guess scanning for so many characters is expensive. word_break_helper is 2%. CamelCase is 35%. Acronyms handing is 206%.. that one there, officer! I'll look at speeding up both CamelCase and acronyms next. (Thanks for help setting up my testing environment, ebernhardson!)
[17:47:08] <ebernhardson>	 inflatador: I think you all might have been waiting for reindexing to stop befoire doing some restarts, we decided to cancel the reindex for now and will start it over after making some adjustments
[17:47:19] <ebernhardson>	 Trey314159: at least we have a clear place to look :) 
[17:51:15] <Trey314159>	 indeed!
[18:09:58] <inflatador>	 <o/
[18:10:14] <inflatador>	 ebernhardson thanks for the update, we'll get started on the reboots soon then
[18:32:09] <gehel>	 ryankemper: we're in the SRE pairing session: https://meet.google.com/eki-rafx-cxi
[18:32:13] <ryankemper>	 gehel: 2' for me
[20:46:32] <inflatador>	 OK, got the docker stuff sorted
[20:46:51] <inflatador>	 ebernhardson ryankemper if y'all have time to review, here's the dev-images MR https://gitlab.wikimedia.org/repos/releng/dev-images/-/merge_requests/49/diffs
[21:30:13] <inflatador>	 .chat does ganeti support cloud-init?
[21:40:52] <inflatador>	 .chat2 does ganeti support cloud-init?
[21:40:57] <inflatador>	 oops, ignore
[21:41:21] <inflatador>	 (answer is ...sort of)