17:59:44 <knikolla> #startmeeting tc
17:59:44 <opendevmeet> Meeting started Tue May 30 17:59:44 2023 UTC and is due to finish in 60 minutes.  The chair is knikolla. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:59:44 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:59:44 <opendevmeet> The meeting name has been set to 'tc'
17:59:53 <knikolla> #topic Roll Call
17:59:57 <dansmith> o/
17:59:57 <noonedeadpunk> o/
17:59:58 <slaweq> o/
18:00:00 <knikolla> Hi all, welcome to the weekly meeting of the OpenStack Technical Committee
18:00:04 <knikolla> A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct
18:00:09 <knikolla> Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
18:00:12 <knikolla> o/
18:00:23 <gmann> o/
18:00:44 <noonedeadpunk> I'd say it's missing important point which is PTG timeslots for Vancouver?
18:00:59 <knikolla> Before we quickly move on to the agenda item's I'm going to capture some todo items under my name, to keep me accountable
18:01:08 <knikolla> noonedeadpunk: yep, that being one of those action items.
18:01:24 <knikolla> #action knikolla Book timeslots for PTG in Vancouver
18:01:28 <gmann> and also what we are going to discuss, some pre captured topics
18:01:36 <knikolla> #action knikolla Prepare PTG agenda for Vancouver
18:01:56 <knikolla> #action Finish TC Tracker 2023.2
18:02:45 <knikolla> I have blocked off time in my calendar for all of those topics this week
18:03:10 * rosmaita sneaks in
18:03:23 <knikolla> Sorry for the delay
18:03:48 <knikolla> We can circle back at the end of the meeting if there's further to discuss about that
18:03:53 <knikolla> #topic Follow up on past action items
18:03:58 <knikolla> There is 1 action item from the previous meeting
18:04:05 <knikolla> dansmith: backport memory reduction patch for devstack to yoga and look useful doing it
18:04:18 <dansmith> first part is done, haven't figured out how to do the second part yet
18:04:58 <knikolla> Depends on the audience, haha. You look pretty useful to us. I don't know if that applies to your supervisor too.
18:06:12 <knikolla> #topic Broken docs due to inconsistent release naming
18:06:19 <knikolla> There are no updates on this and I failed to capture the to do item that arose from the previous discussion
18:06:33 <knikolla> #action knikolla To fix link redirect to release from docs
18:07:29 <knikolla> #topic Gate health check
18:07:34 <knikolla> Any updates on the state of the gate?
18:07:36 <JayF> o/
18:08:01 <dansmith> still having guest kernel crashes on cirros 0.6.1 but they look different
18:08:09 <dansmith> still waiting for enough data to say if it's better or not
18:08:49 <dansmith> otherwise I don't know of any major gate issues myself, other than the combined effect of the usual bunch of small issues
18:09:03 <knikolla> Thanks dansmith, anything else on this or gate status in general?
18:09:04 <gmann> yeah, I have also not seen very visible difference with new cirros
18:09:34 <gmann> but overall there are less timeout because of multiple fixes happened in this cycle
18:09:52 <noonedeadpunk> Yeah, I would say that gates are really goodlately
18:09:57 <dansmith> maybe worth mentioning that I did backport the flag, but it has not yet merged: https://review.opendev.org/c/openstack/devstack/+/883970
18:10:03 <dansmith> but I just pinged some people to remind them
18:10:19 <noonedeadpunk> except nasty CentOS bumping libvirt version to 9.3...
18:10:29 <noonedeadpunk> But yeah, nothing from our side at least
18:11:58 <noonedeadpunk> haven't seen any timeouts last couple of weeks
18:12:07 <knikolla> dansmith: I +1ed that to look useful too
18:12:20 <dansmith> is that all it takes?
18:12:25 <fungi> also a reminder that opendev is working on dropping package mirrors for fedora (and possibly fedora images after that)
18:12:29 <dansmith> anyway, nothing else from me
18:12:40 <spotz> o/
18:13:10 <knikolla> fungi: are there actions to do on our part or things that we need to monitor?
18:13:26 <fungi> other than speak up if you're heavily reliant on fedora testing, no
18:13:51 <fungi> so far the arguments for keeping fedora around have been fairly minor
18:14:30 <fungi> and what we have in opendev is a couple releases behind and ~nobody noticed/cared
18:14:31 <noonedeadpunk> I think we're missing rocky mirrors as of today?
18:14:58 * noonedeadpunk thinks of utilizing freed space :D
18:15:00 <knikolla> roger
18:15:03 <fungi> yes, we've been discussing what would be needed to add rocky linux mirroring
18:15:17 <fungi> but also we're trying to free space for the upcoming debian release
18:15:55 <fungi> anyway, join the discussion in opendev if you're interested in those topics
18:16:01 <knikolla> anything else on gate?
18:16:13 <noonedeadpunk> We've switched most of testing from CentOS to Rocky nowadays, so we'd use these mirrors in OSA at very least...
18:17:22 <knikolla> that seems useful and as fungi mentioned, worth discussing further in the opendev channel
18:17:44 <noonedeadpunk> ++
18:17:58 <knikolla> #topic Keeping Python 3.8 support and clarifying Python version support
18:18:04 <knikolla> #link https://review.opendev.org/c/openstack/governance/+/882165?usp=search
18:18:08 <knikolla> #link https://review.opendev.org/c/openstack/governance/+/882154?usp=search
18:18:37 <gmann> thanks noonedeadpunk for updating those
18:18:40 <knikolla> Thanks noonedeadpunk for updating the proposals.
18:18:52 <dansmith> thanks noonedeadpunk for updating those
18:19:01 * dansmith jumps on the bandwagon
18:19:01 <noonedeadpunk> I've jsut noticed that commit msg for 882165 is wrong....
18:19:03 <knikolla> lol
18:19:17 <gmann> ah
18:19:23 <gmann> it still says library
18:19:35 <noonedeadpunk> I wonder if I should update it....
18:19:46 <noonedeadpunk> likely good to do...
18:19:50 <gmann> yeah, I think better to update to avoid confusion
18:19:54 <knikolla> I think it should be updated, yes.
18:20:00 <slaweq> ++
18:20:02 <dansmith> do it now and we can all re-vote real quick
18:20:05 <gmann> +1
18:20:43 <slaweq> I was just reading it now and confused by that commit message :)
18:20:48 <opendevreview> Dmitriy Rabotyagov proposed openstack/governance master: Add py38 as a PTI requirement for Python projects  https://review.opendev.org/c/openstack/governance/+/882165
18:20:50 <knikolla> ++
18:21:12 <noonedeadpunk> oh, wow, roll-call vote is not reseted on commit msg update o_O
18:21:30 <dansmith> well, good this time :)
18:21:47 <knikolla> Yay.
18:21:56 <gmann> humm but why
18:22:00 <gmann> this is not good right
18:22:07 <noonedeadpunk> yeah, but I wonder if we should have `changekind:NO_CODE_CHANGE`
18:22:19 <noonedeadpunk> for copying votes
18:22:52 <noonedeadpunk> it's not reflecting content.... but commit message could be completely changed and nobody will notice that
18:23:08 <knikolla> I think NO_CODE_CHANGE will still have this same behavior
18:23:10 <fungi> will need to take a closer look at the current acl
18:23:15 <knikolla> we might want NO_CHANGE
18:23:19 <gmann> and depends-on can be removed which is actually kind of change
18:23:32 <noonedeadpunk> yeah
18:23:54 <knikolla> #link https://gerrit-review.googlesource.com/Documentation/config-labels.html#label_copyCondition
18:24:06 <gmann> not sure it keep Code-Review	or its just RC voting only
18:24:16 <noonedeadpunk> it's about RC only
18:24:22 <gmann> k
18:24:30 * noonedeadpunk trying to find that in project-config now
18:24:40 <fungi> #link https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/governance.config
18:24:46 <fungi> i was already looking at it
18:24:52 <knikolla> Thanks fungi
18:25:07 <noonedeadpunk> #link https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/governance.config#L29
18:25:17 <noonedeadpunk> yeah
18:25:29 <gmann> it is same for Code-Review
18:25:49 <noonedeadpunk> huh, yes, we override default behaviour of CR
18:25:50 <fungi> clarkb: ^ do you recall seeing this happen with other less-common review labels?
18:26:20 <clarkb> fungi: no, but that comes from gerrit's migration default iirc. TRIVIAL_REBASE is a superset of NO_CODE_CHANGE I want to say
18:26:29 <clarkb> or at least is documented to be, but maybe they are wrong
18:26:50 <clarkb> its all configurable though so just set it to what you want
18:27:20 <fungi> for the openstack/releases PTL-Approved label we used "changekind:NO_CODE_CHANGE OR changekind:TRIVIAL_REBASE"
18:27:24 <gmann> so it is changed in all repo config files ?
18:27:31 <clarkb> gmann: no
18:27:43 <knikolla> Commit messages are important for governance patches, so I think we should change the current behavior for Roll-Call Votes for governance.
18:27:58 <fungi> most projects inherit the default Code-Review label definition and don't override it
18:28:08 <gmann> https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/tempest.config#L12
18:28:09 <fungi> git history for that file will probably provide some rationale
18:28:21 <clarkb> fungi: it was the conversion from the old function which was deprecated/removed
18:28:29 <clarkb> and it is based on what gerrit itself converts it as iirc
18:28:39 <clarkb> basically its the 1:1 per gerrit to what you had with afunction
18:28:40 <fungi> i mean reason for why it's got an override for code-review
18:29:03 <clarkb> its beacuse the have custom labels
18:29:16 <clarkb> I don't know why the governance repo needs custom labels though
18:29:28 <fungi> looks like https://review.openstack.org/187326 from 2015
18:30:01 <JayF> Is this something we need to fix live in the meeting? Or can we action item a fix to check up on next week
18:30:06 <fungi> er, no, that mainly just renamed the vote, nevermind
18:30:10 <fungi> JayF: it is not, no
18:30:18 <fungi> we can pick this up in #openstack-infra
18:30:24 <knikolla> alright, anything else to discuss on Python 3.8?
18:31:01 <knikolla> both patches got a sufficient number of votes. thank you all
18:31:23 <knikolla> #topic Open Discussion and Reviews
18:31:50 <knikolla> Floor is open for any other matters to discuss
18:32:54 <fungi> oh, well i continued researching and posted in #openstack-infra, but short answer is that the reason code-review is overridden stems from a change in 2015 to intentionally make it not required for merging
18:33:14 <fungi> #link https://review.openstack.org/185785 "Alter governance repo voting rules"
18:33:33 <clarkb> I think the in person board meeting attendance for yvr needs to be requested real soon now
18:33:43 <fungi> hopefully that at least provides some background on wht it's different from other acls
18:33:44 <gmann> but copyAllScoresIfNoChange  was not there
18:33:48 <clarkb> for anyone intending to go that hasn't rsvpd
18:34:19 <gmann> it says it was default true for everyone but we did not see this behavior earlier https://review.opendev.org/c/openstack/project-config/+/880115
18:34:36 <gmann> either old flag was not working or new one added it
18:35:27 <noonedeadpunk> clarkb: I've asked Alison to count me in, but I'm not aware of details (in terms of where/when exactly)
18:35:46 <rosmaita> which day is the board meeting?
18:35:51 <noonedeadpunk> Monday
18:35:52 <clarkb> noonedeadpunk: http://board.openinfra.dev/meetings/2023-06-12
18:35:54 <gmann> other repo where new flag NO_CODE_CHANGE  is added had copyAllScoresIfNoCodeChange  to true explicitly
18:35:55 <spotz> Board meeting is Monday at Microsoft
18:35:57 <clarkb> that has all the details
18:36:26 <knikolla> Thanks clarkb, spotz
18:36:40 <slaweq> spotz (@_oftc_spotz:matrix.org) in Vancouver, right?
18:36:52 <knikolla> slaweq: yes
18:36:53 <spotz> slaweq: Yeah
18:36:54 <gmann> yes
18:37:02 <spotz> It's in Gastown section so not far
18:37:02 <slaweq> ok, I will be there :)
18:37:26 <spotz> But as mentioned you need to let Allison know so you can be on the list for entrance
18:37:34 <slaweq> should I get any email with details or something like that? I already asked aprice (@_oftc_aprice:matrix.org) that I would like to be there
18:37:58 <spotz> I would assume you'd get added to the invite but not sure
18:38:04 <gmann> there is space constraints I think good to get confirmation from aprice
18:38:29 <slaweq> ok, I will confirm with aprice (@_oftc_aprice:matrix.org) to be sure that I'm on the list
18:38:35 <slaweq> thx
18:38:45 * noonedeadpunk needs to do the same
18:39:47 <knikolla> If there's nothing else, we can all get back 20 minutes
18:39:48 <noonedeadpunk> btw, talking about the event - does anybody knows if gold memebers rsvp dinner is only through org list or there's a path for tc?
18:40:04 <knikolla> oh, a dinner
18:40:24 <knikolla> i don't know anything about it.
18:40:40 <gmann> melwitt: it needs to be from company list i think aprice mentioned she will contact company representative to give passes
18:40:59 <gmann> but not sure if TC can get too :)
18:41:06 <noonedeadpunk> It's on Tuesday 13/6
18:41:25 <gmann> it was for all members company getting some passes to participate in that
18:41:36 * noonedeadpunk was thinking if to occupy place in company list or not :D
18:42:02 <knikolla> enjoy it for the rest of us :D
18:42:09 <spotz> I don't think TC is included. Board and sponsors
18:42:36 <gmann> spotz: board also? I think it was member company and foundation staff ?
18:42:43 <noonedeadpunk> Board as well, yes
18:42:57 <dansmith> if I'm not going to be in vancouver, can I be excused now? :)
18:43:02 <spotz> There's something on Tuesday, I wouldn't have called it a dinner though:)
18:43:15 <gmann> yeah that one might be different
18:43:17 <gmann> but anyways
18:43:18 <knikolla> #endmeeting