18:00:29 <gouthamr> #startmeeting tc
18:00:29 <opendevmeet> Meeting started Tue Aug 27 18:00:29 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:29 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:29 <opendevmeet> The meeting name has been set to 'tc'
18:01:08 <gouthamr> Welcome 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:01:13 <gouthamr> Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
18:01:27 <gouthamr> #topic Roll Call
18:01:30 <gmann> o/
18:01:30 <dansmith> o/
18:01:35 <frickler> \o
18:01:37 <spotz[m]> o/
18:01:40 <gtema> o/
18:02:05 <cardoe> o/
18:02:17 <slaweq> o/
18:02:26 <noonedeadpunk> o/
18:03:07 <gouthamr> nearly full house
18:03:09 <gouthamr> courtesy ping JayF
18:04:45 <gouthamr> alright; lets get started..
18:05:24 <JayF> o/
18:05:25 <cardoe> He was just talking to me in #-ironic so he'll hopefully be back.
18:05:48 <gouthamr> first off; i wanted to thank frickler for chairing the last meeting.. i put him on the spot
18:06:01 <gouthamr> #topic AIs from last week
18:06:06 <spotz[m]> He did a great job!
18:06:15 <gouthamr> ++
18:06:24 <frickler> ty
18:06:41 <gouthamr> from what i can tell, we didn't mark any AIs specifically to follow up this week..
18:07:08 <gouthamr> i do see one to continue the licensing discussion at a forum/PTG session
18:07:23 <gouthamr> i'll track this and plan it
18:08:04 <gouthamr> did i miss any other AIs you were tracking?
18:10:04 <gouthamr> regarding the licensing discussion, if anyone has ideas they'd like to put to paper, please do propose a resolution
18:11:12 <gouthamr> taking silence to mean no further AIs
18:11:15 <gouthamr> #topic OpenInfra event planning (spotz)
18:11:56 <gouthamr> spotz[m]:  had asked here a couple of days ago if anyone's going to be attending the OpenInfra summit in Suwon in-person
18:11:57 <gouthamr> #link https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2024-08-18.log.html
18:12:05 <gouthamr> #link https://2024.openinfraasia.org/
18:12:11 <dansmith> bauzas: ^
18:12:19 <spotz[m]> Ahh so I think this is about the TC session in South Korea next week and then thinking of doing an overall leadership one at NA
18:13:07 <fungi> worth noting that the "bridging the gap" forum session on the summit schedule is, as i mentioned in my ml post, an outcome of specific requests made by the tc to the openinfra foundation
18:13:21 <gouthamr> +1
18:13:26 <fungi> so if tc members are in suwon and don't have conflicts at that time, participation is welcome
18:13:31 <spotz[m]> Basically how I worded it for Asia was current, future(as the election won't be over), and past TC members to just come and answer any questions folks might have
18:13:48 <gouthamr> so if there are people on the floor, we have two events we would appreciate your participation in
18:14:09 <gouthamr> i'd go as far as "require" your participation in.. :) we need you.
18:14:26 <spotz[m]> And potentially for NA it would be Board and TC members, or any other OpenInfra project leaders there
18:14:33 <gmann> I will not be traveling either of events, otherwise would love to help
18:14:44 <noonedeadpunk> same here
18:14:47 <JayF> I will not be at either event as well.
18:14:55 <gouthamr> i'm hoping to be at the NA event
18:14:58 <JayF> Happy to participate in a remote session as long as we can make it work.
18:15:16 <gouthamr> ^ i will try to work on this
18:15:27 <fungi> i won't be in suwon, clarkb and ildikov are leading the forum session there, but i'm planning to lead a similar one in indianapolis for oid-na
18:15:42 <spotz[m]> It is 13 hour time difference FYI I did look it up to see if I could do regular work meetings while there
18:15:53 <spotz[m]> NA is possible if we do the session there
18:16:51 <bauzas> I'll stick around if no conflicts
18:17:12 <gouthamr> bauzas++
18:17:21 <bauzas> (tbc I'll be in suwon)
18:17:22 <JayF> spotz[m]: I'll note my willingness to participate remote comes with a volunteer to be up at silly hours :)
18:17:37 <JayF> (meaning I know if it happened, I'm probably going to be up at 3am or working at 9pm :D)
18:18:06 <spotz[m]> Ok I'll see if we can, I know there will only be a single wifi so Asia may not end up working for remote but I believe NA will
18:18:49 <spotz[m]> 6am CST I think
18:20:16 <gouthamr> ack spotz[m].. is there a possibility to move the time for NA? or is it inflexible?
18:20:53 <spotz[m]> Oh NA isn't even on the schedule:) That was the time translation for Asia
18:21:17 <gouthamr> my bad
18:21:26 <spotz[m]> I just know there's a slot on Oct 16 we may need something so offered this
18:21:40 <gouthamr> thank you.. since there can't be a remote session from Suwon, won't matter :)
18:22:06 <spotz[m]> I would say it may not be a good remote option
18:22:33 <gouthamr> im hoping those attending can come back and brief us about the interactions
18:22:51 <gouthamr> anything else to add about $topic spotz[m]?
18:23:10 <gouthamr> thank you for repping us, and for putting the session together
18:23:15 <spotz[m]> Nope, I'll report back after and update about NA
18:24:28 <gouthamr> thank you; lets move to the next topic
18:24:35 <gouthamr> #topic A check on gate health
18:24:51 <gouthamr> anything going on this week?
18:26:04 <gmann> about oslo.policy 4.4.0 u-c, only horizon yet to be fixed which I am working on. other projects fixes are either merged or up for the review
18:26:07 <gmann> #linlk https://review.opendev.org/c/openstack/requirements/+/925464
18:26:09 <gmann> #link https://review.opendev.org/c/openstack/requirements/+/925464
18:26:13 <JayF> no specific comments from me
18:26:36 <slaweq> gmann: is it related to S-RBAC?
18:26:43 <gmann> my target was last week to merge this but due to horizon failure it is pending. let's see how soon I can push fix and we can merge the requirement one
18:26:45 <gmann> slaweq: yes
18:27:08 <slaweq> so I also saw issue in the neutron-designate job which I need to investigate still
18:27:14 <gmann> slaweq: and neutron designate job also which I am testing with some possible fixes but no success yet
18:27:30 <slaweq> but it seems there is some issue related to s-rbac
18:27:38 <slaweq> ahh, thx
18:27:39 <gmann> it can be on designate side I think as there is change in config on neutron side but
18:27:50 <gmann> *no change
18:27:58 <gmann> I will discuss about it in neutron channel
18:28:00 <slaweq> if you will have anything, please let me know
18:28:04 <gmann> sure
18:28:14 <slaweq> if I will find anything, I will also ping you
18:28:23 <slaweq> but I will have probably time for it next week soonest
18:28:34 <gmann> slaweq: this one is my debugging change, feel free to try things here
18:28:36 <gouthamr> gmann: this requirement bump should merge this week?
18:28:37 <gmann> #link https://review.opendev.org/c/openstack/neutron/+/926945
18:28:45 <slaweq> thx
18:29:41 <gmann> gouthamr: I am not sure about deadline but as FF is this week, we should merge not later than that
18:29:58 <gouthamr> i was understanding this is our requirements freeze week as well
18:30:02 <gmann> I mean deadline for requirement change if there is any
18:30:18 <gouthamr> #link https://releases.openstack.org/dalmatian/schedule.html#d-rf
18:30:19 <gmann> yeah, requirement freeze also so yes this week is deadlin e
18:30:50 <frickler> reqs freeze doesn't hold for bumping openstack deliverables
18:31:06 <gmann> ohk
18:31:34 <frickler> though that isn't an argument to delay things if that can be avoided
18:31:58 <gmann> anyways I do not want to delay it just to avoid any last minute failure, though i tested/fixed ~15 projects on this so should not be any issue once we fix the horixon/neutron+designate job
18:32:07 <gmann> frickler: ++
18:32:41 <gmann> that is all from me on this
18:33:26 <gouthamr> okay; thank you gmann
18:33:33 <gouthamr> anything else for this topic?
18:34:38 <frickler> maybe on the aarch64 situation
18:34:39 <opendevreview> Doug Goldstein proposed openstack/election master: Add Doug Goldstein candidacy for TC 2025.1  https://review.opendev.org/c/openstack/election/+/927308
18:34:51 <frickler> we lost one of the donated clouds recently
18:35:01 <fungi> one of the only two
18:35:10 <dansmith> uh
18:35:18 <dansmith> I thought there were at least three?
18:35:28 <fungi> for aarch64/arm64?
18:35:35 <slaweq> :/
18:35:37 <frickler> and the other one (osousl) seems to be severely slower, which we didn't completely realise before
18:35:42 <fungi> only two (osuosl and linaro/worksonarm/ampere)
18:35:44 <dansmith> oh for arm
18:35:46 <dansmith> gotcha
18:35:54 <dansmith> missed that part :D
18:36:25 <frickler> so kolla already had to stop running image build jobs for that arch currently
18:37:13 <frickler> I'm not sure how much other projects are doing testing there
18:37:44 <slaweq> in neutron we are only running some UT jobs on arm IIRC
18:38:34 <gmann> mostly it is UT jobs only
18:38:51 <frickler> so more as an fyi, not much the TC can do about this I think unless someone can draw another cloud donor out of their head ;)
18:39:07 <dansmith> I'll be honest and say I really don't know who cares about the arm bit
18:39:21 <noonedeadpunk> oh well I do know
18:39:27 <fungi> cloud providers with arm hardware who want people to use it more, maybe
18:39:32 <JayF> There are multiple confirmed users in the Ironic community using Ironic on ARM to provision ARM and Ironic on AMD64 to provision ARM
18:39:32 <dansmith> IIRC the jobs were added a while back by someone that cared during the brief (?) obsession with arm servers
18:39:33 <noonedeadpunk> but probably not ones who can / in position to donate
18:39:35 <gmann> note, most of UT jobs are non voting so not sure about their status or who monitor the status
18:40:00 <JayF> dansmith: from my perspective, I still see ARM server usage on the rise, specifically in the AI/ML space.
18:40:01 <noonedeadpunk> Talking about arm I do have a topic for open discussion
18:40:19 <noonedeadpunk> (related to the user suvey)
18:40:22 <gouthamr> https://zuul.opendev.org/t/openstack/jobs with an "aarch" search tells me there's an ironic standalone job; and a "requirements-tox-py38-check-uc" (Run test for requirements project) job in addition to the kolla jobs
18:40:28 <dansmith> JayF: ack, I heard a lot about it for like a year several years ago, but I haven't heard much of anything in a long time
18:41:08 <JayF> yeah, I think the hype curve is falling off but as usual, actual use cases come flowing behind it without the hype :)
18:41:30 <dansmith> just.. someone needs to care if they want it
18:42:05 <JayF> ++ We have Ironic CI provisioning ARM-fake-BM-VMs on x86, which is really the case I'm more concerned about TBH
18:43:15 <opendevreview> Michael Johnson proposed openstack/election master: Adding Michael Johnson candidacy for Designate  https://review.opendev.org/c/openstack/election/+/927309
18:43:31 <gouthamr> alright; lets wrap this up and move to the next topic
18:43:38 <gouthamr> #topic 2024.2 TC Tracker
18:43:38 <gouthamr> 
18:43:43 <gouthamr> #link https://etherpad.opendev.org/p/tc-2024.2-tracker (Technical Committee activity tracker)
18:44:10 <gouthamr> ^ anyone chasing any item that has an update to share this week?
18:45:08 <gouthamr> probably not; things are looking better.. i'll make another pass on the etherpad and clean things up
18:45:13 <gouthamr> #topic Open Discussion and Reviews
18:45:17 <fungi> i've tried to initiate a discussion on the mailing list about improving communication patterns around code review and related contribution based on efforts started by a request from tc members last year to find out why many foundation member organizations are struggling to get people more active upstream, so participation from the current tc membership on that thread is greatly
18:45:19 <fungi> appreciated!
18:45:21 <fungi> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/GTPTFUPXXBDMWNQZGZDLM2IIX4FSTT5Y/ Bridging the gap between community and contributing orgs
18:45:31 <gouthamr> fungi++
18:45:33 <noonedeadpunk> so I was pointed today that we're missing bunch of things on the user survey
18:45:53 <noonedeadpunk> one thing - is relevant openstack releases - they stop on Antelope
18:46:03 <fungi> oh, ouch
18:46:03 <noonedeadpunk> While there's 2 more out
18:46:17 <fungi> i'll make a note to ask aprice about that
18:46:18 <noonedeadpunk> and another one - there's no KVM(aarch64) in list of used HVs
18:46:34 <noonedeadpunk> so we actually have no idea if anyone cares about arm...
18:46:34 <fungi> that definitely ties back into a recent discussion too! ;)
18:46:42 <clarkb> noonedeadpunk: do we distinguish between x86 and non x86 hypervisors already?
18:46:55 <clarkb> I think that is a good idea but the matrix is bigger than just x86 vs aarch64 kvm
18:47:14 <noonedeadpunk> there's plenty of things there acvtually
18:47:55 <noonedeadpunk> ppc64 is there for instance
18:47:57 <fungi> maybe a worthwhile step would be to check with the nova team to get a list of relevant hypervisor+processor backend combinations
18:47:58 <clarkb> got it
18:48:15 <fungi> i wouldn't be surprised if it was last revisited 5+ years ago
18:48:16 <dansmith> relevant or possible? :)
18:48:25 <opendevreview> David Wilde proposed openstack/election master: Add Dave Wilde's candidacy for Keystone PTL 2025.1  https://review.opendev.org/c/openstack/election/+/927310
18:48:30 <fungi> i suppose possible, and then we can find out which is relevant
18:48:32 * gouthamr probably missed an email asking for teams to update their questions for this 2024 survey
18:49:02 <noonedeadpunk> given we are still having essex among releases - that's a good question
18:49:05 <dansmith> https://github.com/openstack/nova/blob/master/doc/source/user/support-matrix.ini
18:49:14 <dansmith> not sure where that gets rendered
18:49:26 <fungi> as in, what target platforms does the nova team think deployments might be using, so they can find out how many are relying on what
18:49:33 <dansmith> https://docs.openstack.org/nova/latest/user/support-matrix.html
18:49:34 <dansmith> there we go
18:49:40 <noonedeadpunk> as apparently some still might run lxc/hyper-v/etc
18:49:45 <fungi> yeah, that would be a good one to sync up against
18:49:54 <dansmith> for what I think people are using.. kvm on x64 :)
18:50:14 <noonedeadpunk> (and kvm on aarch64)
18:50:33 * gouthamr corrects himself with link: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/QX7TPBPUQWS3R4FYIV7CJFHML6GT2IZP/
18:50:35 <fungi> keeping in mind that some deployments are still on train, so may care about platforms we stopped officially supporting many releases ago
18:50:38 <dansmith> I'll take your word for it, but I haven't seen much evidence
18:50:48 <dansmith> unless it just all works, which I don't believe :)
18:51:12 <noonedeadpunk> yeah, so the reporter was unhappy about missing aarch64 as that's what they were running
18:51:33 <fungi> i'm led to believe that there are public cloud providers offering aarch64 flavors
18:51:34 <noonedeadpunk> and it does work eventually, yes
18:51:57 <fungi> i definitely don't have a list in my back pocket, however ;)
18:52:08 <noonedeadpunk> it's a bit tricky though to prohibit x86 to emulate aarch64 and get scheduled there, but it's a different question
18:53:11 <gouthamr> noonedeadpunk: it could be worth starting an ML discussion regarding this, and copying aprice... adding new releases seems straightforward; but, mayyybe there are other inconsistencies that we need to fix
18:53:30 <noonedeadpunk> well tomorrow is a deadline for the survey anyway...
18:53:31 <gouthamr> don't know if its too late either because it'll mess up the analysis
18:53:33 <gouthamr> yes
18:54:03 <fungi> the survey "deadlines" are more like checkpoints
18:54:06 <noonedeadpunk> just we kinda need to be aware about that for upcoming analysis I guess
18:54:12 <slaweq> for this year's survey it is definitely too late but we should chagne it for next year
18:54:19 <noonedeadpunk> ++
18:54:33 <noonedeadpunk> and acccount for upcoming releases during the year
18:54:47 <noonedeadpunk> even though we might not know name - at least have versioned ones
18:56:49 <slaweq> ++
18:57:04 <spotz[m]> e-dalmatian, f-dalmatian, g-dalmatian...:)
18:57:12 <gouthamr> okay; it looks like we can take an AI to check with aprice about when the 2025 User Survey questions are due
18:57:18 <fungi> the openstack user survey absolutely continues collecting submissions after the deadline, they just end up rolled into the next checkpoint
18:57:39 <noonedeadpunk> good point...
18:58:02 <fungi> but yes, for continuity it's best to batch the updates to questions themselves
18:58:24 <gouthamr> ++
18:58:39 <gouthamr> alright, a couple of mins left, so i want to highlight something else while i still have folks here :)
18:58:39 <fungi> which also reduces the workload on foundation staff maintaining the survey configuration and reporting
18:58:45 <opendevreview> Jon Bernard proposed openstack/election master: Add Jon Bernard candidacy for Cinder PTL  https://review.opendev.org/c/openstack/election/+/927312
18:58:50 <gouthamr> Outreachy call for help
18:58:50 <gouthamr> #link https://www.outreachy.org/blog/2024-08-14/outreachy-needs-your-help/
18:58:50 <gouthamr> #link https://www.outreachy.org/communities/cfp/openstack/
18:59:22 <gouthamr> ^ this is probably the first time in a looooong time that the Open Infra Foundation nor any participting OpenStack sponsors have donated towards an Outreachy internship
18:59:56 <gouthamr> so, i wanted to check if any of you know anyone/company can pitch in
19:00:25 <gouthamr> even if you don't have someone right away, please keep this appeal in mind :)
19:00:29 <spotz[m]> I have not heard back on my request for funding
19:01:13 <gouthamr> Outreachy runs three internship cohorts every year; so if we can swing funding for future ones, we can continue deriving benefits of this great program
19:01:28 <gouthamr> i'd be happy to chat with anyone that needs any info regarding this
19:01:35 <gouthamr> but, we're over time for this meeting
19:01:41 <gouthamr> spotz[m]: thank you for trying!! :)
19:01:46 <gouthamr> thank you all for attending
19:01:52 <gouthamr> see you here next week!
19:01:54 <gouthamr> #endmeeting