15:00:13 #startmeeting kolla 15:00:13 Meeting started Wed Oct 13 15:00:13 2021 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:13 The meeting name has been set to 'kolla' 15:00:14 It may be possible to do software raid on root FS via bifrost 15:00:21 #topic rollcall 15:00:23 @priteau, thanks. 15:00:42 \o 15:00:58 o/ 15:01:15 o/ 15:01:41 o/ 15:01:58 Michal Nasiadka proposed openstack/kolla-ansible master: Tidy up renos before Xena release https://review.opendev.org/c/openstack/kolla-ansible/+/813788 15:02:15 Michal Nasiadka proposed openstack/kolla-ansible master: Tidy up renos before Xena release https://review.opendev.org/c/openstack/kolla-ansible/+/813788 15:02:21 o/ 15:03:24 hello 15:04:04 #topic agenda 15:04:08 * Announcements 15:04:08 ** Ussuri goes to Extended Maintenance in 1 month (2021-11-12) http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025276.html 15:04:08 * Review action items from the last meeting 15:04:08 * CI status 15:04:08 * Release tasks 15:04:10 * Xena cycle planning 15:04:10 * Yoga PTG planning 15:04:12 * Open discussion 15:04:44 #topic Announcements 15:04:54 Ussuri goes to Extended Maintenance in 1 month (2021-11-12) 15:04:59 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025276.html 15:05:48 So it will join Rocky++ club 15:06:08 Using the opportunity - do we want to EOL any branches? 15:07:21 mgoddard, yoctozepto? 15:07:43 last eol was queens 15:07:49 so rocky could be a candidate 15:07:56 +1 15:08:34 Yes, that sounds like a good approach. 15:09:00 #topic Review action items from the last meeting 15:09:44 mnasiadka to run through the release checklist 15:10:06 in progress - kolla-ansible tidy renos patch being reviewed, then I'll propose rc1 for Kolla and Kolla-Ansible 15:10:16 and then move on with Kayobe as agreed 15:10:32 mgoddard to update release docs to reflect Kayobe should be branched/cut RC1 after we have Kolla/Kolla-Ansible RC1s 15:10:36 That's also done 15:10:46 #topic CI status 15:11:23 yoctozepto: how are we with those Galera failures? 15:11:39 mnasiadka: no progress; frickler to hold a node to see if service restart helps 15:11:51 ok then 15:11:56 any other CI issues we know of? 15:12:07 seemingly it works more often than not outside of CI 15:12:13 but can break still 15:12:17 I guess 15:12:38 as always 15:12:42 yup 15:12:45 but it's not a release blocker as I understand 15:12:47 ah, I have a set of 3 held nodes, but didn't get to look at them yet 15:13:09 yoctozepto: remind me of your ssh key, then I'll get you access 15:13:56 ok, let's move on 15:13:59 #topic Release tasks 15:14:06 That's taken care of, 15:14:13 #topic Xena cycle planning 15:14:17 That's too late for that :-) 15:14:24 #topic Yoga PTG planning 15:14:39 #link https://etherpad.opendev.org/p/kolla-yoga-ptg 15:14:49 Please post your topics, PTG is next week 15:15:27 last chance to discuss before the PTG 15:16:08 https://etherpad.opendev.org/p/kolla-yoga-ptg 15:16:48 frickler: https://api.github.com/users/yoctozepto/keys 15:17:16 hello, are we in open discussion topics ? 15:17:27 hi alecorps, not yet 15:17:32 ok sorry 15:17:48 np 15:17:56 are there any topics which need more details? 15:17:56 ok then, I guess no pre-PTG discussion items ;-) 15:19:47 I should fill in more info about podman 15:20:00 also, is there any reading we need to do before the PTG? 15:20:12 e.g. review the podman patch 15:20:19 Around multiple environments - can we have a summary what is there now, and what are next steps? 15:21:43 I've added myself a todo 15:22:00 Has anyone looked at the podman patch? 15:22:10 I did 15:22:19 I talked with ohorecny as well 15:22:28 I added also a todo to populate Xena PTG Actions 15:22:31 but not checked recently 15:23:02 my take is to make it work with the current ansible code and do the heavier lifting behind the scenes :-) 15:23:53 are there comments in the patch that explain what that means? 15:25:18 Do I see that correct it doesn't use systemd units for running container images? 15:26:20 wow, that's some monster patch 15:26:23 Merged openstack/kolla stable/ussuri: neutron: Fix update-alternatives on CentOS https://review.opendev.org/c/openstack/kolla/+/813305 15:26:24 mgoddard: yes, there were there 15:26:32 ok, I need to read 15:26:33 frickler: yup, /me trying to make it simpler 15:26:40 mgoddard: ++ 15:26:57 mnasiadka: did not check recently, might not be doing that yet 15:27:20 it would be good to review it before Tuesday then 15:27:30 we are targetting Tuesday, right? 15:27:49 well, we should analyze that patch - and maybe agree on the best approach forward (e.g. if we want to use systemd, other decisions) during the PTG 15:29:04 So yes, it's the time to add more descriptions to each item this week 15:30:26 Do we have any additional topics around the PTG - or should we move to open discussion? 15:31:16 I don't; I will be mostly offering my knowledge and insight on the proposed topics this time, not having many of my own 15:33:33 I will probably find some that might be interesting but not picked up in previous cycles (as ,,backup'' to discuss if we'll feel it makes sense) 15:34:21 added some comments also :P 15:35:15 kevko: will you attend the PTG? 15:36:08 mgoddard: probably yes 15:36:20 kevko: good. Please add your name to the etherpad 15:36:36 kevko: it's a good place to discuss features that you're working on or would like to work on 15:36:45 mgoddard: but I am not sure, it depends on my internet connection ..i will be on vacation 15:36:54 ah 15:37:08 well don't ruin your holiday for it ;) 15:37:12 mgoddard: but probably i will 15:37:39 kevko: ruin or attend? :) 15:37:42 mgoddard: well, i really need to move on with my patches ...I am still rebasing and keeping them live ..because we are using them from stein ... 15:38:01 mgoddard: especially logging, proxysql, mariadb-arbitrator 15:38:10 attend :D 15:38:30 (and working very well :/) 15:38:54 already open discussion ? 15:38:56 mgoddard: https://review.opendev.org/c/openstack/kolla-ansible/+/813788 - and I'll post rc1 patches to releases repo 15:39:09 ok then, let's move to open discussion 15:39:14 #topic Open discussion 15:39:24 alecorps: you had something? 15:39:34 yes 15:39:42 I'm looking for two reviews for the two belows gerrit reviews : 15:39:42 https://review.opendev.org/c/openstack/kolla-ansible/+/807404 15:39:42 https://review.opendev.org/c/openstack/kolla-ansible/+/808760 15:39:50 maybe you can help me ? 15:41:59 Unfortunately we're beyond the point we could review them and merge them in Xena 15:42:26 but we are known to backport small features 15:42:31 just need to wait until we stabilise 15:42:58 ok 15:43:14 I just want to be sure the pr will not be abandonned 15:44:09 I would like to ask why there is such big preasure to remove binary packages .. 15:44:25 alecorps: if you could add them on the whiteboard on the end of Xena priorities list - we'll remember to review that 15:44:33 alecorps: https://etherpad.opendev.org/p/KollaWhiteBoard 15:44:39 ok I will 15:44:42 thanks 15:45:02 kevko: it's not pressure, but an open discussion on the PTG 15:45:14 i know there are problems with it ... but i think option is to drop all meta packages and just install source code (from a package) 15:45:28 mnasiadka: yeah, but it is discussion from version to version :) 15:45:58 yes, we've had that discussion last time - we're just a limited group with many things to maintain 15:46:43 I am DD in debian, so if found some bug fixed in master ..i am patching it as fast as I can ..also CVEs and such .. when i have source i can't do it .. 15:47:02 and most people use source, because most openstack projects are not really good at posting minor releases 15:47:11 i can for example use some git with my source ..but i can't handle requirements for example ..they are installed from pip 15:47:30 if it's binary ..i just fix it with patch in debian .. (or in local apt repo for example ..) 15:48:22 kevko: in Debian it might be simple for you, but there are are distributions - where it's really simple to do it source 15:48:37 well, centos has something similar nope ? 15:48:49 i mean ..patches for packages 15:49:10 kevko: what you describe as needed is even simpler for me to do with source; we might perhaps want to focus on making kolla have better flows and guidelines for your needs 15:49:19 but otherwise source are *more* flexible 15:49:21 not less 15:50:37 is there a way to patch things that are installed from pypi? like the recent suds-jurko for example? 15:50:55 kevko: most people that use binary rely on RDO/UCA/Debian OpenStack to deliver packages, and at least RDO and UCA post new OpenStack packages versions only when there's a minor release - which doesn't happen often for some projects (but bugs are fixed in stable/xena for example) 15:51:19 but yes, I agree with yoctozepto - we should gather stories/scenarios from users and help them with describing a workflow 15:51:44 Merged openstack/kolla-ansible master: Add support for Ironic inspection through DHCP-relay https://review.opendev.org/c/openstack/kolla-ansible/+/813268 15:51:46 and fixing what doesn't work + updating docs with how to handle different situations 15:51:47 Merged openstack/kolla-ansible master: Tidy up renos before Xena release https://review.opendev.org/c/openstack/kolla-ansible/+/813788 15:51:56 yoctozepto: ok, consider that some service, binary, library, whatever has dependency to some library and its upper-constraints is X.X.X ... but X.X.X is buggy ..and fix is in Y.Y.Y ..but that service, binary, library is not compatible with Y.Y.Y because it is major change ...but buggy thing is only in one line for example ... how i can fullfill this with source ? 15:52:54 and library Y.Y.Y is non-openstack ..and author will not fix X.X.X+1 version 15:53:29 kevko: for that we need a special workflow in kolla and I would prefer to work on that so that all users benefit 15:53:47 frickler: I think kevko's issue matches your question ^ 15:54:02 yes 15:54:10 you could fork the code, and install from git 15:54:16 in package you just take a diff from Y.Y.Y version (even if whole code is completly different..you just pick one line diff ..add to package ..rebuild image ) 15:54:58 mgoddard: might be tricky with arbitrary deps 15:55:11 good discussion topic nonetheless 15:55:25 let's add this for the PTG 15:55:30 @mnasiadka: added in the whiteboard 15:55:35 hope it's ok for you 15:55:40 mgoddard: yeah, and this is the way, add possibility to override any source library,app whatever 15:55:48 alecorps: thanks, will check and adapt if needed 15:57:31 mgoddard: but you have to implement whole process of deliver that forked git ..what about dependencies ? .. c libraries, gcc and others if there will be some source which will need it ? in my example this is solved on deb/centos builder machine 15:58:54 also, is there some statistics how many users are using binary/source ? 15:59:24 because I think most binary users are not downloading images from kolla officially ..they just building them .. as me 16:00:38 the numbers on Docker Hub are similar, but that might also mean the only user is CI :) 16:00:44 ok, let's finish the meeting 16:00:46 let's discuss during the ptg 16:00:46 #endmeeting