Wednesday, 2024-02-21

jakeyiphi all, meeting in 15 mins. please populate the agenda https://etherpad.opendev.org/p/magnum-weekly-meeting08:46
jakeyipmnasiadka / dalees around?08:48
mnasiadkaI'm here08:49
daleesYep, around.08:49
jakeyipcool08:51
jakeyip#startmeeting magnum09:01
opendevmeetMeeting started Wed Feb 21 09:01:00 2024 UTC and is due to finish in 60 minutes.  The chair is jakeyip. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
opendevmeetThe meeting name has been set to 'magnum'09:01
jakeyip#link https://etherpad.opendev.org/p/magnum-weekly-meeting09:01
jakeyipPlease put your topics into to Agenda09:01
jakeyip#topic Roll Call09:01
jakeyipo/09:01
daleeso/09:01
jakeyipmnasiadka: courtesy ping :) 09:01
jakeyiphm let's start without him. I think he'll join later09:04
jakeyip#topic Announcements09:06
jakeyiphttps://releases.openstack.org/caracal/schedule.html 09:06
jakeyipCaracal-3 milestone and Feature freeze09:06
jakeyipis next week. So this week we will need to prioritise anything that we want to get in this cycle09:07
jakeyipespecially deprecations, cos those need to sit for at least 1 cycle09:07
daleesfeature freeze next week; hmm I need to get back to that control plane resize spec!09:07
mnasiadkasorry, got distracted 09:07
daleesdo we have deprecation patchsets proposed this cycle that need attention?09:08
jakeyipplease help check under the couch cushions for any reviews that might be missed09:08
jakeyiphmm, I can't think of any now, I will ping09:08
jakeyip(if I find any)09:08
mnasiadkadeprecations? we deprecated nearly all drivers09:08
mnasiadkaand I think we have patches from dropping everything apart heat09:09
mnasiadkawe could have a look at any labels if we still need them09:09
daleesyes, thanks for linking those removals in agenda; i need to look at them and review.09:09
jakeyipI think there's atomic still too, but I can do that09:10
mnasiadkaah right09:10
jakeyipyes thanks for the great work with ironic, coreos dropping mnasiadka09:10
mnasiadkawell, everyone likes to remove some files every now and then ;-)09:10
daleesyou're a net positive in my books, mnasiadka. Even if not in LoC09:11
mnasiadkahaha, thanks :)09:11
jakeyipremoving lines should count for more effort than adding lines. any monkey can add lines.09:11
jakeyip(they don't have to work...) but removing... people get mad if things break :) 09:12
jakeyipok let's get on to next item09:13
jakeyip#topic Review Action Items09:13
jakeyipDelete trusts https://review.opendev.org/c/openstack/magnum/+/90503209:13
jakeyipdalees: thanks for this. I had a question - do you know when trusts are not deleted?09:14
daleesyes, I saw your question but need to get the code back into my head to reply. I'll do this tomorrow (only had 1/2 day today).09:14
jakeyipyou mentioned in your commit "Not every cluster will clean up trusts, even though they are always created."09:14
daleesyeah, there are two code paths to delete completion; one had the delete trusts in it, and another conductor code path didn't.09:15
jakeyipI see, may be helpful to have that in commit message09:15
daleesi think it was a periodic update that affected the outcome. 09:15
daleesYes, good point. Once I review and reply I will update the commit message too09:16
jakeyipI do see trusts building up in my DB although I haven't dug too deeply (like you have), so I would appreciate understanding why09:16
jakeyipbut... if it is too difficult or takes too much time, you don't have to answer09:16
jakeyipit's good to go in.09:16
jakeyipis there anything else re this? since you added that topic?09:17
daleesall good, I'll update it tomorrow!09:17
mnasiadkaDo we need a periodic job to compare trusts with existing clusters to clean up old trusts that accumulated on environments?09:17
daleesno nothing else on it, just needed review attention ;)09:17
daleesmnasiadka: that's interesting; the trusts are created in the `magnum` domain....09:18
jakeyiphmm I would say it is a good idea yet I am scared. :P 09:18
daleesmaybe a CLI once-off, not a periodic.09:18
jakeyipI think would be good as a `magnum-manage` kind of tool09:19
dalees(and let the operator decide if the output was trustworthy or worth actioning)09:19
jakeyipthat's how nova does it too for purging old records09:20
jakeyipthere isn't such a thing in magnum yet so it'll be something new. 09:20
daleesi think it's worth recording that idea, we havea a lot of old trusts too. They aren't too harmful, but would be nice to clean them up after this bug is sorted out.09:21
daleesI'd like to visit that sometime, but not right now.09:21
jakeyipyeap cool. let's go on to the next review?09:23
daleesok09:23
jakeyipDrop fedora ironic driver https://review.opendev.org/c/openstack/magnum/+/90731909:23
jakeyipDrop coreos driver https://review.opendev.org/c/openstack/magnum/+/90730009:23
jakeyipI've reviewed those, appreciate another pair of eyes :)09:24
jakeyipnothing else from me09:24
daleessounds like a job for me; i'll add myself to them.09:25
jakeyipthanks :)09:26
jakeyipUpdate OCCM registery https://review.opendev.org/c/openstack/magnum/+/90934409:26
jakeyipa bit of history - as you may know, we don't prefer to update tags, etc. this is due to the CT design - if a CT doesn't have a certain label and Magnum changes the default, that will potentially break the CT09:27
jakeyipDON'T BREAK PRODUCTION is rule number 1 in my books :) 09:28
jakeyipbut having said that, now that we have good tests for new versions of Kubernetes, we will need a change to pull in newer versions of OCCM, as the registry has moved09:29
daleesk, seems sensible. If it only breaks older than 1.24 then that's fine for Magnum C09:30
jakeyipguess what this comes down to is a decision to change this 'policy', and supplement this change with reno, etc, so operators upgrading will have a warning09:30
jakeyipI would like it to be a bigger (more generic) announcement than for these labels, cos flannel faces the same issue too.09:32
jakeyipso a big generic announcement that - "Magnum Core Team is not keeping labels static anymore", then we don't have to create reno for each label we change the default of09:32
jakeyipof cos it doesn't mean we go all crazy updating all labels, we only do for those that are seriously holding us back in the beginning. like this one09:33
jakeyipcomments?09:35
daleesok - i don't have a big opinion on this. We override nearly every label and mirror all the images so we also set CONTAINER_INFRA_PREFIX :)09:35
jakeyipyeah it doesn't affect Nectar too, but I am just concerned for others09:36
jakeyipI think mnasiadka would prob be ok with this since he has +2. I will add reno to that review09:37
jakeyipnext09:37
mnasiadkayeah, that looks ok09:38
mnasiadkajakeyip: did you want +w https://review.opendev.org/c/openstack/magnum/+/905032 - or is there a reason we're holding from this?09:38
dalees^ for that, I'll answer Jake's Q tomorrow and update the commit message.09:39
daleesso hold +w for a day09:39
jakeyipmnasiadka: holding off until dalees have a chance to update commit message. if dalees can't remember then he can +w :) 09:39
jakeyip#agreed Change 'policy' to allow update defaults for labels if it blocks progress.09:40
jakeyip#action jakeyip to update reno for https://review.opendev.org/c/openstack/magnum/+/909344 with decision09:41
jakeyipok, continuing on09:41
jakeyipSwitch Calico deployment to Helm chart https://review.opendev.org/q/topic:%22calico-helm%2209:41
jakeyipdalees: how is calico working for you? cos it isn't working in CI09:41
daleeswell, I'm using much newer manifests than in Magnum upstream.09:42
jakeyipI assume StackHPC has those patches to make it work.09:42
jakeyipmanifests? can contribute? 09:43
daleesyeah, I can. The calico_tag is used to switch which manifest is included. There's a limit though to how many Calico versions you can have supported, because they're big and overload Heat template size09:44
jakeyipok. after that is done can you look at the contributed ones, one of them is to remove calico_v3_3 09:46
daleesI'll check, but I've got a manifest for Calico 3.13, 3.23 and 3.26 that we're using.09:47
jakeyiphm, does that need deprecation cycle. it's very old. deferring to both of you, since you are more experienced with calico. (I run flannel)09:47
daleesYeah, 3.3 is not so helpful, but maybe it need to stay and we just add one newer to Magnum.09:47
jakeyipok. I can send in a deprecation reno for that, get it in before next week.09:49
jakeyip#action jakeyip deprecate calico 3.3 09:49
daleescalico 3.12 was tested on k8s 1.14 through 1.17. So 3.3 must be quite old09:50
jakeyipyeah I'm not sure if anyone is using it09:50
jakeyiplet's go with deprecation reno first, if we change our mind we can update the reno09:51
mnasiadka3.3 only matches 3.309:52
mnasiadkaand nothing else ;-)09:52
jakeyipmnasiadka: ?09:53
mnasiadkaIf we're talking about the patch dropping calico_v3_3 ,,matcher''09:54
mnasiadkaand surely calico v3.3 is not tested against any new Kubernetes release09:55
mnasiadkabasically what we have in Caracal now won't work for anybody09:55
jakeyipah yeah 09:55
jakeyipmnasiadka: I had a bunch of comments on Jakub patches09:56
mnasiadkaare those comments in Gerrit? ;-)09:56
jakeyipyeah 09:56
mnasiadkaok, we'll have a look - but probably in a day or two09:56
jakeyipthe very first patch in the chain is removing calico_v3.3. . if he doesn't get to it by feature freeze we will merge the reno and leave it for next cycle. is that ok?09:57
mnasiadkaif we don't remove calico_v3.3 - we can't remove the whole manifest and convert to do Helm chart09:58
jakeyipfor subsequent changes that uses Calico helm chart, probably next cycle looking at LoC. would need dalees input too09:58
mnasiadkalet me update the patch now09:59
daleeshm, yeah i'll look more. I'm not too keen on the helm chart for our use, as the static manifest for calico 3.26 is enough to see us through to the End of Heat.  but I don't want to prevent others using/merging it.10:00
jakeyipthere's a change in the chain that might need discussion to - remove tiller. https://review.opendev.org/c/openstack/magnum/+/908414/1 10:00
opendevreviewMichal Nasiadka proposed openstack/magnum master: Removing legacy calico v3.3  https://review.opendev.org/c/openstack/magnum/+/90840710:01
mnasiadkaAnd I'll add a reno in some minutes10:02
mnasiadkabut yes, the removal of calico-service.sh was not intentional10:02
jakeyipdalees: also wonder if helm chart will break your patches. please help to check. I will be able to know more when you send it up.10:03
mnasiadkajakeyip: Helm2 and Tiller are deprecated since Nov 2020 (https://helm.sh/blog/helm-v2-deprecation-timeline/)10:03
jakeyipI guess the ideal situation is that we can carry both helm chart and static manifests so neither one of you have to carry those patches any more :) 10:04
daleesjakeyip: yep, we might be able to have some label magic that allows that. let's see10:05
mnasiadkaI think our goal was to do that once, instead of updating the manifest when even a minor bump to Calico would be required10:05
mnasiadkaAnd we're close to the Heat content limit, so it might be tight...10:05
jakeyipwe need to dump the deadweight :) 10:06
jakeyip*looks for things to throw overboard*10:06
mnasiadkahaha10:07
jakeyipmnasiadka: thanks for updating that patch. :) 10:07
jakeyipmnasiadka: yeah I don't think anyone will be using Tiller code anymore. dalees ?10:07
daleeshaha, no. tiller can go10:08
jakeyipalso, 1 cycle or straight removal? 10:08
jakeyipoh man we are past time. anyone needs to go? 1 more point left10:09
daleesi'm sleepy, but i can stay a bit ;)10:09
jakeyipthanks, appreciate it10:09
jakeyipok let's talk about last thing10:10
jakeyipbeta feature - should it go in this cycle? 10:10
jakeyipit was meant to use to mark StackHPC CAPI driver as beta, so it won't be loaded. And have to be explicitly enabled10:10
mnasiadkaeven if we don't use it - I guess it's a shame to not merge it10:11
daleesyeah, if it's ready it seems reasonable to merge10:12
daleesone less thing to line up merging of, if we need it.10:12
jakeyiphm ok. thanks for the input. I was pretty keen to merge it because it's useful. I might try to clean it up a bit to see if I can make it to feature freeze10:13
jakeyipOH WAIT I forgot most important patch10:14
jakeyipAdd feature to specify driver explicitly https://review.opendev.org/c/openstack/magnum/+/90729710:14
jakeyipthis one NEEDS +2 this cycle10:14
jakeyipdalees: wake up :P 10:15
daleesyes, that is more important ;)10:15
daleesmy list of things to review is getting quite long10:15
jakeyipbump this to the top :P 10:16
jakeyip*pushes the stack of paper off the table*10:16
* dalees converts List to FIFO10:16
jakeyipmnasiadka: need to upgrade to +2 too if you can :) 10:16
mnasiadkaremove that space in reno and I can :D10:17
jakeyipah! :) 10:18
jakeyipgood call.10:18
jakeyipok. nothing else from me. there's a bunch of misc reviews that mnasiadka can hopefully get to, trival things10:19
jakeyipanything else ?10:19
daleesI've read that patch and like it; so review and then +2 won't be long coming.10:20
mnasiadkaYeah, I'll have a look in the review queue and also work on some improvements in CI10:22
opendevreviewJake Yip proposed openstack/magnum master: Add feature to specify driver explicitly  https://review.opendev.org/c/openstack/magnum/+/90729710:22
jakeyipok let's end this meeting10:23
jakeyip#endmeeting10:23
opendevmeetMeeting ended Wed Feb 21 10:23:23 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:23
opendevmeetMinutes:        https://meetings.opendev.org/meetings/magnum/2024/magnum.2024-02-21-09.01.html10:23
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/magnum/2024/magnum.2024-02-21-09.01.txt10:23
opendevmeetLog:            https://meetings.opendev.org/meetings/magnum/2024/magnum.2024-02-21-09.01.log.html10:23
jakeyipthanks everyone for coming.10:23
jakeyipthanks dalees for staying up :) 10:23
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: CI: Wait for pods to exit ContainerCreating state  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/90831011:04
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: Add pods description in logs  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/90944411:04
opendevreviewMerged openstack/magnum master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/magnum/+/90952111:19
opendevreviewJake Yip proposed openstack/magnum master: Add feature to specify driver explicitly  https://review.opendev.org/c/openstack/magnum/+/90729711:21
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: CI: Wait for pods to exit ContainerCreating state  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/90831012:42
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: CI: Wait for pods to exit ContainerCreating state  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/90831014:55
opendevreviewMerged openstack/magnum master: Drop k8s_coreos_v1 driver  https://review.opendev.org/c/openstack/magnum/+/90730023:50
opendevreviewMerged openstack/magnum master: Drop k8s_fedora_ironic_v1 driver  https://review.opendev.org/c/openstack/magnum/+/90731923:52

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