15:00:09 #startmeeting openstack-eventlet-removal 15:00:09 Meeting started Tue Mar 4 15:00:09 2025 UTC and is due to finish in 60 minutes. The chair is hberaud[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:09 The meeting name has been set to 'openstack_eventlet_removal' 15:00:24 Ping list: amorin, JayF, gouthamr, ralonsoh 15:00:39 https://etherpad.opendev.org/p/epoxy-eventlet-tracking 15:00:40 pong 15:00:50 let 15:02:11 waiting 1 or 2 min for folks 15:03:12 #topic feature freeze 15:03:14 so 15:03:26 hello 15:03:50 we just passed the feature freeze, and final epoxy is one 1 month 15:04:39 from the point of oslo, all the deprecations are in place, we are just waiting for a RFE https://review.opendev.org/c/openstack/releases/+/942904 15:04:50 how are your deliverables at this point? 15:05:18 Neutron is not ready, there missing agents 15:05:22 s/is in one/ 15:06:09 Do you have an estimate of the remaining work? 15:06:20 (to complete the migration) 15:06:42 that will be ready, for sure, in F. We are expecting the oslo.service release without eventlet 15:07:28 the second part of the oslo.service migration will be shipped with F 15:07:39 that's too late for epoxy 15:08:01 and we are waiting for the patches to start our reviews 15:08:14 just to be sure, was it expected to deliver all the projects without eventlet in Epoxy? 15:08:37 no no :) 15:08:42 ahhhh uffff 15:08:55 it wouldn't have been possible 15:09:14 I think we are in a pretty good shape 15:09:28 mistral is almost ready, still some eventlet in tests, oslo.services, coordination, stuff like this 15:09:44 I'd not have expected that amount of things done 15:10:02 that's awesome 15:10:41 some of them will disappear during F cycle, because I deprecated them in E 15:10:49 excellent 15:11:10 #topic PTG preparation 15:11:31 We are currently scheduling and preparing the PTG 15:11:51 I think we will at least propose I cross session 15:12:31 what projects in particular? 15:12:36 that would be nice to have status on each projects, but also on cross-projects, like oslo stuff 15:12:48 I'd suggest to you to start thinking about it and if you identify topics that you want to share with us, then, I'll share an etherpad with you 15:13:02 ack, I take note 15:13:48 I'll ask my oslo teammates to see if they plan to schedule a PTG session for oslo 15:13:56 that would also be nice to share tips and tricks proejcts were using to get rid of eventlet 15:14:22 sometimes I am wondering how neutron/nova does the work, to avoid reinventing the wheel on mistral project 15:14:23 ralonsoh: all projects are welcome 15:14:41 amorin: good idea 15:15:02 like, the wiki page was good, but more oriented to async IO 15:15:14 which is not possible in most project for now I believe 15:15:47 talking about this: https://wiki.openstack.org/wiki/Eventlet-removal 15:16:12 After some discussion with Designate folks to give them some entry points, I recently wrote a tiny document, which is more a collection of how to split your work etc... maybe it can fit well with this kind of tricks 15:16:27 yeah aboslutely 15:18:00 in all the case I'll communicate you soon all the details about PTG 15:18:43 ack 15:19:04 Do you plan to schedule eventlet specific session to eventlet for your deliverables? 15:19:27 for sure there will be 15:19:36 I need to ask for it to my PTL 15:19:37 If yes, then let me know. This way I'll update the wiki with the various dates and places 15:19:47 thank you 15:19:51 I'll tell you as soon as I have this info 15:19:58 thank you 15:20:38 nothing will happen on mistral side on PTG 15:20:50 ack 15:21:20 #topic final release candidate deadline 15:22:12 RC1 starts next week, and final release candidates deadline is March 27 15:22:50 so, if some of your deliverables (neutron by example) are rc deliverables, then you still have some time left 15:23:14 I think the same is true for mistal IIRC 15:23:37 how is it triggered? 15:24:02 what? The building of rc releases? 15:24:15 yup 15:24:30 those are convenience patches from the release teama 15:24:42 they are automatically generated 15:24:51 ok, perfect, nothing to do on project side for this 15:24:57 you just have to validate them 15:24:59 execpt having green CI / ready code 15:25:07 yes 15:25:58 and sometimes, you might request a RC2 if you observe a last minute bugs 15:26:37 but even RC2 are more or less convenience patches 15:27:22 you just have to keep an eye on proposed releases https://review.opendev.org/q/project:openstack/releases+status:open 15:28:48 patches should be labeled with topic epoxy-rc1-deadline: https://review.opendev.org/q/topic:%22epoxy-rc1-deadline%22 15:29:17 (not yet fulfilled) 15:30:02 #topic Open Discussion 15:30:12 Anything else that you want to discuss today? 15:30:16 all good 15:30:36 ralonsoh: I'll check your reproducer by tomorrow 15:30:42 thanks! 15:32:32 Then, I think we are done 15:32:39 thanks everyone for joining 15:32:52 see you in 2 weeks https://etherpad.opendev.org/p/epoxy-eventlet-tracking 15:32:57 #endmeeting