14:00:57 #startmeeting kolla 14:00:57 Meeting started Wed Aug 10 14:00:57 2022 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:57 The meeting name has been set to 'kolla' 14:01:09 #topic rollcall 14:01:10 o/ 14:01:12 now \o/ 14:01:31 o/ 14:01:43 hi 14:03:14 #topic agenda 14:03:14 * Announcements 14:03:14 * Review action items from the last meeting 14:03:15 * CI status 14:03:15 * Release tasks 14:03:16 * Current cycle planning 14:03:16 * Additional agenda (from whiteboard) 14:03:18 * Open discussion 14:03:19 #topic announcements 14:03:26 PTG in October is virtual - https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029879.html 14:03:47 #topic Review action items from the last meeting 14:03:49 frickler check availability of zed UCA for Jammy 14:04:30 hrw answered that immediately 14:04:39 ok then 14:04:42 so next up is creating the actual patch 14:04:55 frickler: are you planning to do that? 14:05:14 I can do that, yes 14:06:22 thanks 14:06:29 #topic CI status 14:06:54 seems mainly green 14:07:06 #topic Release tasks 14:07:45 It's R-8 - Switch images to current releaseĀ¶ 14:08:01 Ubuntu UCA is part of that 14:08:18 CentOS Stream 9 is not really working IIRC 14:08:25 And we should really be working on Rocky Linux 9 14:08:45 I'll take care of that based on CS9 patches 14:08:58 #topic Additional agenda (from whiteboard) 14:09:10 (headphoneJames) please review let's encrypt patch: https://review.opendev.org/c/openstack/kolla-ansible/+/741340 14:09:28 Is there any core reviewer interested in testing and reviewing let's encrypt patch? Or even a non-core? 14:10:38 Ok, we're a bit limited on the meeting today - I'll re-ask that next week. 14:11:00 (frickler) Using octavia_network_type: "tenant" in production 14:11:00 Why are our docs telling people not to do this? https://docs.openstack.org/kolla-ansible/wallaby/reference/networking/octavia.html#development-or-testing 14:11:00 Introduced in https://review.opendev.org/c/openstack/kolla-ansible/+/783876 14:11:00 Octavia proposes the same setup in their install guide without any warning https://docs.openstack.org/octavia/latest/install/install-ubuntu.html#prerequisites 14:11:10 I would like to test LE, one day 14:11:39 I think at the time of merging that feature - we did anticipate that the systemd unit with a shell script might just fail sometimes, and we did not want users coming back and complaining 14:12:12 If somebody wants to raise a patch to change the ,,recommendation'' - please do - I guess it should be ok. 14:12:12 indeed 14:12:13 so for me, the thing one could consider not fit for production is using dhcp for the interface 14:12:27 a static configuration would be more stable 14:12:48 but the current wording suggests that tenant networks are somewhat unstable 14:13:04 so I'll make a patch to update the doc, fine 14:14:02 just wanted to hear whether there's any hidden reasoning I'm not aware of 14:14:20 frickler: are you planning to add static ip configuration as well? 14:16:32 mnasiadka: maybe later, not now 14:16:36 ok 14:16:40 next one 14:16:50 (frickler) ceph-ansible has been un-deprecated (kind of) 14:16:50 https://github.com/ceph/ceph-ansible/commit/77fc0e105efaaa8a47e0d6f5676c01b2f674230f 14:16:50 should we consider switching the CI back to it? 14:16:50 not an urgent topic, maybe punt to PTG discussion 14:17:20 yeah, we still use ceph-ansible for osism and CI for cephadm seems to be failing a lot 14:17:28 When it comes to me - I'm not a fan of ceph-ansible, and I can't see a reason why we would be going back to use it in CI instead of cephadm (especially that ceph-ansible readme points to use cephadm). 14:17:40 I think me and Radek put enough hours, to make cephadm green again. 14:18:00 well currently I'm seeing a lot of failures for it 14:18:14 but if you prefer to stick to it, I won't object 14:18:43 just won't be able to help as much in maintaining it 14:20:01 anyway, we can discuss again when yoctozepto is back possibly 14:20:11 Today it seems green, yesterday there were some failures - but it's not always cephadm fault I guess. 14:20:35 I'll try to take a look later. 14:21:14 next one 14:21:19 (i.halomi) Podman and systemd support status 14:21:19 review of systemd with docker a current status on podman version : https://review.opendev.org/c/openstack/kolla-ansible/+/816724 14:21:19 problems with using podman-py 14:21:19 review status of kolla-build with podman support : https://review.opendev.org/c/openstack/kolla/+/828716/ 14:21:19 future testing of Podman functionality in Zuul 14:22:11 our podman version is almost ready 14:22:18 but we have one problem with podman-py module 14:22:35 it doesnt accept empty environment variables and it deletes them 14:23:17 it creates problem in creating haproxy monitor user in mariadb where he has no password at default, can we add there some dummy password to solve this? 14:25:45 Well, that would be a separate change not only affecting podman 14:25:47 mgoddard: ideas? 14:26:29 i created issue in podman-py community so there is chance they will solve it but they didnt respond yet 14:29:11 well, the alternative to wait is to set dummy password for mariadb monitor user - are you planning to send that patch for review? 14:29:45 can we translate them to empty strings? 14:30:56 it might be we could alter mariadb-clustercheck script to send empty password if variable is unset? 14:31:11 but we would need to move the code into kolla repository 14:31:33 so should i create patch for only this password change? 14:32:05 that's the workaround I guess, unless you're willing to patch that in podman-py and there's a chance it will be merged there soon 14:33:23 i am waiting for their response but i dont think i will have time to patch it myself 14:34:08 well, you know what are the options now :) 14:35:41 ok, let's move on 14:35:43 #topic Open discussion 14:36:27 (I skipped the Current Cycle Planning, but there were two features to discuss from the Additional Agenda - and I don't think we have the audience to discuss more of them today) 14:36:37 Anybody has any additional topics/queries? 14:37:09 Did anyone take a look at Systemd patch failures, and if yes, can give some hints about what's wrong? 14:37:37 any chance to look at my reviews? orpphan interfaces cleanup for example 14:38:35 One failed at cache fail and other at couldn't had connection closed 14:39:01 So I suspect the problem might not be on the patch side 14:39:11 or repos.yaml for Kayobe? 14:40:23 links would be helpful 14:40:42 https://review.opendev.org/c/openstack/kayobe/+/845338 14:40:51 https://review.opendev.org/c/openstack/kayobe/+/840033 14:40:55 Systemd: https://review.opendev.org/c/openstack/kolla-ansible/+/816724 14:41:23 or even old TSL sync K-A to Kayobe 14:41:29 https://review.opendev.org/c/openstack/kayobe/+/793697 14:42:52 oh, that's all kayobe, I don't do that, but will look at the other one later 14:43:04 thanks a lot 14:43:33 I'll try to look at Kayobe ones next week most probably 14:43:54 mgoddard could You please look? You should be familar with issues 14:44:27 mnasiadka thanks too 14:44:53 m_hiner: on 5th Aug we merged some cephadm related patches, rebase/recheck so we have fresh results 14:45:21 Oh okay, thanks 14:45:29 And I'll look into the results once they show up 14:45:41 ok, I think that's enough for today 14:45:47 Thanks! 14:45:49 #endmeeting