14:00:21 #startmeeting kolla 14:00:21 Meeting started Wed Nov 6 14:00:21 2024 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:21 The meeting name has been set to 'kolla' 14:00:26 #topic rollcall 14:00:34 o/ 14:00:34 o/ 14:00:47 \o 14:01:53 looks like a small meeting :-/ 14:02:17 \o/ 14:02:28 #topic agenda 14:02:43 - Release tasks 14:02:55 * Current cycle planning 14:03:01 * Additional agenda (from whiteboard) 14:03:07 * Open discussion 14:03:10 #topic Release tasks 14:03:25 So, Dalmatian for Kolla and Kolla-Ansible is done, as in final release 14:03:39 o/ 14:03:39 jovial: around to tell us what's Kayobe state? 14:04:05 guess not, but now the time is ticking for Kayobe 14:04:14 #topic Current cycle planning 14:04:25 Ok then, we sort of promised to kevko to go through all his patches 14:04:39 So - is there a list of things we should review? 14:05:17 would be nice to have those on the whiteboard, because I really lose track of stuff, given the high velocity of patches flying around :D 14:05:19 https://review.opendev.org/q/owner:michal.arbet@ultimum.io+status:open 14:05:23 https://review.opendev.org/c/openstack/kolla/+/915440 - that one needs just a green CI run 14:05:27 looks like quite some task ;) 14:05:48 https://review.opendev.org/q/owner:michal.arbet@ultimum.io+status:open+is:mergeable 14:05:50 smaller one 14:05:55 I really don't think all his patches are "urgent", especially not the ones having a merge conflict 14:05:59 mnasiadka: it's still in whiteboard 14:06:44 Sounds good 14:06:51 L241 on the whiteboard 14:07:12 frickler: are you willing to look at https://review.opendev.org/q/topic:%22kolla-patch%22 ? 14:07:17 there are few patches only ... 14:07:47 fix-config-json-handling is on the way as soon as jobs don't fail on dns issues or internet issues 14:07:59 i've addressed all comments ...and it's very useful feature 14:08:02 willing is such an active term ... but yes, I'll take a look 14:08:31 thanks 14:08:50 I'll handle the rest and find Bartosz (and maybe someone else) to have a look as well 14:09:14 thank you mnasiadka 14:09:21 So, I think we have one topic which we sort of missed on the PTG 14:09:22 Eventlet removal is happening 14:09:25 Which means we need to move everything to WSGI? 14:09:26 i will abandon or mark as DNM 14:09:26 frickler: you might have more insight? 14:09:56 well there are different options than wsgi being discussed iiuc 14:10:04 are we sure we want wsgi ? 14:10:39 I don't think any immediate action is needed, though 14:10:42 afaik not everything works with wsgi 14:10:55 Just asking if we need to have a look on anything 14:11:19 But maybe let's wait 14:11:32 I'm hoping watching what happens in devstack should be good enough for now 14:11:44 well, WSGI/ASGI means we don't have a binary to run - where we use that for non-WSGI enabled services 14:12:45 gunicorn ? 14:12:46 I have some time over the remainder of the year, so I might dust off the gunicorn patch and think if it's a good idea to migrate from mod_wsgi to gunicorn 14:13:12 Which would make all of our services a bit lighter 14:13:41 the only one that requires apache/nginx/whatever is keystone/horizon for federation stuff 14:14:12 anyway, I didn't have time to convert Epoxy PTG notes to actionable items 14:14:23 so I'll do that for the next meeting and we can discuss if we're missing anything 14:14:37 kevko: how is that... RMQ Queue Manager or how is it called? 14:14:43 yes 14:14:54 rabbitmq manager 14:15:17 working/not working? anything we should start looking into? 14:15:22 I would prefer merging it early in the cycle 14:15:28 it's working ... but need /dev/shm mounted 14:15:28 compared to breaking everything in the end 14:15:58 well, sort of defies containers, but people do the same in Kubernetes world, and I guess it's not all of the containers - just API services 14:16:39 or rabbitmq clients 14:16:44 mnasiadka: it's services which are touching rabbitmq 14:16:58 would be nice to get this working 14:17:00 anyway, let's first merge the list you gave us and then get back to this sooner than later 14:17:02 mnasiadka: everything with rabbitmq snippet in configuration 14:17:19 ok then, that's it for planning I guess 14:17:33 #topic Additional agenda (from whiteboard) 14:17:42 mnasiadka: well, rmq manager is nice stuff ...but it's the last one ...and it's some time i was working on 14:18:06 nothing in additional agenda 14:18:11 #topic Open discussion 14:18:14 anything? 14:18:18 (yoctozepto) Need to add https://docs.openstack.org/WHATEVER/deploy/ update after branching to release actions 14:18:28 I found that on the whiteboard just earlier 14:18:31 oh that one 14:18:37 yes, it's also in the release docs 14:18:40 anybody happy to fire it off? 14:18:41 will do a patch for that for the current release 14:19:09 https://review.opendev.org/c/openstack/kayobe/+/793697 14:19:11 old Kayobe change 14:19:12 the other thing: do we need to do new stable releases? 14:19:17 please review and merge 14:19:21 Sorry, I was late for the start. Just a word to say that we are almost ready for rc1 in kayobe. I've just sent the kayobe-config and kayobe-config-dev sync patches on their way. 14:19:25 or maybe not 14:19:40 frickler: I guess it would make sense 14:19:42 and some backports please: https://review.opendev.org/q/I4bbfef3a391b8582ae73cbe06138715b43584dec+status:open 14:20:12 what's exactly required there for the release action? I didn't understand that blurb. 14:20:37 we need to add Kolla-Ansible to the deploy-guide for Dalmatian IIRC 14:21:02 Actually it's empty 14:21:06 :D 14:21:19 I link the patch for reference when I have it 14:21:24 +will 14:21:24 https://docs.openstack.org/2024.2/deploy/ 14:21:47 well it doesn't hurt to be the first? ;) 14:21:54 frickler: If we could add that to the kolla release management docs - it would be nice 14:22:00 mnasiadka: ack 14:22:06 instead of finding that every cycle in KollaWhiteboard :) 14:22:09 Ok then 14:22:25 mmalchuk: the Kayobe one might not get it, but I leave that to jovial , I'll look in the backports though 14:22:40 jovial please 14:22:44 And I encourage all cores to look at backports from time to time (on the Kolla/Kolla-Ansible dashboards) :) 14:22:47 mnasiadka thanks 14:22:57 ok then, I guess that's it for today 14:23:05 thx 14:23:10 Ah, not all 14:23:12 I'm off next Wednesday 14:23:27 I'll ask Bartosz to run the meeting, if he can't - I'll ask frickler or kevko 14:23:34 bbezak will lead? or skip? 14:23:49 Merged openstack/kayobe-config master: [release] Synchronise with kayobe for 2024.2 https://review.opendev.org/c/openstack/kayobe-config/+/933848 14:24:01 But in two weeks I'm on OVSCON in Prague, so unless anybody outside of StackHPC wants to run - we'll probably skip 14:24:05 I'll be there 14:24:09 next wed 14:24:23 I'll be in Prague as well 14:24:30 Ok, bbezak for next Wed, and we'll skip the one in two weeks I assume. 14:24:31 mmalchuk: I'm not sure the TLS one can land in the state it is in. Like i say, we should add generic mechanism for adding certs to the system trust store 14:24:32 oh, I forgot ..I am also off for next two weeks ...finally going to take some rest 14:24:33 company outing? ;) 14:25:02 frickler: Prague is close, we have some short presentation and then I think I still like beers in Czechia ;) 14:25:13 but I will see ... taking my laptol ...I am a bit workoholic 14:25:18 Anyway, I would say that's it for the meeting today. 14:25:23 Thank you all for coming :) 14:25:24 #endmeeting