13:00:05 <bbezak> #startmeeting kolla
13:00:05 <opendevmeet> Meeting started Wed Jul 23 13:00:05 2025 UTC and is due to finish in 60 minutes.  The chair is bbezak. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:05 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:05 <opendevmeet> The meeting name has been set to 'kolla'
13:00:11 <bbezak> #topic rollcall
13:00:22 <amir58118-2> \o
13:01:47 <frickler> o/
13:02:36 <bbezak> #topic agenda
13:02:39 <bbezak_2> * Roll-call * Agenda * Announcements * Review action items from the last meeting * CI status * Release tasks * Regular stable releases (first meeting in a month) * Current cycle planning * Additional agenda (from whiteboard) * Open discussion
13:03:00 <bbezak> #topic CI status
13:03:46 <bbezak> Kolla CI was broken because of ansible-lint issue - I fixed it today by bumping the version and pinning ansible - https://review.opendev.org/c/openstack/kolla/+/955673
13:04:02 <bbezak> I'm not sure why epoxy version is not merging - https://zuul.opendev.org/t/openstack/status?change=955678
13:04:24 <bbezak> as gate jobs were a successful
13:04:51 <bbezak> frickler: do you happen to know why?
13:05:12 <bbezak> (btw I need to finish in ~30 minutes)
13:05:41 <frickler> bbezak: seems zuul is taking its time sometimes
13:06:03 <bbezak> ok, let's wait. thx
13:06:14 <bbezak> #topic Release tasks
13:06:41 <bbezak> yesterday I dug up that one -  https://review.opendev.org/c/openstack/kolla/+/949731
13:06:52 <bbezak> needed for epoxy
13:07:02 <bbezak> https://bugs.rockylinux.org/view.php?id=9406
13:07:42 <bbezak> I pinged NeilHanlon to get some help in Rocky Linux for that
13:08:58 <bbezak> we've recently merged rabbitmq prerequisites for queue manager migration - also needed for slurp epoxy upgrade
13:09:14 <opendevreview> Merged openstack/kolla-ansible stable/2025.1: Add network group to tls-backend  https://review.opendev.org/c/openstack/kolla-ansible/+/955570
13:09:18 <opendevreview> Merged openstack/kolla-ansible stable/2024.1: Add network group to tls-backend  https://review.opendev.org/c/openstack/kolla-ansible/+/955666
13:09:22 <opendevreview> Merged openstack/kolla stable/2025.1: CI: Bump ansible-lint to <26  https://review.opendev.org/c/openstack/kolla/+/955678
13:09:36 <bbezak> and zuul started to merge things
13:09:37 <bbezak> good :)
13:11:26 <bbezak> I'm worried that to have proper migration to queue manager in caracal we would need also https://review.opendev.org/c/openstack/requirements/+/953420
13:11:54 <darmach1> (Better late then never) o/
13:11:56 <bbezak> but we shall see - we're doing some internal testing of that - but we may backport that patch downstream
13:12:17 <bbezak> #topic Additional agenda (from whiteboard)
13:12:43 <bbezak> amir58118-2: those topics of yours are both regarding Swift? - https://etherpad.opendev.org/p/KollaWhiteBoard#L67
13:12:57 <amir58118-2> The term 'modernization' is frequently mentioned in Gerrit reviews for Kolla-Ansible roles. I was wondering if there is a formal roadmap or design document that outlines the goals and plans for this effort?
13:13:25 <amir58118-2> bbezak> yes
13:14:05 <amir58118-2> and i have another one, I have a question about the review process for my patch series to restore Swift support (topic: "dev-swift-modernization"). The kolla patch is passing its tests, but the corresponding kolla-ansible patch requires further work with the Swift team. Can the kolla patch be reviewed and merged separately, or do they need to be reviewed as a single unit?
13:14:06 <bbezak> I'm not sure if we have formal document for that I would need to double check - by modernization it means to this role be as other "modern" kolla ansible roles
13:14:20 <bbezak> as swift was done in previous model of roles from older kolla-ansible version
13:15:12 <bbezak> there are some docs in contributor's guide
13:15:46 <amir58118-2> bbezak> i read all of those, so thanks
13:16:57 <frickler> IMO it doesn't make sense to have a swift image without a matching role to deploy and test it
13:18:29 <amir58118-2> frickler>
13:18:29 <amir58118-2> Thanks, frickler. I agree they are a set. My question was just to clarify the review process, i.e., whether the kolla patch could be reviewed first while the kolla-ansible part is being finalized.
13:19:11 <bbezak> kolla-ansible can have depends-on for kolla patch and it would build image in that CI
13:19:41 <frickler> amir58118-2: well you asked about "reviewed and merged". so reviewed, sure, merged - rather not
13:20:17 <amir58118-2> bbezak> Got it. That's the process I'm following. Thanks for the guidance, bbezak.
13:20:56 <amir58118-2> frickler> Got it, it was my mistake
13:21:55 <bbezak> ok, let's continue to the other point as I need to finish quite soon
13:22:00 <bbezak> * Bridging the gap between community and contributing orgs fungi
13:22:09 <fungi> i'll try to be quick, but there's a lot we dug into... for some background on openstack-wide metrics analysis see ildikov's most recent ml post from a month ago:
13:22:14 <fungi> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/NTBNI7YIDCWBR6BTPEKVZIODWTVUIOXO/ BtG metrics analysis
13:22:23 <fungi> also could be worthwhile to revisit her previous post in that thread going over the contributor and maintainer survey results (and anyone who hasn't filled those out for epoxy, please see if you can find a few minutes to do that!)
13:23:01 <fungi> as a follow-up activity, we've started doing some team-specific analyses, focusing on teams that had multiple contributor and maintainer survey responses (already did nova, cinder, ironic and octavia in recent weeks, neutron coming up next)
13:23:14 <fungi> we're early in the process of analyzing these stats with a focus on improving the experience for maintainers and contributors, so for now this is probably a lot of stuff you already know, or at least confirming what you expected
13:23:26 <fungi> a big part of this is establishing a baseline so that we can better gauge whether future attempts at improving have any observable impact, but we aren't at the point where we have much in the way of guidance or recommendations yet
13:23:40 <fungi> we have plans to continue with this sort of surveying and metrics analysis over coming release cycles; as for the initial results...
13:23:52 <fungi> the contributor survey had 4 responses for kolla and all respondents had contributed for at one year and were contributors to at least one other open source project
13:24:10 <fungi> feedback varied widely (averages of 1.25-3.75 out of 5) with the highest score on "[contributor docs] It helped you to apply better practices throughout your contribution journey and achieve results faster"
13:24:24 <fungi> lowest was on "Changes you propose are reviewed in a timely manner" which has been pretty common across a lot of the teams for which we've been looking at survey responses
13:24:42 <fungi> an interesting note is that the respondent with the shortest time involved ranke
13:24:44 <fungi> d everything much higher than those who had been contributing for a while
13:24:59 <fungi> the top challenges reported were trouble with review attention and understanding the project's reviewing priorities
13:25:09 <fungi> the maintainer survey had only response so far with slightly lower scores (ranging 1-3) with only timely reviewing getting a 1 while everything else was 3 out of 5
13:25:29 <fungi> contributing challenge reported by that maintainer was similar to those from the contributor survey (review attention), but also noted conflicting feedback from other reviewers and scope creep within expectations
13:25:44 <fungi> top challenges with reviewing were a lack of familiarity with certain parts of the code base, and contributors not addressing review feedback or test failures in a timely manner
13:25:58 <fungi> additional feedback noted the stability of test jobs has been crumbling over time, with a lack of maintainer failiarity in the tests and a shortage of maintainers overall this poses a potential sustainability risk
13:26:22 <fungi> looking at metrics we gathered from gerrit for the past 5 development cycles, review response wasn't all that bad which i think indicates some selection bias, and that occasional bad experiences stick in the mind more than positive ones
13:26:46 <fungi> selection bias in the survey responses i mean
13:26:59 <fungi> changes seem to be merging more quickly in recent cycles, though we lack the insight to determine whether this is due to a reduction in complexity of the changes or some other influence
13:27:15 <fungi> metrics also indicated a steady shrinkage of reviewers, which supports survey responses on the subject
13:27:34 <fungi> key takeaways were that sometimes lack of review attention is causing frustration for contributors so better communicating the project's review priorities to them might help assauge that
13:27:42 <fungi> and the project could use some help or prioritization on fixing up and maybe simplifying its test jobs
13:27:57 <fungi> there was also feedback that the project-specific contributor documentation was overly long and hard for newcomers to digest, so finding ways to pare that down might help too
13:28:05 <fungi> sorry, i know that's a pretty big info dump (i tried to pare it down as much as possible), and i'm happy to answer questions or take feedback either here in the meeting or any time after
13:28:18 <frickler> "more reviewer + maintainer capacity needed" is a well known issue I'd say
13:28:32 <fungi> yes, not surprising, as i noted
13:28:34 <bbezak> there is a lot to unpack here indeed - but that is very useful information - that we need to look into. surely lack of reviewers/maintainers is a kolla issue
13:28:35 <frickler> "too much documentation" is new to me, and I'm not sure I can follow that
13:29:24 <fungi> i don't know that it was all documentation, and survey responses indicated folks are referring to the contributor docs fairly often, there was just one response indicating that they were long and maybe too verbose
13:29:43 <fungi> obviously getting more survey responses would help paint a clearer picture
13:30:35 <bbezak> looks to me as something that we should have either dedicated meeting about - and/or topic(day) on PTG
13:31:00 <bbezak> thank you fungi for that update
13:31:19 <fungi> and as i said, this is as much as anything just setting a baseline so we can see if there are changes (positive or negative) in the future
13:31:39 <bbezak> unfortunately I need to finish the meeting for today - let's try to follow up on that - surely after PTL will be back from vacation
13:31:45 <fungi> you're welcome. i didn't have anything else on this topic if there are no other questions or comments
13:31:51 <bbezak> thank you for joining!
13:32:09 <bbezak> we can of course continue this discussion later on on IRC
13:32:10 <bbezak> #endmeeting