| opendevreview | Takashi Natsume proposed openstack/oslo.service master: Fix misuse of assertTrue https://review.opendev.org/c/openstack/oslo.service/+/855367 | 01:12 |
|---|---|---|
| opendevreview | Merged openstack/futurist stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/futurist/+/855921 | 08:43 |
| opendevreview | Takashi Natsume proposed openstack/oslo.db master: Fix misuse of assert_has_calls https://review.opendev.org/c/openstack/oslo.db/+/858264 | 09:12 |
| -opendevstatus- NOTICE: As of the weekend, Zuul only supports queue declarations at the project level; if expected jobs aren't running, see this announcement: https://lists.opendev.org/pipermail/service-announce/2022-September/000044.html | 13:38 | |
| peorj | okay, time for the meeting | 15:01 |
| tobias-urdin6 | o/ | 15:01 |
| tobias-urdin6 | nice | 15:01 |
| hberaud | o/ | 15:02 |
| felixhuettner[m] | o/ | 15:02 |
| peorj | hi | 15:02 |
| peorj | I say we get started | 15:03 |
| hberaud | damani: o/ Around? No meeting today? | 15:05 |
| felixhuettner[m] | i thought we aggreed on the ML to have the discussion about NATS today? | 15:10 |
| tobias-urdin6 | lets just go i guess? don't need to make it official unless you can start meeting hberaud | 15:11 |
| hberaud | ok | 15:11 |
| hberaud | #startmeeting oslo | 15:12 |
| opendevmeet | Meeting started Mon Sep 19 15:12:24 2022 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:12 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:12 |
| opendevmeet | The meeting name has been set to 'oslo' | 15:12 |
| hberaud | Courtesy ping for hberaud, bnemec, johnsom, redrobot, stephenfin, bcafarel, kgiusti, jungleboyj, gmann, tobias-urdin | 15:12 |
| johnsom | o/ | 15:12 |
| hberaud | #link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting | 15:12 |
| hberaud | As I'm not the meeting facilitator, let's move directly to the NATS topic | 15:13 |
| hberaud | #topic NATS driver – moving forward and future of eventlet | 15:13 |
| tobias-urdin6 | yeah, just to start things off, i think we can all agree that using the official nats-py library is the only way forward for getting it in | 15:13 |
| hberaud | +1 | 15:14 |
| damani | hberaud, yes | 15:14 |
| damani | sorry | 15:14 |
| tobias-urdin6 | so the real question becomes how should we go on about that, so, how do we go forward with that? | 15:14 |
| damani | #startmeeting oslo | 15:14 |
| opendevmeet | damani: Error: Can't start another meeting, one is in progress. Use #endmeeting first. | 15:14 |
| tobias-urdin6 | running the driver in a separate thread due to needing asyncio, anybody have any ideas? | 15:15 |
| damani | sorry | 15:15 |
| hberaud | damani: the meeting is already started... | 15:15 |
| damani | you have already started | 15:15 |
| damani | yes | 15:15 |
| tobias-urdin6 | this discussion will probably be a lot of overlap into the "how to use asyncio" in the openstack eco system | 15:15 |
| tobias-urdin6 | so i'm interested in where we should initially place our focus, how we should prioritize our time moving forward, whats steps do we need is what we need to figure out | 15:16 |
| hberaud | yoctozepto proposed to start migrating blazar (a simple project, more simpler than nova) to asyncio first and then start using the nats driver with asyncio | 15:16 |
| hberaud | so with this solution we won't have to run IPC to RPC | 15:17 |
| hberaud | we will use NATS directly | 15:17 |
| hberaud | and, I think, that could help us to design a process to help migrating from evnetlet to asyncio | 15:18 |
| johnsom | Are the discussions that all projects should move, like a community goal? Or is this an opt-in if you want it? I was expecting this was an opt-in change. | 15:18 |
| hberaud | (for the other services) | 15:18 |
| tobias-urdin6 | johnsom: we are just brainstorming now pretty much, but I think it's in the communities interest to consider | 15:19 |
| johnsom | That said, moving off eventlet is a worthy goal. I.e. https://review.opendev.org/c/openstack/designate/+/856313 | 15:19 |
| felixhuettner[m] | just for consistency it might make more sense as a community goal (if the move proves worthwhile) | 15:19 |
| hberaud | IMO I think we should found/write/design an "how to" migrate from eventlet from asyncio | 15:19 |
| hberaud | (first) | 15:20 |
| johnsom | +1 to hberaud | 15:20 |
| tobias-urdin6 | some links where brought up about eventlet being mostly stale in https://meetings.opendev.org/irclogs/%23openstack-oslo/%23openstack-oslo.2022-09-02.log.html | 15:20 |
| johnsom | Goals that are put in place before there is enough supporting libraries and documentation do not go well. | 15:20 |
| hberaud | and then migrate blazar in parallel during the implementation of the NATS driver | 15:20 |
| hberaud | moving away eventlet is clearly a community goal, but I think the blazar migration could be a POC | 15:21 |
| hberaud | before officializing this goal as a community goal. | 15:22 |
| johnsom | +1 | 15:22 |
| tobias-urdin6 | so what are potential blockers, are we talking about asyncio support for oslo.db and an asyncio oslo.messaging executor to migrate blazar? | 15:22 |
| hberaud | We could bring some guidance and adivces | 15:22 |
| hberaud | no I don't think | 15:23 |
| hberaud | whatever...that's a good question... | 15:23 |
| hberaud | oslo.db seems already compatible | 15:23 |
| hberaud | AFAIK | 15:24 |
| hberaud | however if we transition blazar first, then I think that mean that we should also transition the oslo.messaging executor... | 15:24 |
| hberaud | without even starting to use the NATS driver... | 15:25 |
| hberaud | so, I think the NATS driver should be ready before blazar | 15:25 |
| hberaud | and during the transition of blazar we should switch the driver | 15:26 |
| hberaud | thoughts? | 15:26 |
| hberaud | does the snake bite its tail? | 15:26 |
| tobias-urdin6 | hm | 15:27 |
| yoctozepto | o/ | 15:27 |
| yoctozepto | sorry for being late, my calendar reminder failed | 15:27 |
| hberaud | np | 15:28 |
| felixhuettner[m] | or would we rather need the amqp driver to be asyncio-ready as well | 15:28 |
| tobias-urdin6 | so, an asyncio oslo.messaging executor, nats driver with nats-py and get oslo.db working (or verify it works) and run devstack with both nats and rabbitmq where blazar uses nats | 15:28 |
| felixhuettner[m] | to skip this dependency | 15:28 |
| tobias-urdin6 | would that be correct? | 15:29 |
| hberaud | At first glance yes, that looks correct | 15:29 |
| felixhuettner[m] | sound good for me | 15:29 |
| yoctozepto | mhm | 15:29 |
| yoctozepto | or are we ready to roll out a rmq/amqp-compatible asyncio driver? | 15:30 |
| yoctozepto | as to avoid too many moving parts | 15:30 |
| yoctozepto | ignore if it is similar workload to adding nats support | 15:30 |
| tobias-urdin6 | ok, so I found a very old poc in incubator for tullip oslo.messaging executor that is some predecessor (with some others) to the asyncio implement iiuc, not that it's working or complete but atleast a template https://github.com/markmc/oslo-incubator/blob/8509b8bf7220605143dff149a4e32a923d0ead02/openstack/common/messaging/_executors/impl_tulip.py | 15:31 |
| hberaud | tobias-urdin6: running devstack with both nats and rabbitmq, you mean with blazar? | 15:31 |
| tobias-urdin6 | not sure, we'd need to dig more into details about rabbit support for asyncio i guess | 15:32 |
| tobias-urdin6 | hberaud: yeah, like blazar uses rpc over nats and all other openstack services use rabbitmq | 15:32 |
| hberaud | ok, then sound good | 15:32 |
| tobias-urdin6 | the devstack plugin i wrote now just plain off disables rabbitmq so need to remove that | 15:32 |
| yoctozepto | ++ | 15:33 |
| yoctozepto | we need rmq to pass CI because blazar depends on nova | 15:33 |
| felixhuettner[m] | at least the kombu library we use does not support asyncio yet: https://github.com/celery/kombu/issues/879 | 15:33 |
| hberaud | tobias-urdin6: yes I don't think we want to spend time with rmq and asyncio into the related O.M driver | 15:34 |
| yoctozepto | ack, so let's go with oslo.messaging(asyncio+nats) | 15:34 |
| tobias-urdin6 | i'm however not sure if we need some kind of changes in oslo.db for the sqlalchemy part tho but i guess we'll find out | 15:34 |
| yoctozepto | I don't know either | 15:35 |
| yoctozepto | hoping not too many | 15:35 |
| hberaud | yeah... | 15:35 |
| tobias-urdin6 | sound like a plan atleast, if we'd get that working, we have another nest with taskflow/futurist part but we are spared since blazar doesn't use those part (except oslo.messaginge executor from futurist used today) | 15:35 |
| hberaud | Apparently that seems "ready" (by reading the doc) | 15:35 |
| yoctozepto | yup | 15:36 |
| yoctozepto | hberaud: what looks "ready"? | 15:36 |
| hberaud | Last week I tried to identify existing tuto/doc/data that could be useful and used during the blazar transition | 15:37 |
| hberaud | yoctozepto: supporting asyncio | 15:37 |
| yoctozepto | hberaud: that I got but where? | 15:38 |
| tobias-urdin6 | felixhuettner[m]: ack, that won't be fun, we'll probably have a hard time convincing projects to take action unless default oslo.messaging driver becomes nats then | 15:38 |
| yoctozepto | as we mentioned a couple of projects | 15:38 |
| tobias-urdin6 | but atleast we can make this a poc | 15:38 |
| yoctozepto | hberaud: and what have you found regarding tutos and docs? | 15:38 |
| hberaud | yoctozepto: sorry I was thinking only about sqlalchemy | 15:38 |
| yoctozepto | ah | 15:39 |
| yoctozepto | ok | 15:39 |
| hberaud | you're right oslo.db would surely require changes too | 15:39 |
| tobias-urdin6 | do we want to start an etherpad and collect all links and docs or just use some existing? | 15:39 |
| tobias-urdin6 | hberaud: yeah i think so | 15:39 |
| yoctozepto | yeah, we need an organisational scratchpad | 15:40 |
| hberaud | tobias-urdin6: an etherpad could be useful | 15:40 |
| yoctozepto | so etherpad will do | 15:40 |
| tobias-urdin6 | i don't have enough insight into oslo.db but perhaps we can abstract away some asyncio parts for projects there when we run into them | 15:41 |
| hberaud | LGTM | 15:42 |
| yoctozepto | makes sense to me | 15:42 |
| hberaud | let's focuse on O.M and Blazar first and then address the O.db things | 15:42 |
| tobias-urdin6 | +1 | 15:42 |
| hberaud | We could start with 1) the "blueprint" part on one side, 2) check for examples of projects who already migrated from eventlet to asyncio 3) start the blazar migration to asyncio | 15:44 |
| hberaud | (O.M blueprint) | 15:44 |
| yoctozepto | +1, good plan, all 3 can start parallelly though | 15:45 |
| yoctozepto | AFAIAC | 15:45 |
| hberaud | https://review.opendev.org/c/openstack/oslo-specs/+/692784 | 15:45 |
| hberaud | do we want to reuse that one ^? | 15:46 |
| tobias-urdin6 | https://etherpad.opendev.org/p/oslo-asyncio <-- a start? | 15:46 |
| hberaud | or start with a new one fresly created and give a reference to the old one? | 15:46 |
| yoctozepto | hberaud: start with a fresh one, we can copy some contents though as we see fit | 15:47 |
| hberaud | ok | 15:47 |
| hberaud | WFM | 15:47 |
| tobias-urdin6 | think ^ would be easier to see comments etc | 15:47 |
| hberaud | ok | 15:47 |
| hberaud | tobias-urdin6: what do you mean? => "Update NATS driver to use nats-py" | 15:48 |
| hberaud | you mean creating? | 15:48 |
| hberaud | the nats driver doesn't yet exist | 15:48 |
| hberaud | Ok I seen your latest changes on the etheroad | 15:48 |
| hberaud | pad | 15:49 |
| tobias-urdin6 | yeah so earlier patchsets already used nats-py, so perhaps we can use https://review.opendev.org/c/openstack/oslo.messaging/+/848338 as template | 15:49 |
| tobias-urdin6 | otherwise we'll just start from scratch and copy, same there, as spec | 15:49 |
| hberaud | LGT% | 15:52 |
| hberaud | M | 15:52 |
| hberaud | let's resuse the existing stuffs | 15:53 |
| hberaud | what pace should we have for our next meetings? | 15:54 |
| hberaud | I'd suggest speaking about NATS each 2 or 3 weeks. Thoughts? | 15:55 |
| hberaud | Do we want to run our own meeting to avoid similar issue than today? | 15:56 |
| tobias-urdin6 | sounds good, anybody interested in volunteering for any of the parts in the plan? | 15:56 |
| yoctozepto | a dedicate asyncio meeting sounds good | 15:56 |
| yoctozepto | dedicated* | 15:56 |
| hberaud | +1 for a dedicated meeting | 15:56 |
| tobias-urdin6 | works for me, i don't really have a preference | 15:56 |
| yoctozepto | every 2 weeks makes sense to me | 15:56 |
| tobias-urdin6 | do we prioritize getting a poc working or do we want specs? i would rather see a working poc than specs tbh | 15:57 |
| hberaud | tobias-urdin6: do you want to become our chair meeting for this topic? | 15:57 |
| hberaud | the POC LGTM | 15:58 |
| tobias-urdin6 | sure can do depending on time/day tho | 15:58 |
| yoctozepto | PoC makes sense to prioritise over exact specs | 15:58 |
| yoctozepto | but refreshing a spec skeleton would not hurt... | 15:58 |
| hberaud | I'm volunteer to refresh the specs | 15:59 |
| hberaud | to keep a trace of our related researchs and discussions | 15:59 |
| hberaud | Ok, I think we reached our meeting timeslot end | 16:01 |
| tobias-urdin6 | ack, we'll i'm a little bit interested in getting started on a oslo.messaging executor unless anybody else want it | 16:02 |
| yoctozepto | I'm interested in looking into blazar's deps on eventlet closer | 16:02 |
| hberaud | That's sound like a plan | 16:02 |
| tobias-urdin6 | i think the messaging driver parts is more a refactor to a working state with nats-py | 16:02 |
| hberaud | yes | 16:02 |
| hberaud | good we have people almost on each topics | 16:03 |
| tobias-urdin6 | good, do we set a new meeting slot or take offline on ml | 16:04 |
| hberaud | I put my name on the etherpad into the lines that interested me | 16:04 |
| yoctozepto | offline | 16:04 |
| hberaud | as you want | 16:04 |
| hberaud | offline lgtm | 16:04 |
| tobias-urdin6 | works for me, thanks for today | 16:05 |
| yoctozepto | thanks | 16:05 |
| hberaud | that was a productive meeting, thanks everyone! | 16:05 |
| hberaud | Anything else before I close the meeting? | 16:06 |
| tobias-urdin6 | not from my part | 16:06 |
| hberaud | ok thanks everyone | 16:06 |
| hberaud | #endmeeting | 16:06 |
| opendevmeet | Meeting ended Mon Sep 19 16:06:50 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:06 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/oslo/2022/oslo.2022-09-19-15.12.html | 16:06 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/oslo/2022/oslo.2022-09-19-15.12.txt | 16:06 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/oslo/2022/oslo.2022-09-19-15.12.log.html | 16:06 |
| opendevreview | Merged openstack/oslotest stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/oslotest/+/855959 | 17:01 |
| opendevreview | Merged openstack/debtcollector stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/debtcollector/+/855919 | 18:15 |
| opendevreview | Merged openstack/taskflow stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/taskflow/+/855961 | 18:18 |
| opendevreview | Merged openstack/oslo.i18n stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/oslo.i18n/+/855943 | 18:19 |
| opendevreview | Merged openstack/oslo.middleware stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/oslo.middleware/+/855946 | 18:22 |
| opendevreview | Merged openstack/oslo.limit stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/oslo.limit/+/855895 | 18:23 |
| opendevreview | Merged openstack/automaton stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/automaton/+/855913 | 18:26 |
| opendevreview | Merged openstack/oslo.rootwrap stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/oslo.rootwrap/+/855950 | 18:26 |
| opendevreview | Merged openstack/oslo.reports stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/oslo.reports/+/855949 | 18:31 |
| opendevreview | Merged openstack/oslo.privsep stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/oslo.privsep/+/855948 | 18:32 |
| opendevreview | Merged openstack/oslo.concurrency stable/ussuri: [stable-only] Cap virtualenv for py37 https://review.opendev.org/c/openstack/oslo.concurrency/+/855931 | 18:38 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!