13:02:52 #startmeeting kolla 13:02:52 Meeting started Wed Jul 17 13:02:52 2024 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:52 The meeting name has been set to 'kolla' 13:02:55 #topic rollcall 13:02:55 o/ 13:02:58 o/ 13:03:14 o/ 13:03:21 \o 13:04:04 #topic agenda 13:04:04 * CI status 13:04:04 * Release tasks 13:04:04 * Current cycle planning 13:04:04 * Additional agenda (from whiteboard) 13:04:06 * Open discussion 13:04:08 #topic CI status 13:04:18 I haven't seen any serious issues 13:04:43 #topic Release tasks 13:04:58 It's R-15 - nothing related to us 13:05:07 #topic Current cycle planning 13:05:20 I re-started work on Ubuntu 24.04 and Ansible bump 13:05:34 Realised we've pinned bifrost Ansible version in Yoga and never bumped it up... 13:05:47 Trying to do it in a way we don't need to manage the Ansible pin in Bifrost image 13:06:41 is that a long term need, or is bifrost going to be fixed eventually? I don't recall the details why it's necessary, sorry. a link where I can read up would also suffice :) 13:07:08 well, bifrost pins ansible versions each cycle but only in their env-setup.sh (and bifrost-cli) 13:07:21 we can't use bifrost-cli, because that requires things like network_interface to be set 13:07:26 and we're skipping bootstrap on image build 13:07:32 ah, alright 13:07:48 ty 13:07:50 and env-setup.sh is failing because it removes epel first, and then tries to install it - and we try to use our sources 13:07:55 I'll work it out somehow 13:08:25 nothing else on the HAVE TO DO list on the whiteboard 13:08:27 let's move on 13:08:35 #topic Additional agenda (from whiteboard) 13:08:47 (r-krcek) on behalf of m.hiner please check if the docs are sufficient https://review.opendev.org/c/openstack/kolla-ansible/+/836941 13:09:40 I'm a bit worried about some things that are now worked around, and should be done in separate patches 13:09:44 mnasiadka: if you have time, could you please go reply to my replies on the patch? 13:09:46 I've already commented on this 13:10:04 Yeah, I'll reply there 13:10:11 thank you 13:10:14 but basically we don't need to launch the migration CI job every time 13:10:14 docs themselves seem fine to me. there's new commentary not concerned with docs :) 13:10:27 I assume it should be only run when some critical things for the migration itself change 13:10:32 e.g. migration playbooks 13:10:49 I would prefer to have more coverage than one distro 13:11:20 And I would prefer if we have patches for things like https://review.opendev.org/c/openstack/kolla-ansible/+/836941/comment/3f2bfb23_9910ff49/ and https://review.opendev.org/c/openstack/kolla-ansible/+/836941/comment/204e192d_d764d8d5/ to merge everything at the same time 13:11:21 yes, mhm, can we also run them when docker/podman are updated? might be hard to detect in CI though 13:11:25 instead of reworking this later 13:11:50 because I have a hunch it's going to stay like this for a long time ;-) 13:12:01 Ivan has started to work on those patches 13:12:27 afaik listing all containers was already pretty mature? 13:13:09 yes but it was made to work in kolla_container but I think the functionality is better suited for kolla_container_facts module 13:13:31 I'll reply on the patch after the meeting - but would like to see the final solution patches and merge everything together 13:13:54 alright 13:14:40 ok then 13:14:44 no more topics on the whiteboard 13:14:46 #topic Open discussion 13:15:22 Hi, I just wanted to up my patch, do you have any questions on it? https://review.opendev.org/c/openstack/kolla-ansible/+/920377 13:16:54 Additionally, can you please review this patch: https://review.opendev.org/c/openstack/kolla-ansible/+/911417 13:16:58 The container names patch will be dependent on it as it adds actions to kolla_container_facts 13:17:15 mhiner: will have a look 13:17:21 thanks again 13:17:34 chembervint: does it make any sense to not make 30minutes a default? 13:17:38 if anybody cares about unmaintained/zed you might want to check the publish jobs, they could be broken: https://zuul.openstack.org/builds?project=openstack%2Fkolla&pipeline=periodic-weekly&result=FAILURE&result=RETRY_LIMIT&result=POST_FAILURE&result=NODE_FAILURE&result=SKIPPED&skip=0 13:17:57 kevko maybe? :) 13:18:24 it's unmaintained, we don't care 13:18:57 but it seems the new password hasn't been backported to zed 13:18:57 regarding https://review.opendev.org/c/openstack/kolla-ansible/+/911417 I'd like to have some more senior opinions if we should backport it, not quite sure. 13:19:01 I would rather stop publishing 13:19:04 since it's unmaintained 13:19:18 any volunteer to stop publish jobs on yoga and zed? 13:20:01 mnasiadka: I've proposed it at the beginning, and then regarding on your comment moved it into variable, and has added Docs around it. but I don't see any concernes, if we will make default=30mins, but do it through var, to make customer able to tune it 13:20:25 well, I'm not using this at all 13:20:35 SvenKieske/frickler - I think you're using that - can you review? 13:20:49 I would prefer a variable there, on not that huge deployments this will stretch upstart time if something is wrong with the service unit 13:21:02 I'll review it, yes :) 13:21:07 nice, thanks 13:21:08 thank you! :) 13:22:12 one advice: did you talk to upstream neutron-openvswitch-agent people if they think they can speed it up? 13:22:24 because this is really a workaround for a process taking 3 minutes to start 13:22:48 smells to me like there could be some code improvement be made on the neutron side? 13:23:08 s/start/sync/ 13:23:33 https://review.opendev.org/c/openstack/kolla/+/924332 - for stopping publish jobs on zed 13:24:19 ok then 13:24:23 should we wrap up? 13:24:48 SvenKieske: i am building my own images ..so i don't care 13:25:03 So I guess we should wrap up :) 13:25:11 Thank you all for coming - see you next week 13:25:13 #endmeeting