13:00:04 #startmeeting kolla 13:00:04 Meeting started Wed Sep 18 13:00:04 2024 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:04 The meeting name has been set to 'kolla' 13:00:17 #topic rollcall 13:00:31 o/ 13:00:31 o/ 13:00:46 o/ 13:01:00 o/ 13:01:18 o/ 13:01:22 \o/ 13:01:30 o/ 13:02:01 #topic agenda... (full message at ) 13:02:06 #topic CI status 13:02:11 Anything bleeding red? 13:02:46 Michal Arbet proposed openstack/kolla-ansible master: [CI] Add mariadb backup into mariadb scenario https://review.opendev.org/c/openstack/kolla-ansible/+/929771 13:02:57 I guess not 13:03:03 #topic Release tasks 13:03:27 It's R-2 - release in two weeks 13:03:44 I'll try to post Highlights for Kolla, Kolla-Ansible and Kayobe so marketing team is happy 13:04:24 Is feature freeze this week? 13:05:03 Yes, the docs say R-2 is Feature Freeze 13:05:18 Although freeze exception just needs two core agree on reviewing a patch 13:05:26 *two cores 13:06:56 Got you - I will start marking kayobe patches for the the release as RP+1 13:07:18 Since we have more or less 3 months to release - we need to agree if we're still going to push in Ubuntu 24.04 LTS support 13:07:35 Since it's sort of in a good condition in Kolla and Kolla-Ansible - but I didn't start anything in Kayobe 13:08:41 We don't have to do it this cycle, but I guess it would be nice to get it in 13:08:50 Anybody any strong opinions? 13:09:21 not for kayobe unfortunately :) 13:09:25 well, I've asked lastly about the k-a role patch vs kolla drop kolla-distro ...no feedback 13:09:43 Nice - anything still in flight for 24.04 in kolla/kolla-ansible or has everything landed? 13:09:56 kevko: frickler seems to be a bit off, bbezak is on sick leave - let's wait another week? 13:10:12 jovial: https://review.opendev.org/q/topic:%22kolla-ubuntu-noble%22 13:10:52 jovial: Jakub should be working on it, I assume we would need to at least see if it's trivial to get it in Kayobe or not 13:11:10 So let's check and then decide next week 13:11:19 mnasiadka: okay 13:11:35 We sort of already covered this release planning 13:11:45 #topic Additional agenda (from whiteboard) 13:12:02 jovial: Schedule data for kayobe PTG if not already discussed 13:12:19 date* 13:12:51 jovial: As I mentioned last time, Kolla PTG slots will start from Tue 22nd (because I'm coming back from US on Monday) 13:13:17 So I think we could schedule some Tue/Wed slots for Kolla and a Thu slot for Kayobe? 13:13:32 Yep, that works for me. Just wanted to get something in the diary 13:13:33 22nd October of course 13:13:47 Ok, I'll hande reserving the bot slots and creating the Etherpad 13:13:52 And send a mail to openstack-discuss 13:14:17 thanks 13:14:22 jovial: Just to announce that I have proposed to add Matt Crees as a Kayobe core on the mailing list if no one has seen the message 13:14:32 Yes, seen that, didn't have time to respond, but +1 from me 13:14:33 Piotr proposed openstack/kolla-ansible master: Gnocchi Configuration file - Deprecated: Option "enable_proxy_headers_parsing" https://review.opendev.org/c/openstack/kolla-ansible/+/929477 13:15:25 Just raising awareness... feel free to reply to the email on openstack-discuss with any comments 13:15:35 Thanks 13:15:46 That's all for additional agenda 13:15:49 #topic Open discussion 13:15:52 Anybody, anything? 13:16:02 hi, can we discuss my patch https://review.opendev.org/c/openstack/kolla-ansible/+/920377 13:17:20 I prepared some OIDC related small patches, if someone could look at those: https://review.opendev.org/c/openstack/kolla-ansible/+/928940 https://review.opendev.org/c/openstack/kolla-ansible/+/928949 13:18:13 It seams that the last question according 920377 is a documention - should we add something or not 13:18:27 chembervint: sure - from my perspective the case is clear - either we're moving the octavia interface hacky feature written for CI to production status and we rework the docs for it to sound like that - or we're keeping that for Test/Dev like it is now - and then nobody should be doing big scale in Test/Dev :) 13:20:11 please review and merge backports: https://review.opendev.org/q/(project:openstack/kolla+or+project:openstack/kolla-ansible)+(branch:unmaintained/zed+or+branch:unmaintained/yoga)+status:open 13:20:17 yoga CI fixed 13:20:19 SvenKieske, kevko any opinions on chembervint 's change? 13:20:26 mnasiadka: our customers (our customers are operators;) ) using this feature in the prod environment with a scale up to 100computes. and actually, I think it should be prod ready feature, because not all DC are ready to spread L2 between racks 13:20:45 mnasiadka: just checking ... 13:21:19 well LGTM, it's a minor detail if it's not working in all cases, we use this in prod already, documented or not :) 13:21:43 sure would be nice to have more clear docs, as always, but not a deal breaker to me. 13:21:48 mnasiadka: my opinion is that octavia stuff in kolla-ansible - i mean that part with interface etc ...is not for production ... 13:22:00 sorry, can't write that much, swamped with upgrade work 13:22:36 so leave the docs as is, merge the fix don't advertise it for prod but we still use it in prod? fine with me :) 13:22:39 That's also my problem - we're injecting a systemd unit for octavia-interface, which is if I remember correctly a bash script outside network manager or any other interface management subsystem 13:23:12 but we do this already, this is not new, is it? 13:23:27 this was meant for CI and development environments 13:23:29 on the other side, if everywhere it will be specified that it's not for production ..why not ... 13:23:54 ok then, I can live with big scale under test/dev 13:23:56 let me merge it 13:23:59 * frickler sneaks in and reads backlog 13:24:54 done 13:25:12 as for me - it could be used also for production, if we understand how to tune it (exactly what I've added to the docs) 13:25:51 Then it's the operator's responsibility. The problem is that as soon as we start investing time into similar patches, people will adopt them, and that's a path to the hell... So once again, I don't have a problem with it, but the pitfalls of this solution must be clearly described everywhere... and that it's NOTexactly ideal to use in production. 13:26:01 maybe frickler has to add something as I think he implemented the octavia interface stuff on our side :) 13:26:32 From my perspective that octavia-interface thing is more geared towards Kayobe than Kolla-Ansible 13:26:51 I mean it's easier to implement it there, maybe in NetworkManager and with static IPs 13:26:56 well it is a hacky solution, somehow abusing the neutron mechanism I think 13:26:59 and then it might be something we could recommend in production 13:27:15 But for now, it's hacky :) 13:27:27 NM is a good idea, but not all linux distros support it in the same way ... ubuntu - netplan. centos - NM .... and so on 13:27:52 yes, switching to static configuration is on our todo list for sure 13:28:36 yes, I agree, it's hacky. but as it has been discuses in the patch comments - probably we have to fix the current problem. and next think how to rework it in the master? 13:29:52 I also see that I had +2d the patch already, so seems to be fine 13:30:25 Yes, I silenced my Asperger 13:30:45 is it already time to dicsuss patches then ? :D 13:30:46 ok, unless frickler has anything else - I'd be closing the meeting :) 13:30:57 ah 13:30:59 I have something on frickler :D 13:31:08 thank you! 13:31:28 frickler: did you have time to look into kevko 's hacky lib/python linking approach vs my service role? :) 13:31:39 and one more short question - could you please push the button on the backports for merged patch? https://review.opendev.org/c/openstack/kolla-ansible/+/928077 13:31:58 mnasiadka: i will still argue that's not hacky ... symlink to directory is normal in linux 13:32:14 example :) 13:32:16 (nova-compute)[root@compute0 /]# ls -la /lib 13:32:16 lrwxrwxrwx 1 root root 7 Apr 27 02:02 /lib -> usr/lib 13:32:30 var/lib/kolla/venv/lib64 -> Points to: /var/lib/kolla/venv/lib 13:32:42 var/spool/mail -> Points to: /var/mail 13:32:52 /etc/xdg/systemd/user -> Points to: /etc/systemd/user 13:32:54 etc etc etc 13:33:12 mnasiadka: kevko: yes, I looked at it, but didn't make up my mind yet. I think kevko's solution is easier and I tend to prefer that 13:33:12 /bin -> Points to: /usr/bin 13:33:50 kevko: easy, not kilometer long monologue - we've been there already, everybody knows you want that merged 13:34:32 let frickler and others make up their mind, it's not a race 13:34:48 but i didn't want to discuss this ... i wanted to just ask to another review for https://review.opendev.org/c/openstack/kolla/+/829295 https://review.opendev.org/c/openstack/kolla/+/915440 https://review.opendev.org/c/openstack/kolla/+/929516 13:34:52 I place a vote after the meeting 13:35:19 mnasiadka: I also would like to see 24.04 support for 2024.2, do you think you could use help for that? 13:35:43 (though I'll also note that I'll be offline for some days starting tomorrow) 13:36:19 well, that symlink also helps me to have one patch for every distro as i need to patch for several customers and it's nice to has one header in patch file ... for this patch https://review.opendev.org/c/openstack/kolla/+/829295 13:37:19 geez, 211 files in one patch 13:37:39 mnasiadka: i squashed two commits into one ... 13:37:46 mnasiadka: but i can unsquash it 13:38:10 mnasiadka: all 208 files are same 13:38:24 frickler: basically kolla/kolla-ansible parts are ready - there's a bug in python3-docker in Ubuntu that is getting fixed (so we'll use noble-proposed repo for some time) - I don't think I need any more help in that, and Kayobe is rather on SHPC side 13:38:39 kevko: no need, just love going through 208 files to check if they are really the same 13:38:59 mnasiadka: don't click expand all :D 13:40:10 anyway 13:40:37 I guess we can wrap up 13:40:52 Thanks for coming - see you next week! 13:40:53 #endmeeting