09:01:00 #startmeeting magnum 09:01:00 Meeting 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:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:00 The meeting name has been set to 'magnum' 09:01:05 #link https://etherpad.opendev.org/p/magnum-weekly-meeting 09:01:08 Please put your topics into to Agenda 09:01:11 #topic Roll Call 09:01:13 o/ 09:01:18 o/ 09:01:31 mnasiadka: courtesy ping :) 09:04:41 hm let's start without him. I think he'll join later 09:06:07 #topic Announcements 09:06:19 https://releases.openstack.org/caracal/schedule.html 09:06:46 Caracal-3 milestone and Feature freeze 09:07:08 is next week. So this week we will need to prioritise anything that we want to get in this cycle 09:07:28 especially deprecations, cos those need to sit for at least 1 cycle 09:07:36 feature freeze next week; hmm I need to get back to that control plane resize spec! 09:07:47 sorry, got distracted 09:08:27 do we have deprecation patchsets proposed this cycle that need attention? 09:08:33 please help check under the couch cushions for any reviews that might be missed 09:08:46 hmm, I can't think of any now, I will ping 09:08:57 (if I find any) 09:08:59 deprecations? we deprecated nearly all drivers 09:09:16 and I think we have patches from dropping everything apart heat 09:09:28 we could have a look at any labels if we still need them 09:09:45 yes, thanks for linking those removals in agenda; i need to look at them and review. 09:10:01 I think there's atomic still too, but I can do that 09:10:17 ah right 09:10:23 yes thanks for the great work with ironic, coreos dropping mnasiadka 09:10:45 well, everyone likes to remove some files every now and then ;-) 09:11:20 you're a net positive in my books, mnasiadka. Even if not in LoC 09:11:32 haha, thanks :) 09:11:59 removing lines should count for more effort than adding lines. any monkey can add lines. 09:12:31 (they don't have to work...) but removing... people get mad if things break :) 09:13:05 ok let's get on to next item 09:13:13 #topic Review Action Items 09:13:26 Delete trusts https://review.opendev.org/c/openstack/magnum/+/905032 09:14:03 dalees: thanks for this. I had a question - do you know when trusts are not deleted? 09:14:37 yes, 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:51 you mentioned in your commit "Not every cluster will clean up trusts, even though they are always created." 09:15:19 yeah, there are two code paths to delete completion; one had the delete trusts in it, and another conductor code path didn't. 09:15:41 I see, may be helpful to have that in commit message 09:15:57 i think it was a periodic update that affected the outcome. 09:16:13 Yes, good point. Once I review and reply I will update the commit message too 09:16:17 I do see trusts building up in my DB although I haven't dug too deeply (like you have), so I would appreciate understanding why 09:16:34 but... if it is too difficult or takes too much time, you don't have to answer 09:16:59 it's good to go in. 09:17:07 is there anything else re this? since you added that topic? 09:17:09 all good, I'll update it tomorrow! 09:17:17 Do we need a periodic job to compare trusts with existing clusters to clean up old trusts that accumulated on environments? 09:17:35 no nothing else on it, just needed review attention ;) 09:18:05 mnasiadka: that's interesting; the trusts are created in the `magnum` domain.... 09:18:26 hmm I would say it is a good idea yet I am scared. :P 09:18:58 maybe a CLI once-off, not a periodic. 09:19:23 I think would be good as a `magnum-manage` kind of tool 09:19:44 (and let the operator decide if the output was trustworthy or worth actioning) 09:20:17 that's how nova does it too for purging old records 09:20:32 there isn't such a thing in magnum yet so it'll be something new. 09:21:08 i 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:31 I'd like to visit that sometime, but not right now. 09:23:16 yeap cool. let's go on to the next review? 09:23:34 ok 09:23:41 Drop fedora ironic driver https://review.opendev.org/c/openstack/magnum/+/907319 09:23:46 Drop coreos driver https://review.opendev.org/c/openstack/magnum/+/907300 09:24:44 I've reviewed those, appreciate another pair of eyes :) 09:24:48 nothing else from me 09:25:19 sounds like a job for me; i'll add myself to them. 09:26:05 thanks :) 09:26:16 Update OCCM registery https://review.opendev.org/c/openstack/magnum/+/909344 09:27:56 a 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 CT 09:28:40 DON'T BREAK PRODUCTION is rule number 1 in my books :) 09:29:24 but 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 moved 09:30:35 k, seems sensible. If it only breaks older than 1.24 then that's fine for Magnum C 09:30:50 guess 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 warning 09:32:04 I would like it to be a bigger (more generic) announcement than for these labels, cos flannel faces the same issue too. 09:32:57 so 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 of 09:33:52 of 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 one 09:35:22 comments? 09:35:53 ok - 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:36:39 yeah it doesn't affect Nectar too, but I am just concerned for others 09:37:30 I think mnasiadka would prob be ok with this since he has +2. I will add reno to that review 09:37:36 next 09:38:02 yeah, that looks ok 09:38:24 jakeyip: did you want +w https://review.opendev.org/c/openstack/magnum/+/905032 - or is there a reason we're holding from this? 09:39:05 ^ for that, I'll answer Jake's Q tomorrow and update the commit message. 09:39:20 so hold +w for a day 09:39:27 mnasiadka: holding off until dalees have a chance to update commit message. if dalees can't remember then he can +w :) 09:40:39 #agreed Change 'policy' to allow update defaults for labels if it blocks progress. 09:41:10 #action jakeyip to update reno for https://review.opendev.org/c/openstack/magnum/+/909344 with decision 09:41:26 ok, continuing on 09:41:29 Switch Calico deployment to Helm chart https://review.opendev.org/q/topic:%22calico-helm%22 09:41:41 dalees: how is calico working for you? cos it isn't working in CI 09:42:29 well, I'm using much newer manifests than in Magnum upstream. 09:42:30 I assume StackHPC has those patches to make it work. 09:43:19 manifests? can contribute? 09:44:28 yeah, 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 size 09:46:25 ok. after that is done can you look at the contributed ones, one of them is to remove calico_v3_3 09:47:09 I'll check, but I've got a manifest for Calico 3.13, 3.23 and 3.26 that we're using. 09:47:12 hm, 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:39 Yeah, 3.3 is not so helpful, but maybe it need to stay and we just add one newer to Magnum. 09:49:12 ok. I can send in a deprecation reno for that, get it in before next week. 09:49:27 #action jakeyip deprecate calico 3.3 09:50:00 calico 3.12 was tested on k8s 1.14 through 1.17. So 3.3 must be quite old 09:50:30 yeah I'm not sure if anyone is using it 09:51:22 let's go with deprecation reno first, if we change our mind we can update the reno 09:52:20 3.3 only matches 3.3 09:52:24 and nothing else ;-) 09:53:32 mnasiadka: ? 09:54:02 If we're talking about the patch dropping calico_v3_3 ,,matcher'' 09:55:24 and surely calico v3.3 is not tested against any new Kubernetes release 09:55:34 basically what we have in Caracal now won't work for anybody 09:55:34 ah yeah 09:56:10 mnasiadka: I had a bunch of comments on Jakub patches 09:56:21 are those comments in Gerrit? ;-) 09:56:25 yeah 09:56:46 ok, we'll have a look - but probably in a day or two 09:57:27 the 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:58:01 if we don't remove calico_v3.3 - we can't remove the whole manifest and convert to do Helm chart 09:58:39 for subsequent changes that uses Calico helm chart, probably next cycle looking at LoC. would need dalees input too 09:59:29 let me update the patch now 10:00:44 hm, 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:59 there's a change in the chain that might need discussion to - remove tiller. https://review.opendev.org/c/openstack/magnum/+/908414/1 10:01:44 Michal Nasiadka proposed openstack/magnum master: Removing legacy calico v3.3 https://review.opendev.org/c/openstack/magnum/+/908407 10:02:32 And I'll add a reno in some minutes 10:02:41 but yes, the removal of calico-service.sh was not intentional 10:03:14 dalees: 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:45 jakeyip: Helm2 and Tiller are deprecated since Nov 2020 (https://helm.sh/blog/helm-v2-deprecation-timeline/) 10:04:07 I 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:05:01 jakeyip: yep, we might be able to have some label magic that allows that. let's see 10:05:34 I think our goal was to do that once, instead of updating the manifest when even a minor bump to Calico would be required 10:05:56 And we're close to the Heat content limit, so it might be tight... 10:06:28 we need to dump the deadweight :) 10:06:37 *looks for things to throw overboard* 10:07:05 haha 10:07:20 mnasiadka: thanks for updating that patch. :) 10:07:53 mnasiadka: yeah I don't think anyone will be using Tiller code anymore. dalees ? 10:08:08 haha, no. tiller can go 10:08:13 also, 1 cycle or straight removal? 10:09:18 oh man we are past time. anyone needs to go? 1 more point left 10:09:37 i'm sleepy, but i can stay a bit ;) 10:09:45 thanks, appreciate it 10:10:00 ok let's talk about last thing 10:10:15 beta feature - should it go in this cycle? 10:10:42 it was meant to use to mark StackHPC CAPI driver as beta, so it won't be loaded. And have to be explicitly enabled 10:11:07 even if we don't use it - I guess it's a shame to not merge it 10:12:11 yeah, if it's ready it seems reasonable to merge 10:12:44 one less thing to line up merging of, if we need it. 10:13:37 hm 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 freeze 10:14:23 OH WAIT I forgot most important patch 10:14:31 Add feature to specify driver explicitly https://review.opendev.org/c/openstack/magnum/+/907297 10:14:52 this one NEEDS +2 this cycle 10:15:05 dalees: wake up :P 10:15:07 yes, that is more important ;) 10:15:34 my list of things to review is getting quite long 10:16:10 bump this to the top :P 10:16:20 *pushes the stack of paper off the table* 10:16:57 * dalees converts List to FIFO 10:16:59 mnasiadka: need to upgrade to +2 too if you can :) 10:17:30 remove that space in reno and I can :D 10:18:17 ah! :) 10:18:37 good call. 10:19:33 ok. nothing else from me. there's a bunch of misc reviews that mnasiadka can hopefully get to, trival things 10:19:44 anything else ? 10:20:03 I've read that patch and like it; so review and then +2 won't be long coming. 10:22:49 Yeah, I'll have a look in the review queue and also work on some improvements in CI 10:22:51 Jake Yip proposed openstack/magnum master: Add feature to specify driver explicitly https://review.opendev.org/c/openstack/magnum/+/907297 10:23:14 ok let's end this meeting 10:23:23 #endmeeting