19:00:10 <clarkb> #startmeeting infra
19:00:10 <opendevmeet> Meeting started Tue Feb 27 19:00:10 2024 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:10 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:10 <opendevmeet> The meeting name has been set to 'infra'
19:00:16 <clarkb> #link https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/6INGNPH2APYO7GUZ2HFJZPTLQTGITTS7/ Our Agenda
19:00:39 <clarkb> #topic Announcements
19:00:47 <clarkb> I had none that aren't otherwise covered in the normal agenda
19:01:05 <clarkb> May as well dive right in
19:01:07 <clarkb> #topic Service Coordinator Election Results
19:01:12 <corvus> announcement: there are no announcements
19:01:20 <clarkb> I was the only nominee so I guess I am "it" by default again
19:01:29 <frickler> \o/
19:01:35 <clarkb> #link https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/6C4TIQVP2R6AXLN3AKMSOR66DKURRSNC/
19:01:36 <corvus> clarkb: congrats!
19:01:43 <corvus> to you and to us!  :)
19:02:02 <clarkb> I don't have anyting to toast with at my desk but I wish I did :)
19:02:34 <fungi> thank you for your (continued) service
19:02:58 <clarkb> #topic Server Upgrades
19:03:06 <clarkb> #link https://review.opendev.org/c/opendev/system-config/+/905510 Upgrading meetpad service to jammy
19:03:46 <clarkb> tonyb: not sure if you're awake but I remain happy to help with this if I can be of assistance. Maybe we should go ahead and approve some of these test specific changes?
19:04:32 <clarkb> Let us know if we can help.
19:04:37 <clarkb> Any other server upgrade business?
19:05:56 <clarkb> #topic MariaDB Upgrades
19:06:18 <clarkb> as mentioned previously we're going to try to rely on the MARIADB_AUTO_UPGRADE flag
19:06:25 <clarkb> Paste, Etherpad, Gitea, Gerrit, Refstack, and Mailman could use upgrades. Starting with Paste due to its simplicity.
19:06:30 <clarkb> #link https://review.opendev.org/c/opendev/system-config/+/909471 Upgrade paste.o.o mariadb to 10.11
19:06:44 <clarkb> at this point I've got reviews needed and sentiment seems to be just go for it
19:06:57 <corvus> ++
19:07:18 <tonyb> ++
19:07:25 <clarkb> I'll try to do that tomorrow morning then as I should have few distractions at that point in time and can watch it
19:07:47 <clarkb> and if that goes well we can write changes for the other services and do them one by one
19:07:57 <fungi> sounds good
19:08:15 <clarkb> #topic AFS Mirror cleanups
19:08:43 <clarkb> OpenSUSE Leap has been (mostly) removed. There are some mirroring script bits that are sticking around until centos 7 is removed
19:08:59 <clarkb> The removal of Debian Buster is in progress now. You can use topic:drop-buster to find changes related to that
19:09:14 <clarkb> we're currently stuck on the removal of wheel cache build jobs for buster on the openstack/requirements repo
19:09:42 <clarkb> tonyb: do you think you can quickly review those changes and then I can followup with similar changes to remove centos 7 and xenial? Or would you prefer I update the existing changes to remove all three from requirements at the same time?
19:10:26 <frickler> if not, I can just approve as is tomorrow I guess
19:10:34 <tonyb> yup I can do that
19:10:46 <clarkb> I think the unmaintained/yoga branch might be weird too, but so far testing seems happy on all the branches just need reviews
19:10:48 <clarkb> tonyb: thanks!
19:11:09 <clarkb> once that is done we'll be able to drop the nodeset and then we can do nodepool and mirror cleanup last
19:11:27 <clarkb> the depends on metadata should capture all of that in the current changes
19:11:59 <clarkb> once buster is gone I'll keep chipping away at this with centos 7 changes then after that xenial
19:12:12 <tonyb> sounds good.
19:12:19 <clarkb> #topic OpenDev email hosting
19:12:34 <clarkb> Have we had any time to form opinions on this?
19:12:56 <clarkb> I think for myself if I were tasked with setting it up I'd look for hosted mail beacuse I've done that before but I've never self hosted
19:13:07 <clarkb> but I'm happy to learn if others are interested in self hosting
19:14:20 <fungi> i'm on the fence as to whether we host it ourselves. i don't mind being a mailserver admin (on top of already doing it for lists01), but i also see the argument for not unnecessarily burdening ourselves with more work
19:15:12 * frickler is also undecided. less work vs. security vs. more control. not sure which way to prefer
19:15:37 <tonyb> yup thats where I'm at too
19:15:51 <fungi> it's not urgent, we can mull it over for longer, i expect?
19:15:56 <clarkb> ok, I don't think we are in a hurry to solve this so we can continue to sleep on it
19:15:58 <clarkb> yup exactly
19:16:03 <tonyb> okay
19:16:23 <clarkb> I think if someone was ready to address this right now we'd make a quicker decision but I get the sense we all have plenty of other stuff going on already
19:17:07 <clarkb> I'll continue to take temperature on this unless I get told we should drop it from the regular meeting agenda
19:17:20 <clarkb> #topic Gitea 1.21.7 Upgrade
19:17:32 <clarkb> we are running 1.21.5 and there have been two bugfix releases in the last few days
19:17:37 <clarkb> #link https://review.opendev.org/c/opendev/system-config/+/909941
19:18:11 <clarkb> There were no template updates that I saw and I cross checked the JWT secret config modifications that were made and I'm 99% certain they were done in a backward compatbile way and we don't have to change anything on our end
19:18:23 <clarkb> all that to say I think we're ready once reviewers are happy. Maybe we can get that in today?
19:19:10 <clarkb> I can be around to monitor if people are happy with the change
19:19:27 <clarkb> #topic git-review vendoring the commit message hook
19:19:32 <clarkb> #link https://review.opendev.org/c/opendev/git-review/+/910275
19:19:46 <clarkb> This is an idea that has been kicked around for some time. fungi finally got around to implementing it
19:19:53 <fungi> pretty straightforward, hopefully
19:19:55 <clarkb> I need to review the change myself.
19:19:58 <fungi> not much to say about it
19:20:39 <fungi> though in implementing it i did spot a design issue with file permissions on the hook script, which resulted in a separate change to address
19:20:41 <corvus> sounds good to me; i was just wondering if there's any extra context i was missing (like some urgent new issue); but sounds like it's just "good idea; long time coming"
19:20:44 <clarkb> I think one important note is that while the hook script has had minor changes over time the format of the change id has not
19:20:53 <clarkb> so in theory a hook script from 2013 would work today and vice versa
19:21:22 <clarkb> corvus: ya I think there are a handful of good reasons to do it and the count got high enough to actually write the change
19:21:40 <fungi> yeah, my only real concern is if gerrit makes a change in the future which requires updates to that hook
19:22:07 <fungi> and for sites which could conceivably be depending on users getting a modified version of the hook specific to their needs
19:22:38 <fungi> but the change does provide a non-default escape hatch for those situations
19:24:12 <clarkb> ++ I'll review later today
19:24:23 <clarkb> #topic Project Renames
19:24:26 * tonyb too
19:24:32 <clarkb> We have a request for a project rename
19:24:54 <clarkb> (un)fortunately we're quite near the end of openstack's release process and historically we've avoided doing renames during this time
19:25:00 <clarkb> #link https://releases.openstack.org/caracal/schedule.html
19:25:22 <clarkb> I think this is fine as it gives us time to collect any other renames that may need to happen and do them together as well as improve the rename process
19:25:37 <clarkb> in particular i think we should consider updating the playbook to move aside the gerrit replication waiting queue dir
19:25:55 <frickler> what is the actual rename?
19:26:07 <clarkb> frickler: vexxhost/ansible-role-frrouting > openstack/ansible-role-frrouting
19:26:25 <clarkb> starlingx has brought up the idea of renaming some things as well but they haven't actually requested we do that
19:26:39 <clarkb> we can check with them to see if they are still interested and bundle everyting together
19:27:01 <tonyb> what downtime is there for renames?
19:27:03 <frickler> so that would also require a matching governance change? means we couldn't/shouldn't do it right away even if we wanted to?
19:27:21 <clarkb> frickler: correct, though I think that also exists and mnaser is happy for it to move out of vexxhost/
19:27:43 <clarkb> tonyb: renaming is actually an unsupported task in gerrit. To do the renames we shutdown gerrit, move things on disk, then start gerrit and reindex
19:28:10 <clarkb> tonyb: then we also have to rewrite things in zuul etc to match but that can be done in the runnign system typically
19:28:47 <fungi> also gitea api calls and storyboard database edits if they use sb
19:28:49 <tonyb> okay.  that's what I thought.  so the impact is wide but short (hopefully)
19:28:59 <frickler> clarkb: yeah, but similar to what we discussed in #opendev earlier, I'd like to see positive TC feedback before proceeding
19:29:09 <clarkb> frickler: sure
19:29:13 <fungi> tonyb: yeah, we scripted the entire thing in ansible, so it's about as fast as a gerrit restart
19:29:20 <clarkb> looking at a calendar I think we can pencil in April 12 for a rename
19:29:25 <fungi> minus the lingering impact of the online reindex for the affected repo(s)
19:29:34 <tonyb> okay. thanks
19:29:35 <clarkb> that gives us a target and a deadlien for getting paperwork in order
19:29:45 <corvus> the zuul schema has changed since our last renames; possibly in a way that may necessitate an update to the scripts
19:30:00 <fungi> corvus: thanks for calling that out, i had forgotten
19:30:11 <fungi> tonyb: ^ also we rename project keys in zuul
19:30:16 <clarkb> corvus: good to know. We already do a rename of the project keys using the cli tools
19:30:27 <clarkb> corvus: are you concerned about the historical job data in the sql database?
19:30:32 <corvus> we must do a db update right?
19:30:33 <frickler> 12.4. is the last day of the ptg, not sure I'd have energy left then
19:30:37 <corvus> yeah that's what i'm thinking of
19:30:41 <clarkb> corvus: I don't think we currently do a db update
19:30:46 <tonyb> okay.
19:30:50 <corvus> okay, so we just orphan it?  that's fine
19:30:58 <clarkb> corvus: which is probably fine you search for vexxhost/foo instead of openstack/foo to see that data
19:31:08 <clarkb> I think we can live with that since it is historically accurate and reduces our overhead
19:31:09 <corvus> yeah, wfm.  i just couldn't remember.
19:31:39 <clarkb> frickler: oh good callout
19:32:00 <clarkb> April 19 then? Any conflicts there?
19:32:02 <fungi> yes, let's not plan anything over top the ptg. i'll be busy enough ;)
19:32:35 <fungi> 2024-04-19 wfm
19:33:08 <tonyb> sounds good.
19:33:19 <frickler> +1
19:33:27 <clarkb> ok I can pencil thati nto the wiki agenda and I'll ping ildikov to see if starlingx should look at hte opportunity too
19:33:41 <clarkb> #topic Open Discussion
19:34:21 <clarkb> I noticed this morning (after I sent the agenda last night) that I've been asked to schedule PTG time for opendev because I signed us up. I'm thinking that it may be best to wait until most other projects have scheduled their times so that we can slip a few hours in during times that are less problematic?
19:34:47 <clarkb> but also with the expectations that yall may be busy with other PTG stuff and I'll be doing more office hours like content on my own
19:35:28 <tonyb> obviously I can handle office hours in the apac timeblock
19:35:33 <clarkb> any concerns with that approach? Also happy for people to propose times that work well for them
19:37:07 <clarkb> Great I'll proceed with this plan of action then
19:37:16 <frickler> having something in the APAC/EU block might be nice. because we could also use more people from that timezones
19:38:02 <clarkb> frickler: is that the 04-07 UTC or 13-16 UTC block?
19:38:11 <frickler> the former
19:38:32 <clarkb> ack. I think I can make some of those hours work for me too. I just have to stay awake long enough
19:38:40 <fungi> i could stay up late for something early in that timeframe
19:39:06 <fungi> 04-07 is basically 11pm-2am local for me
19:39:42 <clarkb> anything else?
19:40:19 <tonyb> I'm only one infra-root but I can for sure do that block
19:40:35 <clarkb> tonyb: ack
19:40:48 <clarkb> I'll give it a couple more minutes but I suspect we can end early
19:41:01 <clarkb> a reminder I'm happy to watch the gitea 1.21.7 upgrade today after lunch if others are willing t oreview it :)
19:42:02 <tonyb> I can do that.
19:42:34 <clarkb> sounds like that is everything. Thank you for your time today! See you here next week same time and location.
19:42:48 <clarkb> #endmeeting