19:01:08 <clarkb> #startmeeting infra
19:01:08 <opendevmeet> Meeting started Tue Sep 28 19:01:08 2021 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:08 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:08 <opendevmeet> The meeting name has been set to 'infra'
19:01:16 <clarkb> #link http://lists.opendev.org/pipermail/service-discuss/2021-September/000286.html Our Agenda
19:01:22 <clarkb> #topic Announcements
19:02:00 <clarkb> The openstack xena release is starting to solidify and should be out the door next week. For this reason we should attempt to be slushy
19:02:13 <clarkb> I know we've got one zuul bug we want to restart for but otherwise we should probably err on the side of caution at this point
19:02:40 <clarkb> Also I'm going to be half here Friday and Monday as I attempt to have a mini weekend get away
19:02:51 <clarkb> I should be around early friday and late monday
19:03:04 <clarkb> #topic Actions from last meeting
19:03:12 <clarkb> #link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-09-21-19.01.txt minutes from last meeting
19:03:56 <clarkb> The one action was for all y'all to weigh in on the prometheus spec and a couple of you have. Looks like we're leaning towards node exporter but would prefer we avoid docker and use one of their shipped binaries
19:04:15 <clarkb> Thinking on it I like that approach a bit more if we host copies of the binary ourselves and verify shas and all that
19:04:32 <clarkb> I'll try to update the spec to propose that method in the near future
19:04:38 <clarkb> #topic Specs
19:04:58 <clarkb> I think I've covered the prometheus spec already. Do still leave your thoughts if you have them
19:05:06 <clarkb> #link https://review.opendev.org/c/opendev/infra-specs/+/804122 Prometheus Cacti replacement
19:05:16 <clarkb> The other spec we should be looking at is fungi's mailman 3 spec
19:05:20 <clarkb> #link https://review.opendev.org/810990 Mailman 3 spec
19:05:30 <clarkb> This is hot off the presses and I haven't had a look yet but I am excited.
19:05:53 <clarkb> Please take a look if you can and we can start refining this and preparing to make the mailing list server and services more sustainable going forward
19:06:56 <clarkb> #topic Topics
19:07:02 <clarkb> #topic Improving OpenDev's CD throughput
19:07:16 <fungi> yeah, i'm sure i've missed things, and i'm not the most up to speed on what we should be looking for in their current container designs
19:07:26 <clarkb> ianw mentioned he wouldn't make it today but says the stack of changes here are basically ready for review and left some notes. I'll post the links and the notes he gave us momentarily
19:07:36 <clarkb> #link https://review.opendev.org/c/opendev/system-config/+/807672
19:08:00 <clarkb> THis change should list dependencies for all jobs. And zuul doesn't trigger jobs for this change and he is wondering how to make this mergeable (maybe a noop change to a readme or something will do it)
19:08:08 <clarkb> #link https://review.opendev.org/c/opendev/base-jobs/+/807807
19:08:30 <clarkb> Currently every executor adds keys for bridge, then logs in and clones system-config before running playbooks. This change makes split jobs to do this. however, production remains the same as both are called.
19:08:42 <clarkb> #link https://review.opendev.org/c/opendev/system-config/+/807808
19:08:49 <clarkb> This is a follow-on that adds a base job to clone system-config, and stops the other production jobs re-cloning.
19:08:56 <clarkb> This job must run first, but then all other jobs can run in parallel, as they are all in the same buildset and using the same "view" of system-config for that particular run
19:09:24 <clarkb> From the notes I expect this will allow us to go step by step and carefully ensure things are as expected. I'll be attempting to review them soon and offer feedback. Much appreciated if others can do the same
19:09:28 <clarkb> And thank you ianw for digging into this
19:09:37 <clarkb> #topic Gerrit account cleanups
19:09:54 <clarkb> This has become my low priority thing with everything else going on the last week or two with zuul and gerrit and openstack
19:10:00 <clarkb> I'd like to get back to this but haven't had time.
19:10:07 <clarkb> Mostly just an apology here to say that :)
19:10:14 <clarkb> #topic OpenDev logo hosting
19:10:24 <clarkb> As of last night relative to my timezone I think this effort is basically done
19:10:41 <clarkb> gitea, paste, and gerrit are all using the opendev logo via self hosted locations
19:10:57 <clarkb> This means that we can now upgrade gitea to 1.15.x safely without worrying we'll break random theming in other places
19:11:06 <clarkb> #topic Gitea 1.15.3 upgrade
19:11:20 <clarkb> #link https://review.opendev.org/c/opendev/system-config/+/803231/
19:11:43 <clarkb> I think this change is as ready as it will be. I have a held instance for verification at https://198.72.124.104:3081/opendev/system-config
19:11:57 <clarkb> That said due to my previous comments about being slushy maybe we wait until next week after the openstack release is done?
19:12:28 <clarkb> Our testing is pretty good, but with all the random stuff that has happend with zuul, apache, devstack zuul configs and so on I'd like to not be worrying about more potentail problems for the release:)
19:12:37 <clarkb> Anyway please check that held instance and review the change
19:12:49 <clarkb> #topic Scheduling Gerrit project renames
19:13:02 <clarkb> Penciled in October 11-15. We should pick a specific day next week.
19:13:15 <clarkb> I don't expect the gitea upgrade to impact this as our testing tests renames in gitea now.
19:13:33 <clarkb> One thing we should look at is running the full project metadata update against renamed projects as a subsequent step to the renames
19:13:42 <clarkb> I think we can update the test jobs to do this as well
19:14:20 <clarkb> #topic Open Discussion
19:14:55 <clarkb> If there is anything else I'll give it a few minuets to capture those items. Otherwise as expected not much involvement today (and that is fine I'm recording this for people who watch logs)
19:15:36 <fungi> yeah i didn't have anything beyond what you've covered, thanks!
19:19:16 <clarkb> Sounds like that was it. Thank you for listening (or reading the logs)
19:19:19 <clarkb> #endmeeting