| *** mhen_ is now known as mhen | 02:50 | |
| cardoe | Anyway to figure out how to troubleshoot what's loading or not with https://docs.openstack.org/releasenotes/oslo.config/2023.1.html#relnotes-3-20-0-unmaintained-2023-1 ? | 03:47 |
|---|---|---|
| cardoe | Using OpenStack Helm and they hard code starting things with --config-file paths and I'm looking to inject some snippets in. Specifically with neutron-server which isn't running with uWSGI | 03:48 |
| opendevreview | Takashi Kajinami proposed openstack/oslo.cache master: WIP: Add valkey support https://review.opendev.org/c/openstack/oslo.cache/+/938639 | 03:48 |
| cardoe | Thus far I've tried /etc/neutron/neutron-server.conf.d/snippet.ini and /etc/neutron.conf.d/snippet.ini /etc/neutron-server.conf.d/snippet.ini | 03:48 |
| cardoe | It's a section that's defined in another file but its options that aren't defined by any file | 03:49 |
| opendevreview | Takashi Kajinami proposed openstack/oslo.cache master: WIP: Add valkey support https://review.opendev.org/c/openstack/oslo.cache/+/938639 | 05:24 |
| opendevreview | Takashi Kajinami proposed openstack/oslo.cache master: WIP: Add valkey support https://review.opendev.org/c/openstack/oslo.cache/+/938639 | 05:25 |
| damani[m] | hi | 13:01 |
| damani[m] | #startmeeting oslo | 13:02 |
| opendevmeet | Meeting started Wed Feb 12 13:02:17 2025 UTC and is due to finish in 60 minutes. The chair is damani[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:02 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:02 |
| opendevmeet | The meeting name has been set to 'oslo' | 13:02 |
| hberaud[m] | o/ | 13:02 |
| damani[m] | hberaud, tkajinam, JayF, meeting oslo | 13:03 |
| damani[m] | #topic following up on openstackdocstheme discussion | 13:03 |
| damani[m] | the project config change is merged now, oslo-core is added as initial core member https://review.opendev.org/c/openstack/project-config/+/940845 | 13:04 |
| damani[m] | so we agree to add gtema in the core list for https://review.opendev.org/admin/groups/openstackdocstheme-core,members | 13:06 |
| damani[m] | i will add him now, that works for everyone? | 13:06 |
| gtema | and if you do not mind pls also have a look at the bootstrap5 change laying around | 13:07 |
| gtema | it need to land together with the related os-api-ref change so that I can proceed with rendering openapis for openstack services | 13:07 |
| damani[m] | ok nobody else is here i think but yes | 13:09 |
| damani[m] | so os-api-ref is in same situation, no active core and gtema is volunteer to maintain this repo too | 13:10 |
| hberaud[m] | gtema: you speak about this patch? https://review.opendev.org/c/openstack/os-api-ref/+/932048 | 13:11 |
| gtema | fyi: I have practical experience with those both since I was maintaining their downstream versions | 13:11 |
| damani[m] | if olso team agree then we can add gtema in this repo core list also | 13:11 |
| gtema | yes hberaud | 13:11 |
| tkajinam | sorry I didn't notice the meeting time. | 13:13 |
| damani[m] | ok i have took a look about the bootstrap5 looks good to merge for me | 13:13 |
| damani[m] | tkajinam, no worries | 13:14 |
| hberaud[m] | gtema: ack, will check | 13:14 |
| damani[m] | tkajinam, no objection to add gtema as core https://review.opendev.org/admin/groups/openstackdocstheme-core,members | 13:14 |
| gtema | perfect, thks. both changes (in theme and os-api-ref) need to merge at once since otherwise you get the stuff broken | 13:14 |
| damani[m] | and here https://review.opendev.org/admin/groups/os-api-ref-core,members | 13:14 |
| tkajinam | damani[m], no | 13:14 |
| damani[m] | ok i do it now | 13:15 |
| tkajinam | I mean I have nooo objection | 13:15 |
| damani[m] | i understood :) | 13:15 |
| damani[m] | hberaud, same for you? | 13:15 |
| hberaud[m] | no objection | 13:16 |
| damani[m] | #topic feature freeze | 13:17 |
| opendevreview | Takashi Kajinami proposed openstack/oslo.cache master: WIP: Add valkey support https://review.opendev.org/c/openstack/oslo.cache/+/938639 | 13:17 |
| damani[m] | so we are in the feature freeze, no merge | 13:17 |
| damani[m] | i have also check https://review.opendev.org/q/project:openstack/releases+status:open+oslo | 13:17 |
| hberaud[m] | no feature merge | 13:17 |
| hberaud[m] | fixes are allowed | 13:17 |
| tkajinam | I wonder what the current status/plan about new oslo.service backend is | 13:18 |
| damani[m] | yes | 13:18 |
| damani[m] | i mean no more feature merge | 13:18 |
| tkajinam | my main concern is that we have added tons of deprecation warnings but no alternative to get rid of these warnings | 13:18 |
| damani[m] | #topic backend status oslo.service | 13:19 |
| damani[m] | about the backend, so we have merge the backend system and the eventlet implementation | 13:19 |
| damani[m] | i have start to work on the threading implementation but nothing push yet, i will push soon a wip | 13:21 |
| damani[m] | then i will like one week off and then i will start to work again on it | 13:21 |
| damani[m] | i will also fix the documentation, i have a patch here https://review.opendev.org/c/openstack/oslo.service/+/940664 | 13:22 |
| tkajinam | do you want to propose FFE for it or do you plan to merge it in 2025.2 ? | 13:22 |
| tkajinam | if we merge it in 2025.2 then we can probably can't remove eventlet till 2027.1 | 13:23 |
| tkajinam | because 2026.1 may be the first release with alternative to eventlet backend | 13:23 |
| damani[m] | it's the idea yes | 13:23 |
| tkajinam | sorry which one "it" is. 2025.1 with FFE or 2025.2 ? | 13:24 |
| damani[m] | to propose a FFE to have the merge in 2025.1 | 13:24 |
| damani[m] | i mean i think it's the best | 13:24 |
| damani[m] | because as you said if we wait 2025.2 we can't remove eventlet till 2027.1 | 13:25 |
| tkajinam | week of feb 17 is the week for final release for non-client libraries | 13:25 |
| damani[m] | so the FFE seems necessary | 13:26 |
| damani[m] | yes | 13:26 |
| tkajinam | you can extend the deadline by FFE but only for one week | 13:26 |
| damani[m] | yes | 13:26 |
| damani[m] | i hope i can finish soon the implementation | 13:26 |
| damani[m] | and i hope the code will be fine not too much back and forth | 13:27 |
| tkajinam | ok though honestly I'm not too sure if that's feasible | 13:27 |
| damani[m] | i will ping you soon about it | 13:27 |
| tkajinam | ok | 13:27 |
| damani[m] | and we can talk again about it next week, i mean see if it's seems possible or if we wait 2025.2 | 13:27 |
| damani[m] | what do you think about that? | 13:28 |
| tkajinam | let's see how it goes but note that I may not join the next meeting because of its late slot | 13:28 |
| damani[m] | ok | 13:28 |
| damani[m] | next week we can maybe do two meetings | 13:29 |
| damani[m] | or i can ping a bit earliar to give a status | 13:29 |
| tkajinam | or we can discuss in here outside of the meeting | 13:29 |
| damani[m] | that works for you? | 13:29 |
| damani[m] | yes | 13:29 |
| damani[m] | do you any other question about the backend? | 13:30 |
| tkajinam | no | 13:30 |
| damani[m] | ok | 13:31 |
| damani[m] | #topic open discussion | 13:31 |
| damani[m] | something else you would like to talk | 13:31 |
| damani[m] | tkajinam, hberaud, do you have something you would like to talk | 13:31 |
| damani[m] | gtema, do you want i add you to the ping list | 13:32 |
| gtema | yupp, can be done | 13:32 |
| hberaud[m] | FYI I'm on PTO next week, so I'll fully AFK | 13:33 |
| tkajinam | hberaud[m], have a good break :-) | 13:33 |
| hberaud[m] | thanks :) | 13:33 |
| tkajinam | (though that means we may have less review bw | 13:33 |
| damani[m] | gtema, you are now core on openstackdocstheme-core | 13:34 |
| damani[m] | and os-api-ref | 13:34 |
| gtema | thanks a lot | 13:34 |
| damani[m] | welcome | 13:34 |
| tkajinam | once we pass feature freeze we can probably discuss inviting a few more people to cores or project specific cores | 13:34 |
| hberaud[m] | yeah, I tried to do many reviews this week, so if you have ones that you want to prioritize, then, please let me know | 13:34 |
| hberaud[m] | good idea | 13:34 |
| damani[m] | tkajinam, yes seems a very good idea | 13:35 |
| damani[m] | i agree with that | 13:35 |
| damani[m] | hberaud, enjoy your holidays | 13:36 |
| hberaud[m] | thanks :) | 13:36 |
| damani[m] | i hope i will take mine soon too :) | 13:36 |
| damani[m] | by the way something else we want to talk? | 13:37 |
| hberaud[m] | nope | 13:37 |
| tkajinam | no | 13:37 |
| damani[m] | ok | 13:38 |
| damani[m] | so we are done | 13:38 |
| damani[m] | gtema, hberaud, tkajinam, thanks a lot for your participation | 13:39 |
| damani[m] | #endmeeting | 13:39 |
| opendevmeet | Meeting ended Wed Feb 12 13:39:30 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:39 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/oslo/2025/oslo.2025-02-12-13.02.html | 13:39 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/oslo/2025/oslo.2025-02-12-13.02.txt | 13:39 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/oslo/2025/oslo.2025-02-12-13.02.log.html | 13:39 |
| hberaud[m] | thanks damani | 13:39 |
| gtema | thks, cy | 13:39 |
| tkajinam | thx | 13:42 |
| cardoe | So follow on to my questions about Oslo.config. The automatic directory loading isn’t really documented outside of a release note. But I found that easier than env vars. I’m trying to figure out how things load. We have neutron-server which is starting from the binary. But then also have one using uWSGI. The /etc/neutron/neutron-server.conf.d path didn’t work for the later. Nor did using neutron-api. How can I see what | 21:19 |
| cardoe | $prog is set to? | 21:19 |
| cardoe | So to provide some more details... https://etherpad.opendev.org/p/oslo-config-project-prog | 23:19 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!