Tuesday, 2024-05-07

gouthamrgmann: the srbac goal-update seems like a good one to merge; i thought about asking for more votes.. but i changed my mind re-reading the house rules.. 17:55
gouthamri workflowed it now17:55
gouthamrJayF++ gmann++ "tox -e check-review-status" is a real powerful specter :D 17:56
JayFyeah, setting topic on governance changes is important for that :D 17:57
gouthamrtrue17:57
gmanngouthamr: ++17:59
gmannyeah this script is really helpful 17:59
gouthamr#startmeeting tc18:00
opendevmeetMeeting started Tue May  7 18:00:39 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
noonedeadpunko\18:00
gouthamr#topic Rollcall18:01
gmanno/18:01
dansmitho/18:01
noonedeadpunkI forgot to mark myself as out today, but on openinfra Sweden event, so really more out then it18:01
gouthamrack noonedeadpunk 18:02
gouthamrthis meeting is happening simultaneously on Zoom18:02
gouthamr#link https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09 18:02
slaweqo/18:02
JayFo/18:03
gouthamrcourtesy ping: spotz[m] frickler 18:04
gouthamrgtema18:04
gtemaO/18:05
gouthamr#topic DPL model improvement proposals and TC Liaisons 18:05
gouthamr#link https://review.opendev.org/c/openstack/governance/+/916822 (Move DPL model into doc)18:05
gmanngtema: today is video call #link  https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz0918:05
gouthamr#link https://review.opendev.org/c/openstack/governance/+/916833 (Add DPL model & liaison reset policy)18:05
gouthamr#link https://review.opendev.org/c/openstack/governance/+/917516 (TC liaisons for requirements, release management and ; freezer is the fourth)18:05
gtemaRight, forgot about video, will join in a min18:06
gouthamrgmann is presenting the idea behind https://review.opendev.org/c/openstack/governance/+/916833  and https://review.opendev.org/c/openstack/governance/+/91751618:06
gouthamrwe're not in a hurry to merge this18:08
gouthamrbut we're interested to know if there are any major disagreements18:08
gouthamrplease add your comments to these gerrit changes18:08
gouthamrtkajinam brought up the concern that the initial DPL model proposal suggests that the model is suggested for low activity projects18:09
gouthamrJayF suggested we change the language to clarify this18:10
gouthamrwe're suggesting spreading the load for the TC liaisons for the DPL projects 18:11
gouthamrtc-members please feel free to claim any projects you'd wish18:11
gouthamrgtema is seeking if we have a written procedure to know when a project is active/not18:12
JayF#link https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html18:12
JayFI think this is it? gtema 18:12
gouthamrJayF++18:12
gouthamrproject meetings aren't a strict requirement to judge an active project... 18:13
gouthamrbut a holistic/subjective approach that works instead to judge a project's activity/inactivity seems to warrant a TC liaison's judgement18:14
gouthamr(or the TC's judgement in case of PTL model projects)18:14
slaweqhelper script which may give some data about project's health: https://github.com/openstack/governance/blob/master/tools/project_stats_check.py18:15
gouthamrits really hard to automate this sort of thing18:15
JayFgiven how projects in openstack are mature enough to be mostly "done", it's hard to use statistics alone to measure project activity18:16
gouthamrgtema says project users/operators need to know which projects are active18:17
gouthamrJayF brought this up at the TC PTG18:18
gouthamr#link https://etherpad.opendev.org/p/apr2024-ptg-os-tc (TC PTG etherpad)18:18
gouthamrthere was no conclusion to make a proposal18:19
gouthamrcan we break up the problem to make a proposal - for example, if the security concerns are at the top of our mind, can we have a proposal just isolating the security requirements for projects18:21
gouthamrwe'd need to change the project requirements to accommodate this18:21
gouthamrthe security-sig and VMT has less volunteers though; so we'd need to do this simultaneously by growing the security-sig/VMT18:22
gouthamrwill a yellow/green/red marking on our existing project list help? in addition to having https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html and 18:22
JayF(I said) We have a limited amount of resources, any approach would have to acknowledge that and use prioritization rather than just adding additional requirements18:23
gouthamrslaweq suggests adding a badge in repo18:23
gouthamrpeople are discovering projects using multiple sources: project documentation, project navigator, git repositories18:24
opendevreviewMerged openstack/governance master: Move openstack/kuryr and openstack/kuryr-libnetwork to Zun  https://review.opendev.org/c/openstack/governance/+/91751718:24
opendevreviewMerged openstack/governance master: Add timeline to remove enforce_scope in RBAC goal  https://review.opendev.org/c/openstack/governance/+/91517918:24
gouthamrgmann brought up the "openstack map" would also need to accommodate this18:24
gouthamr#link https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c087f27a43eea/www-assets-prod/openstack-map/openstack-map-v20240401.pdf (current "openstack landscape" or map18:25
gouthamr#action gtema will make a proposal to the governance repo regarding tagging inactive projects more prominently 18:26
gouthamr#topic Next steps on PyPi Maintainers cleanup (gmann)18:27
gouthamrthe existing state is recorded in this etherpad18:27
gouthamr#link https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup (Notes on PyPi maintainership of OpenStack packages)18:27
gouthamrwe've to break the package list into two: one where openstack-ci is a co-maintainer/owner; and other where openstack-ci doesn't figure in the maintainers list18:28
gouthamr#action gouthamr will work on this list18:29
gouthamr#topic 2024.2 TC Tracker 18:31
gouthamr#link https://etherpad.opendev.org/p/tc-2024.2-tracker (Technical Committee activity tracker)18:31
gouthamrwe discussed items that needed more TC review atm18:34
gouthamrre: dropping eventlet vs replacing eventlet with asyncio18:34
gouthamr#link https://review.opendev.org/c/openstack/governance/+/902585 (Migrate eventlet usages to asyncio)18:35
gouthamr#link https://review.opendev.org/c/openstack/governance/+/916546 (Goal: Remove eventlet requirements from shared libraries)18:35
gouthamr#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/PY6NUNYFU63XOIZHDDBONJDHRXJMZF5J/ ([all][oslo][neutron][glance][ironic] Deprecating eventlet based WSGI server)18:35
gouthamrprojects seem to be concerned that the big leap from eventlet to asyncio needs to be figured out via https://review.opendev.org/c/openstack/governance/+/902585 18:37
gouthamrand we may be impeding individual project progress18:37
gouthamrJayF suggests that we should clarify that the TC doesn't stand in the way of projects exploring options to replace eventlet18:38
gouthamrwe're not going to have a one-size-fits-all solution18:38
gouthamrJayF suggests communicating this to the ML is required now18:39
gouthamr^ this seems like a general consensus in the TC18:43
gouthamrhberaud ^ 18:44
gouthamrwe'd continue chatting on the gerrit change.. 18:44
JayFI will take an action to chat with hberaud and try to find a soft landing for that proposal and communicate that to the larger community (via gerrit/ML)18:47
gouthamr#topic Open Discussion 18:49
gouthamrJayF++18:49
gouthamrwhy does devstack take a longer time on zuul jobs vs github actions18:50
gouthamrclarkb brought this up multiple times in the past18:51
gouthamr#link https://review.opendev.org/c/openstack/devstack/+/676016 (OSC as a service on devstack) 18:53
gouthamr^ this proposal is ancient in our release timeline18:53
gouthamrthe underlying issue seems to be the token caching 18:54
gouthamrin OSC18:54
gouthamrthank you all for joining!18:59
gouthamrlets catch up here in a week! 18:59
gouthamr#endmeeting18:59
opendevmeetMeeting ended Tue May  7 18:59:57 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-07-18.00.html18:59
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-07-18.00.txt18:59
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-07-18.00.log.html18:59
clarkbgtema: https://zuul.opendev.org/t/openstack/build/3b50d468adfb4946adc28f3ca8e8b145/log/controller/logs/devstacklog.txt#21104-21120 is the recorded timing output19:04
clarkbosc is the largest time block and announted time is actually pretty small now. Thats nice19:04
clarkbthe runtime there was closer to 20 minutes than 40 fwiw19:05
clarkbso half not a quarter. But still pretty bad19:05
clarkbthough maybe need to cross check against the wall clock on the job too19:05
gtemaclarkb: on GH from what I see osc is half of that (239s), but also pip_install is half of the time19:06
clarkb17:10:46.019046 is roughly when devstack stack.sh starts and 17:29:53.817236 is when it ends so that accounting seems to be rouhgly accurate with the wall clock too19:10
clarkbgtema: another thing to keep in mind is if you have tempest disabled that prevents a lot of tempest setup from running which may speed your jobs up19:10
gtemaright19:10
clarkbgtema: re python startup costs I think one of the things that made it so insidious is that everyone running python on their laptops never really noticed since they likely have small numbers of packages installed into a venv on an ssd or nvme drive. But when you get to clouds with metered iops it is really apparent. I also did comparisons between spinning drives and ssds back19:18
clarkbwhen and that was very noticeable too19:18
clarkbbut it gets worse the more stuff you have installed and teh more versions you have installed beacuse pkg_resources/importlib also sort all the packages and their versions in addition to the filesystem scan19:18
gtemaClarkb, I perfectly know that since I was investigating and tracing this heavily. Actually because of that I more or less gave up with the current OSC/SDK in py and decided to focus on rust19:24
gtemaIt's not repairable without huge redesign, but in that case it makes no sense to stick to py (for me personally)19:25
clarkbto be fair its repairable in the same way as an implementation in most other languages though: don't use dynamic plugin loading and install all the code upfront19:26
gtemaA pure "import openatack" is already taking 0.9sec on my desktop 19:26
clarkbyes python will still be generally slow, but a big part of startup cost would be removed that way19:26
gtemaBig - yes. But I am still not convinced in performance of py19:27
spotz[m]Sorry all! In a different time zone and missed joining19:55
gouthamrspotz[m]: np; i didn't mark absence in the official meeting note; but dansmith mentioned that you're at the RH summit20:04
dansmith*mentioned that he thought she said she was...at summit21:13
spotz[m]I put it in channel before I left so he spoke fact.:) I was OpenStacking:)21:42
* gouthamr missed it21:43

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