14:00:00 #startmeeting kolla 14:00:00 Meeting started Wed Jan 25 14:00:00 2023 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:00 The meeting name has been set to 'kolla' 14:00:02 #topic rollcall 14:00:04 o/ 14:01:15 \o 14:01:20 o/ 14:01:22 o/ 14:01:26 \o/ 14:01:30 \o 14:02:05 o/ 14:02:08 /o\ 14:02:13 o/ 14:02:51 \o 14:03:51 #topic agenda 14:03:51 * CI status 14:03:51 * Release tasks 14:03:51 * Regular stable releases (first meeting in a month) 14:03:51 * Current cycle planning 14:03:52 * Additional agenda (from whiteboard) 14:03:52 * Open discussion 14:03:55 #topic CI Status 14:04:30 So, I've fixed some a-c-kolla missing CI jobs after renames 14:05:32 I'm a bit concerned about Rocky Ironic CI jobs issues, both in K-A and Kayobe 14:06:00 I'll write that down on the whiteboard, because they are failing not every time, but often 14:06:08 #topic Release tasks 14:06:11 I don't think we have any 14:06:18 #topic Current cycle planning 14:06:30 So, I think it's time to merge the systemd patch in kolla-ansible 14:06:52 I tried it out, seems to be working ok, and I have a feeling if we don't merge it - we'll postpone it again and again 14:07:02 https://review.opendev.org/c/openstack/kolla-ansible/+/816724 14:07:24 frickler, kevko, hrw, bbezak - wdyt? 14:07:36 trial by fire, sounds reasonable 14:07:59 let's do it 14:08:07 Merged openstack/kolla-ansible master: Adding optional delay between l3 agent restarts https://review.opendev.org/c/openstack/kolla-ansible/+/862916 14:08:07 We still have quite a couple of months before release, so it's time I guess 14:08:08 master is for testing isn't? 14:08:10 :) 14:08:16 And we would make mhiner happy 14:08:36 very much :D 14:08:43 always can revert 14:08:55 yup 14:09:06 Added my +2, another trial by fire participant needed. 14:10:50 i gave also - merging :) 14:11:01 Great, one thing over the line, let's see if it breaks :) 14:11:54 mhiner: I see there are some other patches that you could refresh/rebase now, and we could tackle them one by one 14:12:35 The other long awaited patch is Let's Encrypt, but I didn't have time yet to do some proper testing of that. 14:13:34 another candidate for trial by a fire ? :D 14:13:47 yes, they deal with preparation for podman introduction 14:13:51 not yet, for systemd patch I did have a look on a local env :) 14:14:20 for let's encrypt it needs to wait a bit, unless other cores are happy to give a meaningful review to it 14:14:39 i really want to test letsencypt on local env (but currently i am reworking my pipelines to build en ENV ...but i am almost done ... so i will check it - i hope) 14:15:32 good 14:15:57 ok, let's go further 14:16:12 #topic Open discussion 14:16:16 I have a small question 14:16:25 is there a reason kolla-ansible-debian-aarch64 is not voting? 14:16:46 no idea 14:17:35 maybe because smallest group of people who is using k-a on aarch64 ? 14:17:51 well, if it's reliable, and I think it is - we should mark it as voting 14:17:58 and we should at least try to not break it :) 14:18:19 (with non-voting I have a feeling we don't really care) 14:18:37 Does anybody care enough to mark it as voting? 14:18:52 let me 14:19:06 good 14:19:35 don't care 14:19:40 according Support Matrix 14:19:48 we support Debian 14:20:07 Marcin Juszkiewicz proposed openstack/kolla-ansible master: CI: make debian/aarch64 voting https://review.opendev.org/c/openstack/kolla-ansible/+/871732 14:20:09 so it should vote 14:20:32 https://review.opendev.org/c/openstack/kolla/+/871348 needs brave person for trivial change 14:20:41 debian x86 is voting, so aarch64 should as well 14:20:48 as long as we have any CI infrastructure to test it :) 14:20:57 https://review.opendev.org/c/openstack/kolla-ansible/+/869168 is aarch64 doc update which needs review/work 14:21:12 mnasiadka: opendev got new aarch64 nodes iirc 14:21:27 yes, working since today 14:21:48 though it may actually be only one physical node I think 14:22:06 hrw: doc update seems ok, let's merge it 14:22:15 hrw: from another front - I think you've tried with multiarch images once? 14:22:23 mnasiadka: nope 14:22:44 on another note: I'll be holidaying the next two weeks and plan to be mostly offline. so don't ping me, I'll ping you ;) 14:22:54 frickler: have fun 14:22:55 someone else will have to take care of stable releases next week, too 14:23:00 who goes to fosdem? 14:24:39 what is fosdem ? 14:25:04 fosdem is two weeks conference done in 2 days 14:25:05 google died? :) https://fosdem.org 14:26:21 ok, any other topics? 14:26:49 * hrw not 14:27:31 * kevko not 14:27:43 maybe quickly mention the recent nova+cinder vuln 14:27:49 in case anyone missed it 14:28:14 link ? 14:28:15 which one? 14:29:03 https://launchpad.net/bugs/1996188 14:29:14 #link https://security.openstack.org/ossa/OSSA-2023-002.html 14:29:39 and that one, yes 14:30:57 the patch backports in relevant projects are underway 14:30:58 wow 14:31:07 not affecting kolla directly, but important to fix IMO for anyone having 3rd party accessing their cloud 14:31:07 woow 14:31:24 thanks for info) 14:35:00 Sorry to hijack thread but i have quick question, I am upgrading kolla from Xena to Yoga and i want to upgrade one components at a time (Ex: first keystone then nova and then neutron one by one. what are the best ways?) 14:35:01 guess that's it? 14:35:57 spatel: use -t keystone etc 14:37:14 Hmm! nice.. let me give it a try Thanks :) 14:38:30 Ok, I think that's enough :) 14:38:32 Thanks for coming! 14:38:34 #endmeeting