Tuesday, 2023-08-08

opendevreviewKristi Nikolla proposed openstack/governance master: Unmaintained status replaces Extended Maintenance  https://review.opendev.org/c/openstack/governance/+/88877113:52
knikollao/14:04
rosmaita\o14:07
knikollatc-members: reminder for the meeting in ~1 hr.16:58
dansmithjust FYI, I will not have time to review the latest update with just a few hours notice17:18
JayFdansmith: it's one line added17:20
JayFprobably more trivial than you expect :D 17:20
JayFalthough understandable in any event17:20
knikolla#startmeeting tc18:00
opendevmeetMeeting started Tue Aug  8 18:00:04 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#topic Roll Call18:00
slaweqo/18:00
knikollaHi all, welcome to the weekly meeting of the OpenStack Technical Committee18:00
knikollaA reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct 18:00
knikollaToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee18:00
knikollao/18:00
dansmitho/ (still finishing prior meeting)18:00
rosmaitao/18:00
gmanno/18:00
noonedeadpunko/18:01
knikollawe have one noted absence from Amy. 18:01
JayFo/18:01
knikolla#topic Follow up on past action items18:02
knikollaWe have one action item from the last meeting18:02
knikollarosmaita to review guidelines patch and poke at automating it18:02
rosmaitadid not have time to do any automation this week18:03
knikolla(I imagine I meant writing SLURP release notes guidelines)18:03
knikollano worries, adding it back to the action list then :)18:03
rosmaitai think i did update the patch to fix dansmith's issues18:03
knikollaawesome, thanks. 18:04
knikolla#action rosmaita to poke at automating SLURP release guidelines. 18:04
knikolladansmith: as the next topic item is gate check, we can wait a minute or two until you're back from the other meeting. 18:04
dansmithwell,18:05
dansmithI'd say progress has been made and things are slightly better now18:05
gmannthings are more stable now18:05
gmannyeah, many and many fixes are merged in past couple of week18:05
knikolla#topic Gate health check18:05
dansmithbut I'm still rechecking the nova patch that I was rechecking when we had this conversation last week18:05
dansmithsome of that is unrelated to other projects,18:06
slaweqI saw today some nova patch which was rechecked 20 times before merged18:06
dansmithbut we did effectively merge a gate break that took us a couple days to resolve18:06
dansmithslaweq: yeah18:06
noonedeadpunkwe had some issues with ubuntu images related to libgcc118:06
noonedeadpunkBut it was fixed quickly after being reported18:06
slaweqI also started looking at the SQL queries which neutron is doing but I don't have anything important yet18:07
gmannslaweq: it should be better now, we had many patches waiting on multiple patches to merge18:07
dansmithI've seen no OOMs since we merged the patch to bring conccurrency back down18:07
dansmithas in, opensearch shows none18:07
noonedeadpunkThough, we have spotted couple of nasty regressions in keystone while upgrading to 2023.1, but that's different topic...18:07
rosmaitajust caught 2 OOMs on a single run18:07
dansmithbut there were 12 in the one job I monitor the day before18:07
dansmithrosmaita: which job?18:08
dansmithwe didn't back it down for all jobs18:08
gmannrosmaita: and today?18:08
gmanntempest-full-py3, multinode jobs are now on 4 concurrency so any job inheriting from those run with 418:08
rosmaitacinder-tempest-plugin-lvm-lio-barbican hit two OOM errors:18:08
rosmaitaAug 08 16:19:05 np0034894611 kernel: Out of memory: Killed process 49892 (mysqld)18:08
rosmaitaand not surprisingly, after that there are a bunch of 500s from identity service. System eventually recovers, and then:18:08
rosmaitaAug 08 16:39:26 np0034894611 kernel: Out of memory: Killed process 126697 (qemu-system-x86)18:08
rosmaitaand a bunch of timeouts during tests18:08
rosmaitaso we should do whatever you did for those other jobs18:09
dansmithwhat's the inheritance for that job?18:09
rosmaitahttps://zuul.opendev.org/t/openstack/job/cinder-tempest-plugin-lvm-lio-barbican18:10
gmannit is with 6 concurrency as it inherit from devatck-tempest18:10
dansmithyeah, doesn't inherit from the one we lowered18:10
rosmaitayeah, it inherits from devstack-tempest18:10
gmannbut let's monitor more if there are more oom there and we can lower it down accoringly 18:10
rosmaitawhat's the one you fixed?18:10
dansmiththat's good data, that we've seen zero on the integrated-storage job but the other jobs are still hitting18:10
gmannrosmaita: https://review.opendev.org/c/openstack/tempest/+/89068918:10
rosmaitathanks18:11
gmannlower down the concurrency to 418:11
dansmithlemme opensearch that job18:11
dansmith2 today so far, 4 yesterday18:11
dansmithit runs a lot less than the other jobs so the numbers are definitely lower overall18:11
dansmithhighest in the last two weeks is 8 for scale18:11
dansmithother than that, it's been just small gains to make things better18:13
gmannlet's monitor more if it occurs or even in other jobs too18:13
dansmiththings are definitely better, but skipping a 100% fail regression took like four rechecks to land in tempest yesterday18:13
gmannit is easy fix to set it back to 418:13
dansmithyup18:13
fungiif you have a regression fix you need prioritized in the gate, don't hesitate to give me a heads-up18:14
gmannyesterday I saw highest number of patches merged in tempest in last 5-6 months :) I checked in today morning and many were merged.18:14
dansmithfungi: yeah I keep thinking about doing that, but.. just never do18:14
gmannotherwise it was always avg of 3-4 days to merge anything18:14
fungieven if it means forcing it back into the gate pipeline after a failure18:14
dansmithgmann: I'm still rechecking this to try to clean up our gate: https://review.opendev.org/c/openstack/nova/+/88999218:15
dansmithand it keeps failing :)18:15
gmannit will also go in today :)18:15
dansmithpromise? :)18:15
gmannheh18:16
dansmithanyway, that's enough from me18:16
gmannnova has more diff set of configuration jobs so we never know18:16
gmannnothing else from me too on gate18:16
knikollanoonedeadpunk: you mentioned some keystone regressions. do you have some links I can look at and bring up to tomorrow's keystone meeting? 18:17
noonedeadpunkknikolla: one was https://bugs.launchpad.net/openstack-ansible/+bug/202880918:18
noonedeadpunkanother wasn't filled as a bug, but all tokens are invalidated right after upgrade, which requires cache to be wiped (I assume)18:19
noonedeadpunksecond caused by https://opendev.org/openstack/keystone/commit/f6a0cce4409232d8ade69b7773dbabcf4c53ec0f18:20
noonedeadpunkfirst one is most nasty, as you never know who had a password >54 symbols, so really random ones are invalidated18:21
knikollathe added field in the token? https://bugs.launchpad.net/keystone/+bug/202913418:21
noonedeadpunkah, yes18:21
knikollathanks for bringing them up.18:22
knikollamoving on :)18:22
knikolla#topic Unmaintained status replaces Extended Maintenance18:22
knikolla#link https://review.opendev.org/c/openstack/governance/+/88877118:22
knikollaI did a manor update to bring the proposal inline, please take some time this week to review.18:22
knikollaHopefully this is the last iteration :) 18:22
knikollaminor*18:22
rosmaita"manor" sounds more elegant18:23
gmannok, I have not got chance to look into that as my tuesday is meeting till noon18:23
gmannI will check after meeting18:23
knikollathat would make it unaffordable :)18:23
slaweq😀18:24
knikollathe entirety of the update is the addition of the line "The PTL or Unmaintained branch liaison are allowed to delete an Unmaintained branch early, before its scheduled branch deletion."18:24
dansmithgmann: you too? idk what it is about tuesdays but people love to schedule meetings on it18:25
dansmithgmann: that nova n-v patch just failed again.. I dunno which timezone "today" was in for you :D18:25
gmannyeah, my total meeting (upstream + downstream) goes to 8-9. half of them in morning and half in evening :)18:26
gmanndansmith: :),18:26
gmannI take my word back18:26
dansmith:P18:27
JayFI know I was a holdout on the old proposal, I've already +1'd this one18:27
JayFso it's extremely likely we've hit consensus if folks can make time to vote soon we can get cinder off the hook18:27
knikollathanks slaweq and JayF 18:28
gmannyeah, we are already late on this18:28
gmannwill check right after meeting18:28
knikollawe can move on to the next topic then18:28
knikolla#topic User survey question updates by Aug 1818:28
knikolla#link https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034589.html18:28
knikollaIf we want to do any changes to the user survey for 2024, the deadline for proposing question changes is Friday, August 18.18:29
knikollaPlease see the above linked email for more information.18:29
gmannyou mean TC question only right ?18:29
noonedeadpunkknikolla: wanna add there if ppl are aware of password limit to 54 symbols ?:)18:29
knikollaThat applies for both questions from the TC and from project teams18:29
dansmithnoonedeadpunk: hah18:29
JayFIronic is working on user survey questions in an etherpad here, suggestions/comments welcome if anyone wants to take a look: https://etherpad.opendev.org/p/ironic-user-survey-questions-202318:30
JayFI'm happy to take a similar look at TC questions; but I'm not sure I have any to propose but I will think.18:30
fungiyeah, i mean, if you see things that are project-specific but need updating (projects missing from some lists, for example) please call those out18:30
gmannwe did for TC question last time after doing the survey analysis and what can be useful for our analysis 18:30
rosmaitaiirc, Helena or Allison sent a link to a list of the questions, anyone have that link?18:30
fungifor example, i noticed the list of "what openstack services do you install" has a few missing18:31
gmannbut did we do analysis for last survey after we changes the questions ?18:31
gmannlast analysis I find is 2021 #link https://governance.openstack.org/tc/user_survey/analysis-04-2022.html18:31
gmannwhich I think is before we updated the questions18:31
fungi#link https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034596.html18:32
fungithat has the link to the spreadsheet to take notes/feedback in18:32
rosmaitathanks!18:32
fungibut also you can reply on the ml if you prefer18:32
fungiwhich may be more useful if there's something you want to discuss about it rather than specific feedback you have18:33
gmannJayF: this is what we updated for TC question for 2023 survey #link https://etherpad.opendev.org/p/tc-2023-1-ptg#L10418:33
JayFack, ty18:34
gmannbut my question is we should do the survey analysis otherwise we are not at all looking into the response/feedback 18:34
knikollaThat's a fair point. 18:35
slaweq@gmann you mean 2023 survey analysis? 18:35
gmannupdating a few more question if we need is good. also one thing to note that adding the new questions has some cap. we can remove/update the old one first if needed18:36
gmannslaweq: last we did for 2021 only. I think 2022 survey feedback is out after that18:36
slaweqOk18:36
gmannslaweq: 2023 feedback is not yet out which is due in Aug end18:36
slaweqAhh, ok18:37
gmannAug 23rd is deadline to fill 2023 survey so after that it will be available18:37
gmannthat has our latest updated questions we discussed in PT18:37
gmannPTG18:37
slaweqSo I ment 2022, last one which just finished recently if I'm not mistaken18:37
gmannyeah18:37
slaweqAnd I agree that we should do analysis of it18:38
gmannAs per past analysis, there were some of the important information from TC perspective 18:38
slaweqI can help with that 😃18:38
knikollaslaweq: I can forward you the excel file with 2022 responses. 18:39
slaweq@knikolla thx 18:39
gmannslaweq: thanks 18:39
knikollaas I think I may have it. 18:39
fungiis there an nda associated with that data?18:39
knikollahttps://lists.openstack.org/pipermail/openstack-discuss/2022-October/030843.html18:40
slaweqThx18:41
fungiokay, so that's the nda-free version. cool18:41
gmannslaweq: this can be helpful too https://www.openstack.org/analytics18:41
slaweq@gmann thx, I know that page already18:41
gmanncool18:42
knikollaWe can touch base next week again and see if we have any ideas or insights that we can shape up to be updates to questions. 18:43
knikollaanything else on the topic? 18:43
gmannslaweq: I found the email from aprice including the xls, forwarded the email to you18:44
slaweqThx @gmann 18:44
gmannslaweq: but that is super unreadable :) and jungleboyj knows the trick to read/convert it to better way18:45
gmannhe is the one did two user survey analysis and posted in TC page18:45
slaweqOk. I will ping him if I will need any help there 😃18:46
gmann++18:46
fungiif the xls version is not the redacted/anonymized one, you may also need to agree to an nda18:46
knikollathe xls only has aggregate project usage data18:46
fungioh, so same as the csv version you linked to above18:47
gmannhumm, it should have TC questions also18:48
gmannits there with  TC* column for example 'TCOpenStackVersion' 'TCStableBranches'....18:50
knikollaanything else on the topic?18:51
knikolla#topic Reviews and Open Discussion18:52
fungidon't forget, quarterly informal call with the openstack community and openinfra board tomorrow at 18:00 utc (23 hours from now), put your conversation starters in the pad if you have any:18:52
fungi#link https://etherpad.opendev.org/p/2023-08-board-openstack-sync August 2023 OpenInfra Board Sync with OpenStack18:52
knikolla#link https://review.opendev.org/q/project:openstack/governance+status:open18:52
fungicall details are in that pad too18:52
knikollathanks fungi18:53
knikollatomorrow, 18:00UTC18:53
fungiyes18:53
knikollaSync up call with OpenInfra Board. 18:53
knikollatc-members please try to make it if you can18:53
knikollaalright, thanks all! 18:55
knikolla#endmeeting18:55
opendevmeetMeeting ended Tue Aug  8 18:55:19 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:55
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2023/tc.2023-08-08-18.00.html18:55
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2023/tc.2023-08-08-18.00.txt18:55
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2023/tc.2023-08-08-18.00.log.html18:55

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