13:00:50 <mnasiadka> #startmeeting kolla
13:00:51 <opendevmeet> Meeting started Wed Aug  2 13:00:50 2023 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:51 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:51 <opendevmeet> The meeting name has been set to 'kolla'
13:00:52 <mnasiadka> #topic rollcall
13:00:53 <mnasiadka> o/
13:00:59 <mmalchuk> \o
13:01:04 <jangutter> o/
13:01:07 <frickler> \o
13:01:16 <mattcrees> o/
13:01:32 * frickler likes how that all lined up
13:03:07 <mmalchuk> lol
13:03:14 <mnasiadka> #topic agenda
13:03:14 <mnasiadka> * CI status
13:03:14 <mnasiadka> * Release tasks
13:03:14 <mnasiadka> * Regular stable releases (first meeting in a month)
13:03:14 <mnasiadka> * Current cycle planning
13:03:16 <mnasiadka> * Additional agenda (from whiteboard)
13:03:16 <mnasiadka> * Open discussion
13:03:18 <mnasiadka> #topic CI Status
13:03:42 <mnasiadka> Basically master Kayobe is RED, because of a bug in Kolla-Ansible's systemd stuff
13:04:04 <mnasiadka> And we haven't seen that in Kolla-Ansible CI, because we don't use systemd at all (docker_restart_policy = no)
13:04:37 <mnasiadka> working on a fix, but basically on upgrade we end up with removing containers before they are stopped (so docker engine sends SIGKILL instead of SIGTERM) - and guess what - MariaDB doesn't like it very much.
13:05:39 <mmalchuk> thats predictable)
13:06:11 <mnasiadka> thank you captain obvious :)
13:06:14 <mnasiadka> ok, let's move on
13:06:19 <mnasiadka> #topic Release tasks
13:06:24 <mnasiadka> none this week
13:06:29 <mnasiadka> #topic Regular stable releases (first meeting in a month)
13:06:39 <mnasiadka> frickler: should we wait for the systemd fix with stable releases?
13:06:53 <frickler> which releases are affected?
13:07:28 <mnasiadka> Antelope only
13:08:03 <frickler> let's wait then I'd say
13:08:20 <mnasiadka> Yoga is going EM I think, so we'd need to tidy up patches there and submit last release
13:08:26 <frickler> also please review https://review.opendev.org/c/openstack/kolla/+/888219 that updates the instructions, I used the updated docs last time already
13:09:12 <frickler> oh, only just EMed xena
13:09:36 <frickler> but I don't mind, we don't use yoga anymore downstream
13:09:58 <mnasiadka> well, other thing is that seems EM is being changed to unmaintained (naming wise)
13:10:25 <mnasiadka> so those that use EM can expect a branch name change if I remember correctly to unmaintained/xena and unmaintained/yoga
13:10:38 <frickler> and becoming opt-in rather than opt-out going forward
13:11:03 <mnasiadka> yup, I don't mind - EM was like an unwanted child in Kolla landscape ;)
13:11:40 <mnasiadka> SHPC uses Yoga for now, but  Xena is not something we need
13:12:17 <mnasiadka> So agreed - when systemd will be fixed in k-a and backported to Antelope - we should do releases
13:12:23 <frickler> I was about to ask if we can just eol yoga instead, but seems you would not agree?
13:13:03 <mnasiadka> For now I think it would be better to keep the branch open, but I'll discuss that internally and come back to it on next weekly meeting
13:13:12 <mnasiadka> Anybody needs Xena?
13:13:15 <frickler> cool
13:13:22 <mmalchuk> me
13:14:18 <mnasiadka> No patches for stable/xena open
13:14:36 <mnasiadka> mmalchuk: how long do you think you need stable/xena open?
13:14:51 <mmalchuk> couple of week
13:14:55 <mmalchuk> please
13:15:19 <mnasiadka> ok, let's reassess in September
13:15:26 <mmalchuk> thanks
13:15:30 <mnasiadka> #topic Current cycle planning
13:15:42 <mnasiadka> Anybody had cycles to review Let's Encrypt?
13:15:53 <mmalchuk> I did review
13:16:16 <opendevreview> Merged openstack/kolla master: Update stable branch management doc  https://review.opendev.org/c/openstack/kolla/+/888219
13:16:27 <mnasiadka> I don't have time this week, but I'll try next
13:17:02 <mnasiadka> Ok, let's go to agenda from whiteboard, seems we have some
13:17:15 <mnasiadka> #topic Additional agenda (from whiteboard)
13:18:06 <mnasiadka> ihalomi - failing podman test on rocky9 https://zuul.opendev.org/t/openstack/build/bfc1625b4e0f4788be21f3bf5454ba4d
13:18:20 <mnasiadka> I promised to have a look, but didn't have time - should have some after the systemd bug
13:18:34 <mnasiadka> frickler - octavia jobboard
13:18:43 <mnasiadka> https://review.opendev.org/c/openstack/kolla/+/888587
13:18:43 <mnasiadka> https://review.opendev.org/c/openstack/kolla-ansible/+/888588
13:18:55 <frickler> yes, took me until today to update, sorry for that
13:19:07 <frickler> first patch is merged, second we talked about earlier
13:19:07 <mnasiadka> no problems
13:19:10 <mnasiadka> kolla side is merged
13:19:35 <mnasiadka> I understand jobboard won't work without redis - so we'd need some precheck?
13:20:00 <frickler> yes, I think so, I will try to build that
13:20:25 <mnasiadka> Great, anything else on that topic?
13:20:42 <frickler> not from me
13:20:48 <frickler> except ...
13:20:48 <mnasiadka> ok, next one
13:20:49 <mnasiadka> frickler - debian bookworm support
13:20:57 <mnasiadka> https://review.opendev.org/c/openstack/kolla/+/886088 seems mostly ready
13:20:57 <mnasiadka> https://review.opendev.org/c/openstack/kolla-ansible/+/888034 need to check the haproxy config update
13:21:45 <frickler> yes, the latter is marked as wip still because I wasn't sure whether we can drop that old haproxy option globally
13:21:49 <mnasiadka> kolla side looks ok, I can fix the netcontrold image
13:21:56 <frickler> does someone know haproxy better than me?
13:22:28 <mmalchuk> haproxy authorr?)
13:22:42 <mmalchuk> what the problem?
13:22:49 <mnasiadka> https://www.haproxy.com/blog/multithreading-in-haproxy#from-multiprocess-to-multithreading
13:22:59 <mnasiadka> nbproc is not supported, and we should move to multithreading
13:23:30 <mmalchuk> but there was reviews
13:23:44 <mmalchuk> and CI passd
13:24:18 <mnasiadka> where?
13:24:39 <mmalchuk> https://review.opendev.org/c/openstack/kolla-ansible/+/883560
13:25:11 <mmalchuk> and
13:25:12 <mmalchuk> https://review.opendev.org/c/openstack/kolla-ansible/+/883559
13:25:12 <mnasiadka> frickler: is nbproc dropped or do we need now to do nbthread and nbproc?
13:25:35 <mmalchuk> both need reviewers
13:25:40 <mnasiadka> I haven't seen that
13:25:49 <mmalchuk> vacation)
13:25:50 <opendevreview> Michal Nasiadka proposed openstack/kolla-ansible master: loadbalancer: support setting nbthread with variable haproxy_threads  https://review.opendev.org/c/openstack/kolla-ansible/+/883559
13:25:55 <opendevreview> Michal Nasiadka proposed openstack/kolla-ansible master: loadbalancer: support cpu-map for threads  https://review.opendev.org/c/openstack/kolla-ansible/+/883560
13:26:01 <opendevreview> Michal Nasiadka proposed openstack/kolla-ansible master: loadbalancer: remove support for haproxy_processes  https://review.opendev.org/c/openstack/kolla-ansible/+/883982
13:26:08 <mnasiadka> rebased, let's review
13:26:11 <frickler> me neither, I'll check those patches
13:26:33 <mnasiadka> added RP+1 to them
13:26:44 <frickler> the other thing is how to bump the debian python version in k and k-a at the same time
13:27:06 <frickler> make debian n-v in k-a temporarily?
13:27:17 <mnasiadka> no, we've been passing a variable in the past
13:27:36 <mnasiadka> but I had an idea to link the python version so that wsgi configs don't need to know the python version
13:27:45 <mnasiadka> or we could have a task to check python version in the image
13:28:08 <mnasiadka> https://review.opendev.org/c/openstack/kolla-ansible/+/874990
13:28:11 <mnasiadka> one attempt
13:28:23 <mnasiadka> I can have a look again, so we stop doing weird dances every time
13:28:42 <mnasiadka> ok, next one
13:28:53 <mnasiadka> jangutter - etcd support
13:28:53 <mnasiadka> https://review.opendev.org/c/openstack/kolla-ansible/+/888012 (adding/removing nodes to a cluster)
13:28:53 <mnasiadka> general question: any users of etcd? etcd-3.3 might no longer be supported
13:29:01 <mnasiadka> I saw that patch, will have a look next week
13:29:08 <jangutter> thanks! no rush!
13:29:24 <mnasiadka> around upgrading etcd - we could bump to 3.4 I guess, because etcd can't do skip level upgrades, right?
13:29:37 <jangutter> That's what I read too..
13:30:04 <mnasiadka> so let's do that
13:30:05 <jangutter> It's getting close though, if 3.6 releases then 3.4 goes out of maintenance.... so I guess sooner is better than later.
13:30:14 <mnasiadka> jangutter: happy to raise a patch to go to 3.4?
13:30:21 <mnasiadka> and then we could go to 3.5 in Caracal
13:30:22 <jangutter> try and stop me :-p
13:30:28 <mnasiadka> ok, thanks
13:31:08 <mnasiadka> I unfortunately need to run... sorry for the short meeting today
13:31:14 <mnasiadka> feel free to continue the discussion after the meeting
13:31:21 <mmalchuk> Gnocchi is back, fix - https://review.opendev.org/c/openstack/kolla/+/890302
13:31:23 <mnasiadka> #endmeeting