14:00:00 #startmeeting kolla 14:00:00 Meeting started Wed Feb 14 14:00:00 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:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:00 The meeting name has been set to 'kolla' 14:00:06 #topic rollcall 14:00:08 o/ 14:00:10 o/ 14:00:27 o/ 14:00:48 o/ 14:00:56 o/ 14:03:04 #topic agenda 14:03:04 * CI status 14:03:04 * Release tasks 14:03:04 * Current cycle planning 14:03:04 * Additional agenda (from whiteboard) 14:03:06 * Open discussion 14:03:09 #topic CI status 14:03:19 Cinder upgrade jobs still broken, but Cinder is working on a fix 14:03:56 We've switched etcd in cephadm jobs to redis for now, we could also deploy etcd just for testing etcd - we just need to make sure redis gets used for services coordination 14:04:23 I believe no other major nor minor CI issues 14:04:34 #topic Release tasks 14:04:45 \o 14:04:54 It's R-7 14:05:09 Extra-AC freeze and Oslo feature freeze 14:05:17 nothing to do on our side 14:05:26 #topic Current cycle planning 14:05:35 bbezak: how's the Ironic drama? 14:06:31 initially I wanted to move only to service role for ironic 14:06:37 unfortunately not all services implemented service role 14:06:41 support 14:06:57 glance/nova didn't, so ironic user can't list glance images in different projects 14:07:06 so in caracal we need to also use admin user 14:07:16 (role) 14:07:31 and service role too, as it is special pan scope role only for ironic :) 14:07:32 well, it is what it is 14:08:11 I worked on the Cinder service role as well, it seems to be working 14:08:30 but I sort of dislike adding the 'service' role in each service so service-ks-register role can create 'service' role 14:08:31 more over we need to add service role creation up to zed I believe 14:08:40 in keystone role 14:08:42 since Bobcat I think keystone-manage bootstrap creates this role 14:08:45 yeah 14:08:51 I'll look into that 14:09:08 so basically we need a separate patch for adding service role in keystone Ansible role and rebase the Nova/Cinder patch on that 14:09:27 for slurp to work 14:09:31 Yes 14:10:02 Ah, forgot to mention - we regained ownership over unmaintained/yoga - regular kolla/kayobe cores can merge patches 14:10:26 for now SHPC is going to maintain those branches surely - once we don't need them - we can discuss what to do 14:10:56 kevko: how's dinit testing going? 14:12:50 ok, seems kevko is busy :) 14:12:53 let's go further 14:12:59 #topic Additional agenda (from whiteboard) 14:13:06 (jovial): https://review.opendev.org/c/openstack/kolla-ansible/+/877776 14:13:44 Pierre Riteau proposed openstack/kayobe stable/2023.2: CI: support .gitreview of unmaintained branch https://review.opendev.org/c/openstack/kayobe/+/908929 14:13:50 Pierre Riteau proposed openstack/kayobe stable/2023.1: CI: support .gitreview of unmaintained branch https://review.opendev.org/c/openstack/kayobe/+/908930 14:14:23 Merged openstack/kolla-ansible master: CI: Switch cephadm jobs to redis https://review.opendev.org/c/openstack/kolla-ansible/+/908895 14:14:27 Merged openstack/kolla-ansible master: CI: Increase RADOS timeout for cephadm jobs https://review.opendev.org/c/openstack/kolla-ansible/+/908980 14:14:31 Merged openstack/kolla master: docs: update monthly stable releases loop https://review.opendev.org/c/openstack/kolla/+/908991 14:14:32 ok, reviewed that again - needs a core outside of SHPC 14:14:34 mnasiadka: fine, ..but i have some issues with rabbit :P 14:14:37 #topic Open discussion 14:14:43 kevko: who doesn't have issues with rabbit :) 14:14:52 Any other topics? 14:15:19 Can you please review this again: https://review.opendev.org/c/openstack/kolla-ansible/+/905837 14:15:42 mnasiadka: true :D 14:15:49 I have used it in the migration patch and it seems to be doing fine 14:17:37 mhiner: I'll have a look later 14:17:54 Also I would appreciate if someone took a look at the migration patch in the failed job "kolla-ansible-rocky9-container-engine-migration" 14:17:57 need to understand the whole context - unless you can update the commit message writing why is it required 14:18:27 mnasiadka: I will update that 14:18:33 mhiner: thanks 14:18:47 do you plan to also test the reverse migration? ;-) 14:19:22 like Podman to Docker or like migration after migration? 14:19:38 Yes, Podman to Docker 14:19:59 could be in the same CI job I guess 14:20:52 same job? so Docker to Podman to Docker? 14:20:56 (and just asking if you plan to, it's fine if you don't) 14:21:15 yeah, Docker to Podman to Docker ;-) 14:22:28 tbh I don't, don't want to create so many jobs for single action and also single-node vs multi-node is important because of different way MariaDB is handled in those scenarios 14:23:16 so let's get docker to podman working first 14:23:28 and see if anybody is interested in migrating in the other direction 14:24:30 just fyi the other direction is supported in the patch 14:24:48 but not tested thoroughly? 14:26:03 not in the CI at least, in my local tests it worked but that was some time ago 14:26:09 ok, thanks 14:26:17 I see no other topics 14:26:20 so let's close for today 14:26:50 Ah, last thing - I'll populate the Dalmatian PTG Etherpad and send a mail to the mailing list 14:26:58 but etherpad copy paste is playing tricks with me 14:27:16 Thank you all for coming - and see you next week! 14:27:18 #endmeeting