Wednesday, 2024-11-13

*** fungi is now known as Guest924901:33
*** kinrui is now known as fungi01:41
*** mhen_ is now known as mhen02:35
opendevreviewXiang Wang proposed openstack/oslo.messaging master: Implement ConsulOperator as a service broker to support HTTP Driver  https://review.opendev.org/c/openstack/oslo.messaging/+/91249903:06
opendevreviewXiang Wang proposed openstack/oslo.messaging master: Add HTTP driver to oslo.messaging.drivers  https://review.opendev.org/c/openstack/oslo.messaging/+/91484003:06
opendevreviewXiang Wang proposed openstack/oslo.messaging master: Implement HTTPListener and HTTPClient and add OpenAPI specs  https://review.opendev.org/c/openstack/oslo.messaging/+/91505603:06
roger_wangHi everyone,  I am currently working on submitting the HTTP-driver patches. I've addressed all the issues mentioned in the comments and would appreciate it if someone could review them again. This will help me move forward with the subsequent patches.  Thank you!04:01
roger_wanghttps://review.opendev.org/c/openstack/oslo.messaging/+/912499/1504:01
roger_wangalso, there is a partch for moving spec to Epoxy: https://review.opendev.org/c/openstack/oslo-specs/+/91395804:02
opendevreviewMerged openstack/oslo-specs master: Move oslo-http driver spec to Epoxy  https://review.opendev.org/c/openstack/oslo-specs/+/91395809:18
tkajinamso we will have the meeting here in 30 minutes, right ?12:32
Damani_hi13:05
tkajinamshall we start ?13:07
Damani_#startmeeting oslo13:07
opendevmeetMeeting started Wed Nov 13 13:07:26 2024 UTC and is due to finish in 60 minutes.  The chair is Damani_. Information about MeetBot at http://wiki.debian.org/MeetBot.13:07
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:07
opendevmeetThe meeting name has been set to 'oslo'13:07
Damani_courtesy ping for hberaud, bnemec, johnsom, redrobot, stephenfin, bcafarel, kgiusti, jungleboyj, gmann, tobias-urdin13:07
Damani_#link https://etherpad.opendev.org/p/epoxy-oslo-meeting-tracking13:08
tkajinamnot sure if that ping list is still up-to-date13:09
Damani_no 13:09
Damani_you're right 13:09
Damani_probably not, but that will be a good way to update the list :)13:09
Damani_#topic Red flags for/from liaisons13:09
Damani_actually i think we can probably jump direct to the open discussion 13:10
Damani_tkajinam, what do you think?13:11
tkajinamI was about to ask what that red flags you will discuss13:11
Damani_no red flags actually 13:11
Damani_so let's jump to the open discussion 13:11
Damani_#topic Open discussion13:11
Damani_about the epoxy-1 releases yes it's a good point and i have started to do code review 13:12
Damani_https://review.opendev.org/q/topic:%22epoxy-milestone-1%22+status:open13:12
tkajinambecause we are at still E-1 we don't have to rush too much to merge things before that release13:12
Damani_tkajinam, about the releases do you have something else do you want to mention?13:12
Damani_yes right 13:13
tkajinambut it's probably a good reminder for us, because we are expected to land big changes earlier than the other projects13:13
tkajinamso if you can check pending items for master, that would be good13:13
Damani_yes i will do it 13:13
Damani_and yes about https://review.opendev.org/c/openstack/releases/+/93446513:14
tkajinamfor antelope as I mentioned in the etherpad we have to check any pending backports to 2023.113:14
Damani_we need to check and do a list of backport we potentially need to do 13:14
tkajinamand also any changes we haven't yet released13:14
tkajinamyeah13:14
Damani_yes 13:14
Damani_that is pretty important 13:15
tkajinamI've been pulled by some "fun" stuffs happening so I'm unsure if I can take time for it13:15
tkajinambut as a few projects already transitioned their stable/2023.1 to unmaintained/* we may need to complete in a few weeks13:15
Damani_i will  do it 13:15
tkajinamI mean "take time for it this week"13:15
tkajinamthx13:15
Damani_maybe i will just ping you sometimes to double check with you 13:16
Damani_if it's ok?13:16
tkajinamyeah I'll respond to it on best effort basis.13:16
Damani_sounds good 13:17
Damani_ok next topic update constraints for oslo.utils https://review.opendev.org/c/openstack/requirements/+/93417613:17
tkajinamthis is just fyi. the bump is currently blocked by os-vif13:18
Damani_ok 13:18
Damani_i see now 13:18
Damani_thanks a lot 13:18
tkajinamwe need https://review.opendev.org/c/openstack/os-vif/+/932436 but os-vif has broken CI now13:18
Damani_yes 13:18
tkajinamfrom oslo's perspective we have nothing we can really do.13:18
Damani_and now i think we can talk about the oslo.service and the proposal removal of eventlet 13:19
Damani_https://review.opendev.org/c/openstack/oslo-specs/+/92750313:20
tkajinamdo you want to set # topic ?13:20
Damani_#topic oslo.service proposal removal of eventlet13:20
tkajinam(by the way, for next time, we can fist discuss the agenda item to prioritize these and then move to open discussions13:21
Damani_https://review.opendev.org/c/openstack/oslo-specs/+/92750313:21
Damani_tkajinam, yes right sorry for that 13:21
tkajinamnp13:21
Damani_in will dom that for next time 13:21
Damani_tkajinam, did you have take a look?13:22
opendevreviewTakashi Kajinami proposed openstack/oslo-specs master: oslo.service: Propose a plan to Remove Eventlet  https://review.opendev.org/c/openstack/oslo-specs/+/92750313:23
Damani_hberaud, are you around?13:23
tkajinamI've not yet go through the latest version but will do. I don't have any objections about the whole direction so my comments (if I have any) may be trivial one we can address in follow-up13:24
tkajinamI'm more curious to know the implementation side. I've seen a few patches to deprecate eventlet things but I've not yet seen any core change to implement the core switch mechanism.13:25
Damani_so in olso.service the idea is to use cotyledon, futurist and thread13:26
Damani_we just need to add also a new backend system and as mentionned in a comment need to structure and manage import in a runtime level 13:27
Damani_for me that seems good and i think the patch https://review.opendev.org/c/openstack/oslo-specs/+/927503/8/specs/epoxy/remove-eventlet-from-oslo-service.rst13:28
Damani_can be merge 13:28
Damani_but i don't know if someone have objections about it 13:29
tkajinamproject wide feedback may be gathered by the separate SIG meeting. because it's not feasible to gather opinions everyone involved with I'd suggest time box approach13:31
tkajinamI mean set the deadline 13:31
Damani_ok 13:33
Damani_you mean for the specs or for the implementation?13:33
Damani_deadline for the specs i think it will be great if we have a decision and merge for next week 13:35
tkajinamboth13:35
tkajinambut for now, I'm basically talking about that spec13:35
Damani_i can send a mail to ask new code review and feedback 13:35
Damani_i will send a mail today about that 13:36
Damani_thanks a lot 13:36
Damani_do you something else you want mention about that topic?13:36
tkajinamnothing else today13:37
Damani_ok 13:37
Damani_just a last thing i forget about epoxy, i have proposed a patch in releases to update the schedule for oslo https://review.opendev.org/c/openstack/releases/+/93464213:38
Damani_tkajinam, hberaud, if you can take a look please :)13:38
tkajinamok13:38
Damani_thanks a lot 13:39
Damani_so if you have nothing else i proposed to end the meeting for today 13:39
Damani_tkajinam, thanks a lot for your time and participation 13:39
Damani_#endmeeting13:40
opendevmeetMeeting ended Wed Nov 13 13:40:02 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:40
opendevmeetMinutes:        https://meetings.opendev.org/meetings/oslo/2024/oslo.2024-11-13-13.07.html13:40
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/oslo/2024/oslo.2024-11-13-13.07.txt13:40
opendevmeetLog:            https://meetings.opendev.org/meetings/oslo/2024/oslo.2024-11-13-13.07.log.html13:40
elodillesDamani_: quick comment for the finalr release before stable/2023.1 transition to unmaintained/2023.1. basically we want to do that in 1-2 days and was advertised multiple times in the cycle, so please do not start now backporting things, it's too late for that already13:43
Damani_elodilles, ok 13:43
Damani_thanks a lot for the mention 13:44
elodillesnote that it is possible to backport to unmaintained/2023.1 after it is cut, just it won't be possible to create upstream releases out of it13:44
Damani_ok 13:44
elodillesnp13:44
Damani_i think it's a good stuff to have back that meeting :)13:45
Damani_to have this type of mention for example 13:45
Damani_elodilles, do you want to be on the ping list for that meeting?13:46
elodillesyepp, meetings are good to discuss things + people can read the logs as well13:46
Damani_yes '13:46
elodillesDamani_: not particularly, but i'll might read the logs time to time o:)13:46
Damani_ok sounds good 13:46
elodillesnote that i haven't found any relevant *open* or *merged but not released* Oslo change when i composed this mail: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/UDQAC7SR5JAQJE5WBAG54A2MTBVBTJ44/#R3VK6KV23RNVBHTZROXKMAUMT5C7V6SW13:49
elodillesthat is why i haven't added Oslo in the list13:49
opendevreviewTakashi Kajinami proposed openstack/oslo.messaging master: Remove deprecated AMQP1 driver  https://review.opendev.org/c/openstack/oslo.messaging/+/93411613:49
elodilles(it is possible that i missed something, but hopefully i was right o:))13:50
opendevreviewTakashi Kajinami proposed openstack/oslo.messaging master: Remove deprecated AMQP1 driver  https://review.opendev.org/c/openstack/oslo.messaging/+/93411613:53
opendevreviewDaniel Bengtsson proposed openstack/oslo.messaging master: Remove deprecated AMQP1 driver  https://review.opendev.org/c/openstack/oslo.messaging/+/93411614:13
johnsomHi Oslo team. The meeting time is a bit early for me (5am), but please leave me on the ping list as a reminder to read the scroll back. thanks!18:04
*** tkajinam is now known as Guest933822:33

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