Tuesday, 2024-07-16

*** ChanServ changes topic to "Discussions for OpenStack Technical Committee | documentation: https://governance.openstack.org/tc/ | meetings: https://governance.openstack.org/tc/#meeting | channel logs https://meetings.opendev.org/irclogs/%23openstack-tc/"04:51
*** bauzas_ is now known as bauzas09:14
*** halali- is now known as halali16:03
*** halali is now known as halali-16:04
gmanngouthamr: done17:04
gouthamrtc-members: meeting here in ~10 mins :) 17:50
spotz[m]\o/17:55
gouthamr#startmeeting tc18:00
opendevmeetMeeting started Tue Jul 16 18:00:12 2024 UTC and is due to finish in 60 minutes.  The chair is gouthamr. 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
gouthamrWelcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct.18:00
gouthamrToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee.18:01
gouthamr#topic Roll Call18:01
gmanno/18:01
dansmitho/18:01
frickler\o18:01
slaweqo/18:01
gtemao/18:01
spotz[m]o/18:02
JayFo/18:02
gouthamrcourtesy-ping: noonedeadpunk 18:02
noonedeadpunko/18:02
noonedeadpunksorry, got a bit late :)18:03
gouthamrawesome, full house 18:03
spotz[m]Just starting:)18:03
gouthamrlets get started18:03
gouthamr#topic AIs from last week18:03
gouthamrwe took a few regarding inactive/emerging projects18:04
gouthamrand we have some reviews pending18:04
gouthamri'll bring them up in a bit18:04
gouthamrMasakari: noonedeadpunk to follow up on the status and progress related to SQLAlchemy/Oslo.db issues18:05
opendevreviewSlawek Kaplonski proposed openstack/governance master: Update criteria for the inactive projects to become active again  https://review.opendev.org/c/openstack/governance/+/92150018:05
gouthamrany update here, noonedeadpunk? 18:05
noonedeadpunkfrankly - no :(18:06
gouthamrty, no problem.. we can pursue this next week18:06
noonedeadpunktrailing behind the plan dramatically18:06
gouthamrdalees responded to the ML post regarding adjutant's pending patches and broken CI18:06
gouthamr#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/RJD75IM5OTDTI4SUUTZQ7F23J4ZSZCSG/ 18:07
gouthamri saw some patches merging with his help; so hopefully this looks good/trending better for the release team's concerns as well18:08
gouthamrany concerns regarding adjutant? 18:09
noonedeadpunkjust checked masakari results from the last week recheck - and they're utterly broken :( 18:09
noonedeadpunkhttps://review.opendev.org/c/openstack/masakari/+/920034/1#message-30bd512eedaae5eff4268d1460b00cf78a9cf25218:09
gouthamrah; we probably need suzhengwei's attention18:11
noonedeadpunkyeah, for sure18:11
frickleradjutant looks ok-ish to me after a quick glance at gerrit18:11
noonedeadpunkI'll try to propose a fix though18:11
gouthamrnoonedeadpunk: thank you.. 18:12
gouthamrfrickler: ack; ty18:12
gouthamrthe other pending items/AIs we took last week were regarding retirement of kuryr-kubernetes and the eventlet removal goal proposal18:13
gouthamrwe can run through the gate health topic and get to these as part of our usual tracking18:14
gouthamr.. discussion18:14
gouthamrdid i miss any other AIs? :) 18:14
gouthamr#topic A check on gate health18:15
dansmithI've been very consumed lately,18:15
dansmith(and was out last week) but the big CVE push from the week before definitely had a lot of rechecking, but things did eventually move through18:16
dansmithlots of the usual, timeouts doing volume things, failures to ssh to instances that were otherwise healthy, etc18:16
slaweqregarding ssh timeouts we have some new issue recently in neutron18:17
frickleralso zuul itself was having multiple issues in recent days18:17
slaweqhttps://review.opendev.org/c/openstack/neutron/+/924213 this should hopefully make it better18:17
gouthamrcurious about that; do the tests in nova/integrated-gate/neutron use cirros always? or some other OS images too? 18:17
dansmithonly cirros18:18
slaweqbut this is also for the ml2/ovs or lb jobs, so no default configuration from devstack18:18
dansmithfor the base jobs anyway.. I think maybe ironic and tripleo used other OSes18:18
dansmithgouthamr: in general, real OSes have hard-coded memory requirements that mean they won't even boot in 128MB instance flavors18:18
JayFWe use cirros as the image we install on the nodes. We use other OSes for ramdisks (similar to octavia having amphora with non-cirros)\18:19
frickleriiuc neutron uses ubuntu for some advanced tests18:19
gouthamrmanila does ubuntu images; and SSH timeouts are a frequent problem.. 18:19
JayFI'll note I've been working on DIB support for gentoo, and Ironic will be looking into doing IPA ramdisks with gentoo. It's likely also possible to create a minimal alternative to cirros if we ever had a reason to do so.18:19
slaweqfrickler: true, but only in the neutron-tempest-plugin jobs and in some specific tests18:19
slaweqin most of them we use cirros18:19
noonedeadpunkyeah, we felt quite some instability in zuul recently18:20
noonedeadpunkincluding timeouts reaching API during docs promotion18:20
noonedeadpunk(basically fetching the artifacts)18:20
gmannthere was some proposal to test other img in tempest as integrated but we have not done much progress on that18:20
noonedeadpunkfwiw dib has couple of outstanding patches for fixing fedora builds (non-container way)18:21
gouthamrJayF++ nice; i'd be interested to try that! gentoo has a decent package manager and nfs/samba/ceph clients! 18:21
JayFgouthamr: happy to chat about it sometime in another venue; I am a gentoo contributor and pretty expert level at it :)18:22
funginoonedeadpunk: if it was over the weekend, that was due to some changes in the query planner leading to sub-optimal queries that bogged down the servers18:22
noonedeadpunkI think it was today18:22
fricklerfungi: no, that was 2h ago18:22
fungioh, so something new presumably18:22
noonedeadpunkhttps://zuul.opendev.org/t/openstack/build/6caf416c14c44ca6b20bc834556d1d3a18:22
noonedeadpunkI also timouted with same query localy just in case18:22
dansmithI'm sure that wouldn't matter at this stage, all it has done is clone requirements and try to install it.. I think all that is disabled but let me confirm18:25
dansmithoops, sorrty18:25
gouthamrack; few issues here :) ty for highlighting the SSH issue dansmith.. since the image wasn't changed, the problem there could be related to the sporadic issue that the neutron dhcp change that was reverted may have improved? Or has this been seen before 18:25
dansmithwe see it all the time18:26
gouthamrah18:26
gouthamrso needs some more investigation :/ 18:27
gmannSSH issue is consistent since many years :)18:27
dansmithit's been ten years, which is why I say the usual18:27
dansmithright18:27
gouthamrand these timeouts are pretty large too? 300 seconds iirc18:28
dansmithit's not a timeout problem,18:28
dansmithit's a no-connectivity-so-timeout problem18:28
dansmithno amount of waiting will fix it18:28
gouthamrmakes sense18:28
gouthamror doesn't - unless we root cause this to some misconfigured ports or dhcp/network flows 18:29
slaweqin some of those cases I noticed issues with metadata which wasn't reachable thus there was long boot time and timeouts18:29
slaweqbut even if we would wait longer in such case it won18:30
slaweq*won't help18:30
slaweqbecause there will be no ssh key inserted into the guest vm18:30
dansmithnah, that's not the issue we normally see, we see connection timeout18:30
dansmitheither way,m18:30
dansmithno need to triage these old issues here I think18:30
slaweqI was investigating that issue already but did not found anything18:30
dansmithI really just mentioned it as "the usual general failures"18:30
slaweqdansmith ok18:31
gouthamrack; i wonder if we can create a bug nevertheless and keep piling on logs/triage information18:31
gmannyeah, we have investigated and debugged and workaround it a lot but nothing worked well or fix the root cause. 18:31
dansmithI bet there's plenty already18:31
dansmithtbh I'm surprised to hear that anyone is surprised about this :)18:31
gmannyes, there are many in tempest also logged 18:31
gouthamrsheesh newbies, dansmith 18:31
gouthamrack; ty.. i'll track some down and poke you after the meeting18:32
gouthamrany other gate discussions to be had today?18:32
gouthamrregarding non-cirros images, glad to see JayF's experiments with dib and gentoo, please feel free to post any updates here in the coming weeks18:32
JayFFor the newbies, Ironic has a similar issue with random failures, usually associated with dnsmasq crashes. It's been reported upstream and is unplanned to be addressed afaict18:33
JayFSo we'll have to implement support for something like kea to get outta that one :( 18:33
gouthamrwe hammer things pretty hard18:33
JayFI think you get the general impression of why they are uninterested in fixing the hard memory safety bug, yeah :D Only really happens in OpenStack CI18:34
gouthamrperhaps you'll be chatting about the zuul query issues in #opendev18:36
gouthamrhehe, you are.. 18:36
gouthamrlets move on 18:36
gouthamr#topic 2024.2 TC Tracker18:37
gouthamri wanted to start with eating the frog 18:37
gouthamr#link  https://review.opendev.org/c/openstack/governance/+/902585 (Remove eventlet from OpenStack)18:38
gouthamris this one ready to merge?18:38
noonedeadpunkit's not having enough votes at very least...18:39
JayFonly 3 of 9 TC members have voted on it by my count18:39
gouthamrnot by the TC rules though, it has enough to merge.. but, i don't like to get it in without more buy-in 18:40
gtemaI'll review this tomorrow18:40
noonedeadpunk+1 to ^18:40
fricklerI have a question about the procedure, it is going to be merged as "proposed" goal, is the expectation that it will move to "accepted" unchanged?18:40
gouthamrnot really; and that's something we should brainstorm18:40
gmannremember this is goal proposal which does not require formal-vote but selection of goal need the motion 18:40
JayFfrickler: right now, honestly, I think the point is more to get a roadmap down for people to follow, regardless of if we commit to it as a goal or not18:40
dansmithwell, (not) comitting to it as a formal goal is pretty important to earn my vote18:41
noonedeadpunkah, then probably it's ready for merge18:41
gmannyeah, selection of goal is separate process and goal document can be improved many times based on feedback18:41
frickler+118:41
gouthamrfor one, i'd move all of hberaud's lovely explanation into a doc :D 18:42
spotz[m]I'm sure he would if we asked18:42
gouthamrand suggest a roadmap18:42
gouthamrand a structure around getting this done across openstack like the proposal seeks18:43
gouthamrspotz[m]: yeah.. for now this is okay.. i think its a good read, sometimes the dire warnings are repetitive, you get the point after a while.. but, the length of this may be deterring people to review.. 18:44
gouthamrbut, its been evolving this way for months18:45
gtemaindeed  -the length is pretty scary18:45
noonedeadpunkyeah, 1500 lines needs quite some determination to finish :D18:45
spotz[m]Possibly, and there's differeent ways to configure looking so you might get all the comments or only some of them18:45
JayFgtema: yeah, the original was more like "this is the solution" and was shorter, this version is more of a menu of solutions18:46
gtemait's all clear, but ...18:46
gouthamrhaha :D 18:46
gouthamrso would we need a few more days to look/iterate on this?18:47
gtemayeah, just days, not weeks18:48
gouthamrty please do; we'll try to get the proposal in, or out by next week.. 18:49
gouthamrwhen you comment please do note if something needs to be clarified when we accept the goal 18:49
gouthamrnoonedeadpunk frickler dansmith gmann slaweq - is this okay? :)18:50
dansmithI honestly can't promise anything.. most of my world is still on fire and I'm pretty grumpy about this topic18:50
gouthamrsorry for the ping/mention.. i want to understand the process myself and not let this stagnate 18:50
gouthamrdansmith: ack, your past concerns regarding enforcing asyncio across the board may be addressed 18:51
gouthamrso i'll tease you to look at those parts and keep us honest18:51
slaweqGood for me18:51
noonedeadpunkyup, sounds good18:51
noonedeadpunkcan I ask to land like... Monday or smth? As there's a chance I will have time for a good read only during weekends...18:51
gouthamr++18:51
gmannok for me.18:51
gouthamr++18:52
gouthamrokay then; i'll follow up async18:53
gouthamrlets go down the tracker18:53
gouthamr#link https://review.opendev.org/c/openstack/governance/+/923441 (Inactive state extensions: Freezer)18:53
gouthamr#link https://review.opendev.org/c/openstack/governance/+/923919 (Inactive state extensions: Monasca)18:54
gouthamr^ these two will ofcourse conflict; don't know if its worth rebasing right away, if folks have concerns with one or the other18:54
gouthamr#link https://review.opendev.org/c/openstack/governance/+/924109 (move skyline out from the "Emerging Projects" list)18:55
gouthamrthese should address the project inactivity/emerging projects concerns that we brought up in the past weeks18:56
gouthamrpending noonedeadpunk's investigation into masakari, i think we're looking good.. please take a look and express any concerns on these patches18:56
fricklerregarding skyline I saw this patch and it made me wonder whether we should be concerned  openstack/skyline-console master: Lock setuptools version as 69.2.0  https://review.opendev.org/c/openstack/skyline-console/+/92413018:56
noonedeadpunkmasakari fix was really easy: https://review.opendev.org/c/openstack/masakari/+/92427818:57
noonedeadpunkbut now someone should merge that :D18:57
gouthamrnoonedeadpunk: haha, you put that together during the meeting 18:57
gouthamrfrickler: yikes; but, its in the makefile.. do we expect that to be adhered to by distros? 18:58
fricklerwell, distros will have to execute the build somehow, too18:59
JayFAt a minimum, at least they're documenting it for distros.18:59
gouthamrhttps://github.com/pypa/setuptools/issues/430018:59
JayFPackagers should be looking at Makefiles even if not directly using them.18:59
gouthamrsorry; we're at the hour19:00
JayFo/ ty gouthamr 19:00
gouthamrfrickler: can you post this to the skyline graduation patch as well please?19:00
gouthamrthanks for noticing it19:00
gouthamrthank you all for attending19:00
gouthamrwe'll hopefully reprise Open Discussion in future meetings19:01
gouthamr#endmeeting 19:01
opendevmeetMeeting ended Tue Jul 16 19:01:12 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2024/tc.2024-07-16-18.00.html19:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-07-16-18.00.txt19:01
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2024/tc.2024-07-16-18.00.log.html19:01
fungii'm working on the openstack section of the next foundation newsletter, deadline for content is tomorrow. if anyone has suggestions for things they think should be mentioned, please add them to the usual brainstorming etherpad:19:01
spotz[m]Thanks Gouthamr19:01
fungi#link https://etherpad.opendev.org/p/newsletter-openstack-news OpenStack Newsletter Ideas19:01
gtemathks, cy19:01
slaweqthanks19:02
gouthamrw00t thanks for checking fungi 19:02
spotz[m]fungi: Has Helena submitted anything for the OpenInfra Day NA?19:02
gouthamrwasn't the CFP supposed to open yesterday? :) 19:02
spotz[m]Yeah need the link?:)19:02
spotz[m]https://forms.gle/zdeT2Mg5CBjiMu6z919:03
fungispotz[m]: submitted in what way? i think the newsletter highlight is the asia summit schedule, but i'll check if the oid-na cfp is going to get a mention too19:04
spotz[m]Thanks fungi and sponsorships too, I think registration link will be confirmed in the next day or so19:04
fungii'm asking her19:05
noonedeadpunkah, I wish our org had a budget for US OID....19:05
fungii mean, she's the one who coordinates the newsletter content, so probably, but will know in a bit19:05
spotz[m]hehe, should have figured that was her19:06
fungiit's not like we have vast and limitless staff or anything19:06
fungijust a handful of meat-based coffee-powered machines that never sleep19:07
* fungi just realizes he forgot to put sleep on his schedule for tonight19:07
spotz[m]Bad fungi!19:08
fungispotz[m]: helena says yes to all of the above19:11
spotz[m]Sweet19:11
fungi(cfp, sponsorships, reg link if available by then)19:11
fungiand now that cfp is open i have a couple of sessions i need to submit19:11
spotz[m]Submit away!19:30
*** bauzas_ is now known as bauzas19:36
*** bauzas_ is now known as bauzas20:55
*** bauzas_ is now known as bauzas22:21
*** bauzas_ is now known as bauzas23:56

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