14:03:08 #startmeeting kolla 14:03:08 Meeting started Wed Dec 18 14:03:08 2024 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:03:08 The meeting name has been set to 'kolla' 14:03:10 #topic rollcall 14:03:12 o/ 14:03:15 \o 14:03:27 I was just about to wake you up ;) 14:05:19 hmm, looks like small audience anyway 14:05:28 o/ 14:05:29 yup 14:05:36 #topic agenda 14:05:52 * CI status 14:05:58 * Release tasks 14:06:04 * Current cycle planning 14:06:08 * Additional agenda (from whiteboard) 14:06:13 * Open discussion 14:06:15 #topic CI status 14:06:31 well, new Jammy kernel broke Neutron, but thanks to frickler it looks good now 14:06:59 After some work with proxysql settings I think we're getting multinode testing stability back 14:07:08 #topic Release tasks 14:07:34 I don't think we have any 14:07:39 #topic Current cycle planning 14:08:05 I've been progressing with uWSGI stuff, thanks to frickler and bbezak for reviews, will continue with the rest of services 14:08:53 I've seen kevko is working on finalising the database internal TLS, so we might finally get better in terms of backend/internal TLS 14:08:53 yeah, thanks for that, keep pinging me if I don't respond fast enough 14:10:00 I think for keystone and horizon - I'll just switch from apache+mod_wsgi to apache+mod_uwsgi - we have users that use mod_auth_mellon and existing stack for federation, so I doubt we'll ever want to get rid of apache 14:11:05 #topic Additional agenda 14:11:13 apache+mod_proxy + external uwsgi, like devstack does, might be an alternative? not sure if it is better, though 14:11:34 yeah, right - I think we want to do what devstack does 14:11:42 so we don't find out weird issues by ourselves 14:11:51 (mattcrees): What do people think on backporting this patch? https://review.opendev.org/c/openstack/kolla-ansible/+/937670 We may not want to, as people who only ever run from one location will get an unnecessary config change. We should find out if anyone will be hit by that first. 14:12:00 Matt C is not here, but he wanted us to discuss that 14:12:49 frickler: I'm probably fine with backporting this, but need a second core to approve :) 14:13:39 hmm, the backport would also cause a restart in itself, right? so spontaneously I'd rather not do this 14:16:27 Ok then, we'll backport that downstream 14:17:09 #topic Open discussion 14:17:13 Anybody anything? 14:19:03 not from me 14:21:02 then I guess we're done :) 14:21:10 Thanks for coming frickler and mmalchuk 14:21:12 #endmeeting