Wednesday, 2023-09-13

opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313103:51
opendevreviewMerged openstack/python-magnumclient master: Use TOX_CONSTRAINTS_FILE  https://review.opendev.org/c/openstack/python-magnumclient/+/87409003:59
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313104:43
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313104:54
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313105:25
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313105:53
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313106:46
opendevreviewMerged openstack/python-magnumclient master: Remove translation sections from setup.cfg  https://review.opendev.org/c/openstack/python-magnumclient/+/72814707:04
opendevreviewMerged openstack/magnum-ui master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/magnum-ui/+/89445007:05
opendevreviewMerged openstack/magnum-ui master: Cleanup py27 support  https://review.opendev.org/c/openstack/magnum-ui/+/89062207:28
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313107:29
opendevreviewMichal Nasiadka proposed openstack/magnum master: devstack: Install sonobuoy binary  https://review.opendev.org/c/openstack/magnum/+/89382307:36
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313108:04
opendevreviewMerged openstack/python-magnumclient master: Clean up tox.ini  https://review.opendev.org/c/openstack/python-magnumclient/+/87408908:42
gbialaso/ 09:02
gbialasHi!09:02
jakeyiphiya gbialas 09:02
jakeyipwill start in a bit09:03
gbialasOk.09:04
jakeyipalright, we should be ready to start09:17
jakeyip#startmeeting magnum09:17
opendevmeetMeeting started Wed Sep 13 09:17:49 2023 UTC and is due to finish in 60 minutes.  The chair is jakeyip. Information about MeetBot at http://wiki.debian.org/MeetBot.09:17
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:17
opendevmeetThe meeting name has been set to 'magnum'09:17
jakeyip#topic Roll Call09:17
jakeyipo/09:17
daleeso/09:18
jakeyipping gbialas09:18
mkjpryoro/09:18
gbialaso/09:19
jakeyipping mnasiadka :)09:19
jakeyipThanks everyone for joining the meeting 09:19
jakeyipAgenda:09:19
jakeyip#link https://etherpad.opendev.org/p/magnum-weekly-meeting09:20
jakeyipPlease add your topics to the Agenda09:20
jakeyip#topic Changing container_runtime default09:21
gbialasYes, that is mine :) 09:21
jakeyipgbialas: let's start with this. sorry I wasn't around last week. I read thru the chat.09:21
jakeyipI agree we don't want to keep the old things around forever. In fact, I was hoping ClusterAPI solves my problem09:21
jakeyipbut unfortunately.... long story... :) 09:21
mnasiadkaIt's going to solve it in longer run09:22
gbialasWell cluster IP is song of the future, till  then we have to live with it :) 09:22
mnasiadkaBut let's try to make the current driver working out of the box without any labels ;)09:22
jakeyipyeah. maybe I should provide some context09:22
jakeyipso Antelope supports v1.23. It still works with dockershim.09:23
mnasiadkaBobcat is going to support 1.23?09:24
jakeyipduring last PTG we sort of decided not to touch labels anymore. This is to prevent the case of an operator upgrading Magnum and the default labels changing and breaking existing cluster templates that didn't define it09:25
jakeyipFor example, an site might be using a template that defaults to dockershim and if we change the runtime, an operator upgrading from Antelope to Bobcat will have it broken because maybe there are some things that expects dockershim and it was the default09:26
jakeyippersonally, I think the labels is a massive headache. therefore I was hoping CAPI will remove this altogether 09:27
mnasiadkawell, operator is upgrading to Bobcat and still wants to deploy unsupported kubernetes version?09:27
gbialasI have spawned cluster in 1.23 version, and then changed default for container_runtime. I have rescaled cluster, and it worked. 09:27
mnasiadkajakeyip: CAPI will not remove labels, we need to somehow pass additional options to the driver09:27
mnasiadkaWe could manage properly kube_version09:28
jakeyipgbialas: the existing clusters will already have the dockershim value. it is new clusters that will have the new value09:28
mnasiadkacurrently we copy kube_tag as kube_version09:28
mnasiadkaif we would know what is the major version being requested - we could do a conditional on container_runtime09:28
jakeyipmnasiadka: yes with CAPI and the CAPI labels we will be very careful not to make this mistake 09:28
jakeyipmnasiadka: kube_ver is just one, some of them may depend on fcos version, etc09:30
jakeyipe.g. use_podman label when Magnum was changing from fedora atomic to fedora coreos09:31
mnasiadkajust saying that this way we would not break any expectations09:31
mnasiadkasecond thing is - we could have a validator on kubernetes version to the ones we support09:32
jakeyipcan explain more?09:33
jakeyipgbialas any comments?09:33
jakeyipI am not objecting to changing, I am open to ideas09:33
daleesit would be nice to be able to have label defaults be "sensible" in each version and able to change. It would probably be a lot of change, but it'd help if templates stored defaults when they were created they'd not be affected by code changes of defaults.09:33
gbialas We should support some recent version (both k8s and fcos) Right now we are supporting versions which are eol. 09:33
mnasiadkadalees: don't we do that today?09:34
daleesmnasiadka: can't do, if a template is created with no labels, it'll use defaults on cluster creation. So the behaviour changes if the default in code changes.09:34
daleesthis is why label defaults are annoying; we may break old templates.09:35
mnasiadkaah, so we would need to evaluate all labels defaults and push them to the Heat stack09:35
jakeyipgbialas: we do support new versions, if you are making a new CT you have to provide the labels that will work for it. this is actually good because this CT won't follow defaults if magnum changes.09:35
jakeyipCT becomes immutable and not dependent on Magnum defaults. 09:35
daleesthe other option is to just say "we will change defaults to match k8s version X". And if the user wants to have a template that still works the same, they specify all the labels in the template (we do this at Catalyst Cloud, and are explicit about most labels)09:36
mnasiadkawell, still containerd will work with 1.23, I guess even with 1.1909:36
mnasiadkamost projects just do release notes on changed defaults09:36
jakeyipmnasiadka: not sure but we don't test it and I'm not keen to look :) 09:36
mnasiadkayeah, once we test, that it might be better :)09:38
jakeyipI like dalees idea on getting the defaults set in the CT on creation.09:38
mnasiadkaso what for now? we change the default or just write in the docs that any not EOL kubernetes version needs setting container_runtime to containerd?09:38
daleesI think that is a difficult change, the defaults live in Heat template files not python code - so I don't think you could just iterate over them and store.09:39
jakeyipthe way decided last PTG is to document it. Every version we have the tags that should be used when creating CT. That way CT stores all the info09:39
mnasiadkaok, so let's continue with that for now09:40
jakeyipI also like mnasiadka idea of eventually not providing default lol09:40
mnasiadkaYeah, maybe we should have some mandatory labels :)09:40
daleesmnasiadka: Jake is working on documenting "known good" labels for k8s versions, containerd is one of them. https://review.opendev.org/c/openstack/magnum/+/894006/2/doc/source/user/index.rst09:40
jakeyipif this problem follows us for a while (e.g. CAPI won't save us), dalees may want to explore that idea09:41
mnasiadkaok, so that probably concludes09:42
jakeyipthen we just have a breaking change behaviour version and after that all CT will suck defaults in at create time and store them. Then we are free to rachet the labels each version09:42
mnasiadkayup09:43
jakeyipgbialas: you ok with that? we don't mind help in getting a patch for this idea, then we can update labels each version09:43
gbialasYes, im ok with this. 09:44
jakeyipI've just noticed the time, let's move on quickly. gbialas do message me if you want to discuss more. Sorry to disappoint :) 09:44
jakeyip#topic Fixing meeting name09:45
gbialasIi is as it is :) 09:45
jakeyipmnasiadka: updates?09:45
mnasiadka#link https://opendev.org/opendev/irc-meetings/src/branch/master/meetings/containers-team-meeting.yaml09:45
mnasiadkahaven't raised a patch to rename it09:45
mnasiadkaI was thinking of leaving the name as is09:46
mnasiadkachanging id to magnum - so it points to correct logs on eavesdrop09:46
mnasiadkadoes it make sense?09:47
mnasiadkaor should we also rename OpenStack Containers to OpenStack Magnum?09:47
jakeyipI am not sure where the bug is actually.09:47
jakeyipis this a community thing or can both of us decide? 09:48
jakeyipor 3 of us (sorry dalees :D ) 09:48
jakeyipOH I think I understand now. because we start meeting with 'magnum'09:50
jakeyipold logs here https://meetings.opendev.org/meetings/containers/09:50
jakeyipnew logs here https://meetings.opendev.org/meetings/magnum/09:50
jakeyipam I right?09:50
jakeyipdid I lose everyone... ?09:52
* dalees is here09:54
jakeyiphm 09:54
jakeyipnvm let's go on to next topic, nearly time09:54
jakeyip#topic ClusterAPI09:54
jakeyipUpdate: We have encountered a bit of a roadblock while at the very last stage of the ClusterAPI driver. It turns out that the current implementation, contributed by StackHPC, may conflict with another driver VeXXHost developed in-house09:56
mnasiadkajakeyip: we can decide - old logs are in containers09:58
mnasiadkajakeyip: but when you write startmeeting magnum - the logs get into magnum09:58
mnasiadkajakeyip: so either we change only id, or name as well - core reviewers can decide :)09:58
jakeyipwe have discussed about this a fair bit. The biggest consideration is keeping the community happy and engaged so the project is substainable.09:58
jakeyipthanks mnasiadka, we will discuss this offline so as not to waste others' time09:59
mnasiadkajakeyip: ack09:59
jakeyipso in view of that, the current implementation in Magnum can't be merged as is10:00
jakeyipThere are a few things we will need to do10:00
jakeyip1. Find a way for both drivers to co-exist10:01
jakeyip2. Refactor the driver interface code so others can contribute out of tree drivers without conflicts10:02
jakeyip3. Possibly merge StackHPC and VeXXHost drivers so in the future there is 1 good reference CAPI driver10:03
jakeyipI think that's all, mnasiadka or dalees, do you have anything to add?10:04
daleesNo, you covered what I was going to say in #210:04
jakeyipquestions anyone? 10:05
mnasiadkanot me10:06
jakeyipmkjpryor has been strangely silent. :)10:07
jakeyipmaybe he is very disappointed10:07
jakeyipok let's move on10:09
jakeyip#topic Open Discussion10:09
jakeyipOh I noticed a BU Mentorshop Agenda. It doesn't have a name to it, do we have someone who wants to talk about that?10:10
jakeyipalright if there's nothing let's end the meeting. 10:12
mkjpryorApologies - got distracted by an urgent email10:12
jakeyipoh that's ok10:12
mkjpryorWe are currently extracting our patches into an out-of-tree driver that we will work on for the time being10:12
mkjpryorThe problem with our driver and VEXXHOST's co-existing in the same installation is that we use the same image properties to identify our drivers10:13
mkjpryorSo we would need to come up with a way out of that10:13
jakeyipyeah we've discussed about that, we will find a way around that10:14
mkjpryorMore generally, we are keen to find a way to share as much code between our driver and VEXXHOST's as possible10:14
mkjpryorBut that is probably a fair distance off at the moment10:15
jakeyipideal scenario is that a Magnum installation will be able to use any number of drivers. The ClusterTemplates will hint which driver to use.10:15
mkjpryorThat makes sense I think10:15
mkjpryorI don't really understand why it wasn't always like that, but I also wasn't using Magnum when the API was designed10:16
jakeyipmkjpryor: yes, I think that is the most helpful. we would really love if both StackHPC and VEXXHOST can work together to come up with one good reference.10:16
jakeyipthe API was designed in mesos days so things changed :) 10:16
mkjpryorWe do favour our Helm approach, TBH, as it allows us to reuse the intelligence in the Helm chart in other places, e.g. for proper gitops and in Azimuth10:16
mkjpryorI'm not sure whether VEXXHOST's objections are because we are using Helm or because we are not using ClusterClass10:17
mkjpryorFWIW, we are probably going to modify the Helm charts to use ClusterClass at some point in the next few months10:17
mkjpryorThat may bring us a bit closer10:18
dalees  mkjpryor, question for you (and I'll ask the same of Vexxhost): how open are you to contributions to your out of tree driver and helm charts? There are lots of changes we've been waiting to submit once it merges, which won't happen for a while. I believe one or two are created as PRs but had no attention.10:19
mkjpryorVery open, for us10:20
mkjpryorI did see a PR to the CAPI Helm charts for Flatcar integration10:22
jakeyipHi all, I think we can continue the CAPI discussion, but let's close the meeting10:22
mkjpryorI need to have a proper think about how we support multiple OSs there, because I'm not convinced that PR is the cleanest approach10:23
jakeyip#endmeeting 10:23
opendevmeetMeeting ended Wed Sep 13 10:23:14 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:23
opendevmeetMinutes:        https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-09-13-09.17.html10:23
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-09-13-09.17.txt10:23
opendevmeetLog:            https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-09-13-09.17.log.html10:23
jakeyipThanks everyone for coming please feel free to continue10:23
daleesno worries, cheers jakeyip 10:23
jakeyipcan post PR here please?10:24
daleeshttps://github.com/stackhpc/capi-helm-charts/pull/5310:24
jakeyipthanks dalees 10:25
daleesmkjpryor: please post comments to the PR when you have some time. It'd be great to have flatcar support10:31
mkjpryorWill do10:31
mkjpryorThe main thing I don't like about it is having ignition-specific versions of some of the properties10:32
mkjpryorIt feels like there has to be a better way10:33
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313111:26
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313112:42
opendevreviewTyler proposed openstack/magnum master: Cluster API: Implement upgrade to a new template  https://review.opendev.org/c/openstack/magnum/+/88425413:02
opendevreviewTyler proposed openstack/magnum master: Cluster API: Support basic networking parameters  https://review.opendev.org/c/openstack/magnum/+/88489113:02
opendevreviewTyler proposed openstack/magnum master: Add extra_network_name label  https://review.opendev.org/c/openstack/magnum/+/89317613:02
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313113:56
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313116:29
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313116:29
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313116:30
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313117:17
opendevreviewJake Yip proposed openstack/magnum master: Add k8s v1.26.8 and fcos 38 to docs  https://review.opendev.org/c/openstack/magnum/+/89400623:48

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!