15:00:05 <gmann> #startmeeting tc
15:00:05 <opendevmeet> Meeting started Thu Jun 16 15:00:05 2022 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:06 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:06 <opendevmeet> The meeting name has been set to 'tc'
15:00:13 <gmann> tc-members: meeting time
15:00:18 <gmann> #topic Roll call
15:00:20 <gmann> o/
15:01:33 <jungleboyj> o/
15:03:04 <rosmaita> o/
15:03:08 <gmann> slaweq informed that he will not attend as holiday in Poland
15:03:27 <knikolla> o/
15:03:33 <gmann> dansmith also informed that he might not attend as he has medical commitment
15:04:15 <gmann> spotz: diablo_rojo_phone arne_wiebalck are you attending?
15:06:26 <gmann> anyways let's start. we do not have quorum but that is fine and we will not have any formal voting in this meeting.
15:06:32 <gmann> #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting
15:06:35 <gmann> today agenda ^^
15:06:47 <gmann> #topic Follow up on past action items
15:06:54 <gmann> slaweq to report bug for fedora job failure
15:07:10 <gmann> I think fedora job worked as dansmith tested that so no need for bug?
15:08:04 <arne_wiebalck> sorry o/
15:08:23 <gmann> devstack platform job is passing and failing but not sure what is failure #link https://zuul.openstack.org/builds?job_name=devstack-platform-fedora-latest&skip=0
15:08:29 <gmann> arne_wiebalck: hi, np!
15:08:44 <gmann> will check with them if anything needed on this Action item
15:08:54 <gmann> #topic Gate health check
15:09:02 <gmann> what's news on gate?
15:09:18 <gmann> I have not seen any frequent failure in master gate this week
15:09:25 <rosmaita> \o/
15:10:23 <jungleboyj> woo hoo.
15:10:32 <gmann> (rosmaita) update on cinder-backup memory bloat issue
15:10:38 <gmann> rosmaita: please go ahead on this
15:10:53 <rosmaita> Gorka was looking into this and thinks he may have a fix
15:11:00 <rosmaita> https://review.opendev.org/c/openstack/devstack/+/845805
15:11:02 <gmann> #link https://review.opendev.org/c/openstack/devstack/+/845805
15:11:13 <gmann> #link https://review.opendev.org/c/openstack/cinder/+/845806
15:11:21 <rosmaita> he was talking with dansmith in either -cinder or -qa yesterday
15:11:45 <rosmaita> the change affects all devstack services, so he's going to look further at performance
15:12:07 <rosmaita> because it seems to work well for cinder backup and shouldn't hurt anyone else
15:12:13 <rosmaita> but we do need to be sure
15:12:39 <rosmaita> there's also a cinder patch, but it only affects about 30 MB of memory
15:12:55 <rosmaita> the big one is the devstack patch which changes malloc settings
15:12:57 <gmann> nice, I think it should be visible in performance.json file too ?
15:13:12 <gmann> I mean the improvement should be visible in that file
15:13:17 <rosmaita> yes, dansmith told him about that and Gorka's looking into it
15:13:22 <gmann> +1
15:13:38 <rosmaita> that's all
15:14:11 <gmann> thanks rosmaita for updates and thanks to Gorka for fixing this. it will be a great improvement.
15:14:23 <rosmaita> we are hopeful!
15:14:37 <gmann> any other news on gate? including stable branch gate ?
15:15:29 <gmann> #topic New ELK service dashboard: e-r service
15:15:45 <gmann> I think dpawlik  is also on holiday as slaweq mentioned
15:15:58 <gmann> so skipping this topic unless anyone else have any updates on this?
15:16:54 <gmann> #topic RBAC feedback in ops meetup
15:17:21 <gmann> we have feedback and these are few etherpads where feedback is there from ops meetup or forum sessions
15:17:29 <gmann> #link https://etherpad.opendev.org/p/BER-2022-OPS-SRBAC
15:17:36 <gmann> #link https://etherpad.opendev.org/p/deprivilization-of-service-accounts
15:17:43 <gmann> #link https://etherpad.opendev.org/p/rbac-operator-feedback
15:18:07 <gmann> I was hoping to have the last etherpad as central one to collect from everywhere but no big deal
15:18:21 <spotz> o/ Sorry I'm late
15:18:32 <gmann> from ops meetup, it seems clear that system scope are not a popular things anyone require at this stage at least
15:18:55 <gmann> this line make it clear  #link https://etherpad.opendev.org/p/BER-2022-OPS-SRBAC#L47
15:19:17 <rosmaita> that is useful info
15:19:30 <rosmaita> lines 37-38 are also interesting
15:20:25 <gmann> yeah
15:21:09 <gmann> I am not surprise that operators do not understand scope things even sometime we as developers also do not :)
15:21:20 <gmann> but anyways this is very useful feedback
15:21:26 <gmann> next plan is 1. I will compose all the feedback in central etherpad 2. schedule policy popup meeting on next Tuesday (21st) 3. decide the next direction based on feedback in meeting 4. update goal document and projects on agreed direction
15:21:32 <fungi> and i still see a lot of references to "admin" in there, which should ideally only be by way of analogy for the new rbac model
15:22:14 <fungi> given the desire to eradicate the string "admin" from default role names
15:22:20 <gmann> fungi: yes, global admin is something most of operator want. that is what few NVF operatror also mentioned
15:22:57 <gmann> I will do the 1st and 2nd today and let's discuss in tuesday RBAC call
15:23:43 <gmann> anything else on RBAC topic?
15:23:50 <fungi> i would say "global admin" is how they were referring to what they want, but it's not what we would name it
15:24:07 <fungi> due to the baggage and confusion around what "admin" means
15:25:13 <gmann> fungi: yeah naming is one part but it seems like "admin (someone whatever name is) able to do everything is their requirement" and that is what we wanted to avoid in new SRBAC
15:25:48 <gmann> by introducing the scope but anyways we should ship what operator need than what developer think it can be useful for them
15:25:59 <gmann> s/them/operator
15:27:08 <gmann> moving next?
15:27:38 <gmann> #topic TC + Board meeting
15:27:47 <gmann> #link https://docs.google.com/presentation/d/1yCiZy_9A6hURXD0BRdr33OlK7Ugch5EgSvFzL-jvDIg/edit#slide=id.g129c4257ac3_0_1456
15:28:15 <gmann> I virtually presented the 'OpenStack Updates' in berlin board meeing
15:28:43 <jungleboyj> gmann:  Thank you for doing that!
15:29:50 <gmann> initially, there was a delay in zoom setup but really appreciate foundation, Jonathan, berlin venue guys to make it work.
15:29:56 <gmann> but later it went well
15:30:07 <jungleboyj> Good!
15:30:23 <gmann> I am glad that board liked the presentation and the content.
15:30:31 <rosmaita> nice
15:30:54 <gmann> and happy to know about the status and challenges we are facing in OpenStack.
15:31:09 <jungleboyj> That is good.
15:31:40 <gmann> this kind of communication was missing for last couple of years due to COVID or so and it is nice to have such updates from projects
15:32:34 <gmann> there was discussions on OpenStack Challenges especially on diversity, fewer contributors slides
15:33:12 <gmann> there was no solution discussion about those but at least board ack this and agreed to solve this in some way. which is what our main motive for these updates were
15:34:59 <gmann> and on the same note, I shared the idea of starting an "Open Infra project interaction" group under board to have such regular checks/updates on each Open Infra project, not just OpenStack. Board agree to start it and we have a few volunteers also. I will communicate it on ML sometime next week.
15:35:51 <gmann> that is overall updates from board meeting.
15:36:58 <gmann> anything else on this or any query?
15:37:21 <rosmaita> nope, thanks for doing the presentation
15:37:58 <spotz> Thanks gmann
15:37:59 <gmann> np!, hoping next time we all can attend in-person
15:38:04 <jungleboyj> ++
15:38:37 <gmann> #topic Open Reviews
15:38:55 <gmann> let's discuss rosmaita item first before I check the open reviews things
15:38:56 <gmann> (rosmaita) quick update on SLURP Release Notes
15:39:02 <gmann> rosmaita: go ahead pleae
15:39:04 <gmann> please
15:39:10 <rosmaita> sure
15:39:36 <rosmaita> i got some good feedback on the patch
15:39:45 <rosmaita> #link https://review.opendev.org/c/openstack/project-team-guide/+/843457
15:39:57 <rosmaita> I have a -W on it while i work on an update
15:40:09 <rosmaita> though i have been working on other stuff
15:40:20 <rosmaita> I have some ideas that I think could automate a version of the manual procedure outlined in the current patch without requiring any reno changes, but I haven't had time to test them yet
15:40:30 <gmann> great
15:40:37 <rosmaita> and i am kind of back-burnering this because it doesn't need to be settled until M-3 of 2023.1 (though my goal is to have it worked out before M-3 of Zed)
15:40:57 <gmann> yeah, we have time on this
15:41:03 <rosmaita> it's shown up on the past few gmann update emails, so i figured i should say what the status is
15:41:28 <rosmaita> that's all from me
15:41:59 <gmann> thanks rosmaita for updates and working on that. zed m-3 or before 2023.1 start it is fine.
15:42:05 <rosmaita> ok, cool
15:42:24 <gmann> on open review
15:42:40 <gmann> slaweq: updated this patch, please review/add your vote #link https://review.opendev.org/c/openstack/governance/+/839880
15:43:26 <gmann> and we need one mroe vote in this charter change #link https://review.opendev.org/c/openstack/governance/+/844882
15:43:54 <gmann> I think jungleboyj arne_wiebalck ^^ you can add your vote
15:43:59 <gmann> other are done already
15:44:08 <jungleboyj> Looking.
15:44:12 <gmann> thanks
15:44:14 <gmann> that is all from me today
15:44:29 <gmann> anything else to discuss from anyone?
15:45:17 <gmann> if nothing else let's close the meeting.
15:45:23 <gmann> Thanks everyone for joining.
15:45:30 <gmann> #endmeeting