18:00:27 #startmeeting tc 18:00:27 Meeting started Tue Jul 2 18:00:27 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:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:27 The meeting name has been set to 'tc' 18:01:20 #info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the OpenStack TC youtube channel, where the recording will be uploaded soon. 18:01:33 #link https://www.youtube.com/channel/UCBuGwBXOmWHydSE09RM84wQ 18:01:39 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:45 Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee 18:01:51 #topic Roll Call 18:01:53 o/ 18:02:01 o/ 18:03:15 * gouthamr notes that slaweq gtema spotz[m] are on the Zoom call 18:03:30 #link https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09 18:03:38 ^ link to the Zoom call in case you need it 18:03:50 noted absence: dansmith 18:03:57 note you may want to undo that if zoom bombing is still an issue (though I guess regular meeting logs are also posted so meh) 18:04:15 :P 18:04:17 yes 18:04:25 #undo 18:04:25 Removing item from minutes: #link https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09 18:04:30 I put that on the ML once not realizing and it didn't become an issue. 18:04:38 ++ 18:04:44 Probably wise to have opsec but no little actual benefit at this point in time [knock on wood] 18:04:57 courtesy ping noonedeadpunk 18:05:19 now that everyone isn't stuck at home the novelty/fun/entertainment in disrupting online communications has gone away 18:05:53 Dan noted prior to the meeting start that he is out, working on today's recent OSSA (just putting this into the minutes) 18:06:30 #topic Action Items from past weej 18:06:32 #topic Action Items from past weej#undo 18:06:35 #undo 18:06:35 Removing item from minutes: #topic Action Items from past weej#undo 18:06:40 #topic Action Items from past week 18:07:10 Following up on projects in the "inactive" state 18:07:40 freezer is looking to remain in the "inactive" project list through this cycle 18:07:54 gmann: we're looking for a formal vote, but doesn't have to happen on gerrit 18:08:28 JayF mentioned that decisions made in meetings upset community members 18:09:02 We had a specific complaint a couple of PTGs ago about people worried we made decisions in meetings. Our response was all official decisions are made async, in gerrit. 18:09:06 I'd like us to keep that pattern. 18:09:19 +1 18:10:10 gmann suggests that noonedeadpunk can create a gerrit change to annotate the inactive project list with the 2024.1 release 18:11:18 JayF gtema and gmann would like to reflect the data in a more formal way: projects.yaml and project documentation 18:11:35 I suggest putting project inactivity in reference/projects.yaml, noting each release it was inactive similar to how we note each release we nominate a ptl. 18:12:38 spotz[m] asked if the objection from the community around voting was because we weren't recording the vote formally via Meetbot's voting process 18:13:11 JayF mentioned that wasn't the case; the problem was with folks in different timezones wouldn't be able to meaningfully participate 18:13:38 wrt monasca, gmann will respond to thuvh's IRC question on the ML 18:13:43 This was an issue brought up by the community a couple of PTGs ago, I believe it was the one at the beginning of my time as Chair, or maybe my first as vice-Chair 18:13:52 re: meeting votes v gerrit votes 18:17:08 regarding Skyline leaving the "emerging" projects list, we'd like the PTL/core team propose a gerrit change to remove the project from that list 18:17:27 we are asking if anyone in the TC disagrees with giving skyline folks more time to propose this change 18:18:42 #agreed we'll give the Skyline team more time to work with us to remove the project from the emerging projects list 18:18:59 #topic Remove eventlet from OpenStack (hberaud / zzzeek) 18:19:36 #link https://review.opendev.org/c/openstack/governance/+/902585/ (Goal Proposal: Remove eventlet from OpenStack) 18:20:07 this goal defines the problem - the patterns of eventlet's use in OpenStack for folks interested to learn why this is a problem 18:21:49 the goal also proposes a plan for project teams to follow to replace the use of eventlet 18:23:32 zzzeek has been the maintainer of sqlalchemy, and most OpenStack projects use it.. 18:24:17 also is a fairly prolific openstack contributor in his own right, fwiw 18:25:07 he's looking to show how sqlalchemy uses asyncio today so we can see examples/pattern to follow 18:25:22 he's currently sharing a presentation, we'll grab you a link 18:25:49 it'll start in the video about 20-25 minutes in, too, which is helpful 18:25:58 not sure these slides are that useful without Mike's context 18:26:04 true 18:28:12 we're currently going through how eventlet's monkeypatching achieves nonblocking I/O 18:31:54 sqlalchemy was tasked to adding a asyncio frontend, but zzzeek wasn't keen on rewriting the whole front end to be asyncio specific.. so sqlalchemy's approach is to use an abstraction that allows both sync and async sections 18:32:38 #link https://awaitlet.sqlalchemy.org/en/latest/ (a library that allows non-async defs that invoke awaitables inside of asyncio application) 18:33:14 this approach is also present in a library called "greenback", but zzzeek found it was complicated 18:34:07 #link https://review.opendev.org/c/openstack/oslo.db/+/922976 asyncio enginefacade for oslo.db, also on the slides in the meeting 18:34:13 ty JayF 18:34:22 Will that work if I'm not chair? 18:34:26 yes 18:34:28 nice 18:39:16 JayF is asking if zzzeek is experimenting with using the oslo.db Asyncio Facade with any OpenStack service 18:41:16 zzzeek has looked at a few services; some services may want to use this asyncio db facade - there are examples in the docs.. there are some other services, like Swift that seem to use eventlet in a different way 18:43:29 I also asked if it's useful as a migration tool, and it sounded like the answer is yes, it mainly exists to let asyncio-native and non-asyncio-native code to live together in the same python module 18:43:53 #link https://awaitlet.sqlalchemy.org/ 18:44:09 #link https://github.com/zzzeek/async_demo/ 18:44:15 zeek's async demo ^^^^ 18:46:21 +1 ty zzzeek 18:46:23 zzzeek+++ I appreciate having technical presentations in the TC video meeting. IDK if this used to be a common thing, but this has been great. Thank you! 18:46:33 ++ 18:46:37 great 18:49:01 we're discussing timelines and suggestions on how to get people involved across the community 18:49:28 should the specification include a timeline? 18:49:38 #link https://docs.google.com/presentation/d/169Bc_Uhv-L-0HzM6WuE6uBsC-1hIlgCOQ4lRAAapv1M/edit?usp=sharing 18:49:58 ^^ ++ perfect; thanks zzzeek 18:50:55 JayF recommends us to timebox the spec reviews 18:54:01 I'd note the spec in question 18:54:03 #link https://review.opendev.org/c/openstack/governance/+/902585 18:54:14 Was filed Dec 4, 2023. It's been in review for seven months. 18:56:25 gmann was concerned that the goal wasn't exactly clear - it reflects our need for options as opposed to a specific technology.. so people may be left confused on wht to do, how and when 18:56:45 JayF is concerned about getting any nergative feedback in there in a time boxed manner 18:56:48 I clarified that my intention in suggesting a deadline was more around ensuring all TC members had refelected their opinions with review comments and votes 18:57:00 so that we don't have those folks continuing to be in limbo for more months 18:57:21 * gouthamr how are you typing without putting your hands on your keyboard 18:58:22 we are nearly at the hour 18:58:40 thanks everyone! 18:58:42 and so we decided to keep on the topic; and kept the room open for any other questions/concerns regarding $topic 18:58:44 thanks o/ 18:59:10 we just hopped off the video call; thank you all for joining.. and for the productive discussion 18:59:44 we'll summarize this; and we can brainstorm the timeline.. and tc-members will get my nag on the reviews :) 18:59:56 until next week for this meeting! 19:00:04 hberaud++ zzzeek++ 19:00:07 #endmeeting