14:02:26 #startmeeting kolla 14:02:26 Meeting started Wed Mar 12 14:02:26 2025 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:26 The meeting name has been set to 'kolla' 14:02:31 #topic rollcall 14:02:34 o/ 14:02:37 \o 14:02:38 o/ 14:02:44 still jetlagged? ;) 14:02:47 o/ 14:03:43 frickler: sort of, doing a lot of things at the same time to catch up two weeks absence :) 14:04:09 darmach koperg wake up :) 14:04:43 #topic agenda 14:05:00 * Announcements 14:05:08 * CI status 14:05:16 * Release tasks 14:05:24 * Current cycle planning 14:05:30 * Additional agenda (from whiteboard) 14:05:34 * Open discussion 14:05:37 #topic Announcements 14:06:18 So... I'm in New Zealand time zone when the PTG happens - so PTG will be around 7AM UTC time slot - I'll post those on openstack-discuss ML once I book these and create an etherpad for Kolla 14:06:34 or something like that 14:06:38 #topic CI status 14:06:54 Seems we have some neutron-metadata-agent healthchecking issues 14:07:05 Trying to debug it in https://review.opendev.org/c/openstack/kolla-ansible/+/944104 14:07:28 Also add some more debug to CI logs for unhealthy containers, so we don't have to do that next time. 14:07:45 I've seen some rabbitmq podman related container state problems, but I assume it's different 14:07:56 (although these don't happen every time) 14:08:03 #topic Release tasks 14:08:15 for metadata maybe neutron changed something? 14:08:31 might be related to eventlet removal and change timings somehow 14:08:36 Might be, that's why I need to first check if for example the process name did not change or something similar - we need more debug logs 14:08:58 And maybe better healthchecking scripts, but that's not going to happen soon ;) 14:09:05 ack 14:09:08 It's R-3 14:09:18 We might see breakages due to some last minute patches 14:09:40 I don't think we have any immediate work to do - koperg is working on Ansible bump 14:09:50 #topic Current cycle planning 14:10:02 Anybody wants to discuss any feature? any review requests? 14:10:18 I have this one: https://review.opendev.org/c/openstack/kolla-ansible/+/938649 14:10:25 I think its merge ready 14:10:41 yep. cinder issue in nova with tempest 14:10:50 https://review.opendev.org/c/openstack/kolla-ansible/+/937038/6 14:11:02 frickler: 14:11:11 I have https://review.opendev.org/c/openstack/kolla/+/934735 14:11:11 I have a simple ironic-related patch https://review.opendev.org/c/openstack/kolla/+/942785 and bbezak had another one which we might want to combine 14:11:57 https://review.opendev.org/c/openstack/kolla/+/933860 14:12:09 I'll add the others above to my list 14:12:29 yuval: one last question and I'm happy to apply my +2 ;) 14:13:20 frickler: can we go back with catalog_info in 6 patchet? 14:14:44 mmalchuk: I don't think we should backport in kolla anyway, but I'll update, yes 14:16:46 frickler: but we need merge in master an I mean 6 patchset 14:16:51 not latest 14:16:55 ok, added the rest of the patches to my review queue 14:17:38 yuval proposed openstack/kolla-ansible master: add lightbits driver support https://review.opendev.org/c/openstack/kolla-ansible/+/938649 14:17:42 Thanks 14:18:44 mnasiadka: you right, removed :) 14:20:08 #topic Additional agenda (from whiteboard) 14:20:47 Nothing new there 14:21:01 #topic Open discussion 14:21:02 Anybody anything? 14:23:10 yea 14:23:14 I got a question 14:23:20 shoot 14:23:31 I want to add an env variable to the cinder docker 14:23:49 currently I am forking out from the main branch to do it using the group_vars 14:24:06 and kolla-supported way to do it? 14:24:11 any* 14:25:17 this is the reason I need to do it: https://opendev.org/openstack/os-brick/src/commit/6e83ac6eeee8f3a4b3265a4e927dca1bc190e088/os_brick/privileged/__init__.py#L24 14:25:36 Not really, we have some places where we do supply environment in role defaults/ and then use it when starting the container, but not in Cinder 14:25:58 Like https://github.com/openstack/kolla-ansible/blob/b952debacc0b6516468d6fd8121facc65eb4d9c1/ansible/roles/etcd/defaults/main.yml#L7 14:26:43 to me that looks like a bad design decision in os-brick 14:26:47 yes.. maybe we can do some magic so we can control this in any docker we bring up? 14:27:10 frickler: totally agree - I uploaded a change for it but was rejected 14:28:48 I don't see any rejection here https://review.opendev.org/c/openstack/os-brick/+/942689 14:29:31 yes... silent rejection 14:30:03 cinder team is just almost non-existent in my experience 14:30:05 anyway I will think how we can control it and bring up a patch 14:31:05 frickler: no, no, They are doing amazing job. it just doing this change is not trivial 14:31:06 Ok then 14:32:01 I guess that's it 14:32:06 Sorry, missed the current cycle planning. Could we get some core reviewer eyes on the big rabbitmq patch chain again please? https://review.opendev.org/c/openstack/kolla-ansible/+/924623 and https://review.opendev.org/c/openstack/kolla-ansible/+/942867 are good to go imo. 14:32:22 @mnasiadka: sorry missed the start of the meeting ( client work ) We can consider ansible bump technically done - thanks for your help :D 14:32:53 We have quite a few to patches get through if we want RabbitMQ 4.0 in epoxy :) 14:33:22 Well, we need more reviewers it seems. 14:33:53 If you guys would review not only the patches you want to get in, maybe we'd get more core reviewers... 14:35:08 I will try 14:37:08 +1 14:37:16 (me too) 14:37:32 Can take a look, if you are satisfied with +1 :P 14:38:16 Ok, I'll try to make time to review other patches. 14:38:52 Reality is, that there are 4 active core reviewers, and we can't have velocity to merge everything - and the situation is getting worse, not better. 14:39:24 If your employers value/use kolla/kolla-ansible/kayobe - they should invest more. 14:39:28 That's my 5 cents :) 14:39:31 Thank you for coming - see you next week :) 14:39:42 #endmeeting