Tuesday, 2023-08-01

mnasergmann, JayF: i was the second ever chair after dhellman and when gmann came in, i figured since i left dhellman in there, kept a little emiratus in there00:40
mnaserbut thats just the history lesson behind it :>00:40
gmannyeah01:24
JayFI just am pointing my mind at things like, e.g. the pypi maintainer cleanup -- and I lean in the direction of less people with access is better.01:49
*** elodilles_pto is now known as elodilles06:35
knikollatc-members: reminder, weekly meeting in ~1 hour. This is the one on Zoom. 16:59
diablo_rojoFigures when I would be able to participate in a meeting on IRC it would be the zoom week :/17:51
diablo_rojoknikolla: items for the newsletter was the more pressing item I wanted to bring up - if you can do a callout, I would appreciate it! https://etherpad.opendev.org/p/newsletter-openstack-news17:53
knikolla#startmeeting tc18:00
opendevmeetMeeting started Tue Aug  1 18:00:54 2023 UTC and is due to finish in 60 minutes.  The chair is knikolla. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
opendevmeetThe meeting name has been set to 'tc'18:00
knikolla#link https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09#success18:01
rosmaitaty18:01
knikolla#topic Roll call18:01
knikollao/18:01
slaweqo/18:02
gmanno/18:02
rosmaitao/18:02
dansmitho/18:02
JayFo/18:03
rosmaita#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting18:03
knikolla#topic follow up on past action items18:05
knikolla#link https://review.opendev.org/c/openstack/project-team-guide/+/84345718:05
knikolla#topic Release notes guidelines for SLURP/NON-SLURP cadence18:07
knikolla#action rosmaita to review guidelines patch and poke at automating it18:08
knikolla#topic Unmaintained status replaces Extended Maintenance18:09
dansmithknikolla: can we move gate health back up to earlier in the meeting like it used to be, or make sure we don't get into these 40 minute discussions in "past action items"?18:40
dansmithI have something to discuss re: gate health today and I'm wondering if we're going to have time18:41
knikollamakes sense, will do it starting from the next meeting. thanks for suggesting.18:42
dansmiththanks18:43
knikolla#topic gate health check18:45
funginot to interrupt the discussion, just a heads up that zuul has recently (as of our rolling upgrade last saturday) grown a throughput improvement insofar as that it can detect and act on job failures earlier than before (at the time of the first task failure rather than waiting until the job completes), so that may help speed up deep gate queues and gate reset propagation down the line.18:49
fungithere's some pending ui support to expose that rarly-failure state a little better, but at the moment it just looks like zuul has a premonition that the job will fail (because it already knows it's in the process of failing)18:49
fungis/rarly/early/18:50
fungithe keystone activity during devstack setup seems likely related to lack of token caching and insistence in devstack making lots of independent calls to openstackclient18:52
knikolla#endmeeting19:00
opendevmeetMeeting ended Tue Aug  1 19:00:07 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2023/tc.2023-08-01-18.00.html19:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2023/tc.2023-08-01-18.00.txt19:00
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2023/tc.2023-08-01-18.00.log.html19:00
knikollathanks all! 19:00
dansmithfungi: I think I saw that in action today, where a build was marked as failed with no failed jobs, and then later a failed job appeared19:01
fungidansmith: that's precisely it. in a week or two it will look like https://matrix-client.matrix.org/_matrix/media/r0/download/acmegating.com/ljRghcEytLBWKYFWrkFcQWIu19:02
dansmithah cool19:02
fungiwith descriptive tooltips19:03
fungiso the progress bar for the failing job will go red while it continues to finish up19:03
dansmithyeah, nice19:03
fungibut more importantly, zuul knows at that point the change as a whole is failing and can proceed with whatever downline retesting that may imply19:04
fungiso hopefully at least a minor speedup in change processing19:05
dansmithat the moment all I can hope for is a minor speedup in failing the next job which will obviously fail because everything is failing :)19:07
fungibingo! it's like you've been here a while19:08
gmann+119:08
dansmithheh19:08
gmannand can we add ability to stop the run by author if any quick job failing realize them no need to run it further as I need to debug current failure more19:09
gmannit can be done currently by pushing the change but if anyone need time to debug and do change/test locally then they will be able to stop the further run and give that node to other change19:10
gmannat least that will save a lot of nodes for the changes waiting in the queue 19:14
JayFI'll note, re: DB performance, Ironic did some benchmarking which led us down some paths to significantly improve our API performance (and by extension; backend DB performance) https://github.com/openstack/ironic/tree/master/tools/benchmark19:15
fungigmann: briefly abandoning and restoring the change can also do it19:15
JayFI'm not sure if there's anything useful or unique there which could be applied to Neutron or Keystone; but it's there19:15
JayFhaving the benchmark was super nice because we were able to clearly demonstrate when we improved vs not improved a thing19:16
fungizuul should act on the abandon event and dequeue the change immediately19:16
gmannfungi: yeah but that does not seems right way, abandon is more of denying the changes to go furher. idk19:16
JayFhttps://ironicbaremetal.org/blog/the-search-for-performance/ is a blog we published about the process19:16
fungizuul doesn't know anything about change owners or gerrit's acls, so you need some sort of action which will trigger an event zuul can act on19:17
fungisetting the change to wip state may now dequeue as well, worth checking19:18
gmannowner of that can be same as abandon/restore which is core group or author19:18
gmannohk, i did not know about wip. let me try that19:19
fungias in gerrit's wip toggle, though i suppose workflow -1 might do it too19:19
gmanntrying both19:20
fungii know those will keep zuul from trying to merge the change, but may not eject them from the gate, not sure19:20
gmannseems like not, I tried in this which still running https://review.opendev.org/c/openstack/tempest/+/89024219:22
knikolladiablo_rojo: I still see the items we added last time here https://etherpad.opendev.org/p/newsletter-openstack-news, did those get sent out and therefore I can clean them up and add new ones?19:22
dansmithW-1 to kick it out would be awesome19:22
gmannyeah19:22
fungigmann: oh! you were testing on a change that was in the check pipeline, not the gate19:55
fungiwe tested on https://review.opendev.org/890065 just now and workflow -1 definitely kicked the change out of the gate19:55
fungiapparently zuul's continuous evaluation of the votes and other submit requirements on a change is fairly new (in the past year), so maybe just nobody's noticed it worked19:59
diablo_rojo_phoneknikolla: they did not make it last time but I will make sure it's all added for this month! Feel free to add to the list through Thursday this week. 20:13
gmannfungi: ohk, at least that will be helpful. any chance we can do same for check pipeline too ?20:45
gmannfew of them in newsletter etherpad are not valid anymore, we should not add them in this month20:46
fungiwhat's the reason for dequeuing a change in check? those are independent so they don't wait on each other to complete anyway (or they require each other, so aren't going to complete any sooner if another one is dequeued)20:46
gmannfungi: same reason, if I see anyone integrated job failing early give me signal that this change need more debug/time/updates then I can at least stop other jobs still running and taking tiem20:48
gmanntc-members: FYI, board meeting in an ~11 min from now in case anyone want to join https://board.openinfra.dev/meetings/2023-08-0120:49
dansmiththis is just a regular one, not the tc-board sync right?20:49
knikolla++ thanks for the ping gmann20:49
knikolla@dansmith yep20:49
gmanndansmith: yes, regular one20:50
dansmithack20:50
opendevreviewBrian Rosmaita proposed openstack/project-team-guide master: Add SLURP release notes strategy  https://review.opendev.org/c/openstack/project-team-guide/+/84345721:38
TheJuliaknikolla, gmann, fungi: I just added the foundation-board address to the invite I have. If folks can confirm once it makes it through moderation if that works on their calendars, that might just be the easiest path forward. If not, I'll go add all add all of the directors one by one. 22:12
gmanncool, let me check22:13
fungii think jbryce moderates the board ml, if your post is stuck in moderation22:13
TheJuliagmann: I'm assuming, since it gets tagged as an isc file for an invite, that it will likely hit moderation, but Jonathan is typically pretty good at clicking that button quickly22:14
fungilooks like it went through22:14
TheJulia\o/22:14
TheJuliacool22:14
TheJuliaWell, in that case I'm going to go find some lunch22:14
fungikiller plan22:14
TheJuliaThanks everyone!22:14
fungithank you too!22:14
gmannTheJulia: perfect, it worked, I got the invite with ical22:14
fungiin the future i can send copies of those to the foundation-board ml in addition to openstack-discuss, if it helps22:15
gmann++22:15
TheJuliafungi: ++, that would be awesome, since it is easy for me to miss stuff or lag by a period  because I'm pulled in numerous directions22:16
fungii'm all too familiar with that feeling22:17
fungijust didn't want to step on any toes22:17
TheJulia:) It is a team effort!22:18
fungimore like group therapy ;)22:18
TheJuliaheh22:18
TheJuliaAnyway! lunch!22:19
* TheJulia re-engages cloaking device labeled "vacation"22:19
fungiyou're as terrible at vacation as the rest of us22:19
JayFI've been fussing at TheJulia for planning on taking this meeting from Maui for weeks, she can attest22:21
JayFthe sand on those beautiful beaches is jealous of the attention zoom just got LOL22:21
TheJuliaeh, more like 1.5 weeks since I booked my hotel/flights not even 2 weeks ago22:22
JayF1.5 is still weeks :D 22:22
fungiback to warm sands and tasty drinks!22:22
JayFmmm delicious sand22:23
* TheJulia shimmers away as only a trekie can22:23
spotz[m]I just logged in no one was still on22:26
fungispotz[m]: meeting started ~1.5 hours ago22:27
fungijust wrapped up22:27
spotz[m]I was at a dinner in Cork, we just ended22:27
fungialmost didn't make quorum, just got attendance over the minimum threshold about an hour into the call22:28
spotz[m]Yeah I got on when I could. It was 90 minutes until we got dinner. First meeting I’ve missed:(22:30
fungiwell, my point is, it wasn't just you who couldn't make it. you're in good company22:31
fungialso in cork. i wouldn't have bothered dialling in at all if that were me! ;)22:31
spotz[m]Hehe PTO is next Week:)22:33

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!