Wednesday, 2024-02-28

opendevreviewMichal Nasiadka proposed openstack/magnum master: Removing Tiller support  https://review.opendev.org/c/openstack/magnum/+/90841407:00
opendevreviewJake Yip proposed openstack/magnum master: Update cloud-provider-openstack registry  https://review.opendev.org/c/openstack/magnum/+/90934407:59
jakeyiphi all meeting in ~5 mins08:55
jakeyip#startmeeting magnum09:00
opendevmeetMeeting started Wed Feb 28 09:00:35 2024 UTC and is due to finish in 60 minutes.  The chair is jakeyip. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
opendevmeetThe meeting name has been set to 'magnum'09:00
jakeyip#link https://etherpad.opendev.org/p/magnum-weekly-meeting09:00
jakeyip#topic Roll Call09:00
jakeyipo/09:00
mnasiadkao/09:00
daleeso/09:00
opendevreviewMerged openstack/magnum-tempest-plugin master: CI: Wait for pods to exit ContainerCreating state  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/90831009:00
opendevreviewMerged openstack/magnum-tempest-plugin master: Add pods description in logs  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/90944409:01
jakeyipopendevreview came for meeting :) 09:01
jakeyipalright let's crack on09:01
jakeyip#topic Feature Freeze09:02
jakeyipFeature Freeze this week, any patches that needs to go in and I haven't put in the agenda? please add and ping09:02
jakeyipanything else to discuss for feature freeze?09:03
daleesI still hope to revisit control plane resizing this week. Just finished other up with other work. https://review.opendev.org/c/openstack/magnum/+/90608609:03
daleesbut maybe it will miss the freeze09:03
mnasiadkaI think would be nice to get Calico in09:04
mnasiadkabut that's a chain of patches09:04
jakeyipdalees: ah that one. yeah you had a question about validation, I found a good place. take a look at the comments and see if it works?09:05
mnasiadka#link https://review.opendev.org/q/topic:%22calico-helm%2209:05
daleeson the topic of calico, sorry i've not uploaded the static manifest patchset for that yet. I prefer it over the helm chart and operator as it's easier to mirror.09:05
jakeyipmnasiadka: calico is on the agenda :) 09:05
daleesjakeyip: yes, thank you! that's what i need to revisit09:06
jakeyiplet's skip to calico since we are on it already :) 09:06
mnasiadkadalees: there's one more image to mirror, I can post some docs to it - or ideally we could have a tool that lists images you need to mirror09:06
opendevreviewMichal Nasiadka proposed openstack/magnum master: Removing Tiller support  https://review.opendev.org/c/openstack/magnum/+/90841409:07
jakeyipok seems like we don't have enough info to make decision one way or another09:08
jakeyipwe don't use calico so I need to eval dalees to decide.09:08
jakeyipdalees: on that topic - so you will still be using your patches if we get mnasiadka's helm version in?09:09
daleesmnasiadka: not sure that's true; it's pulling helm charts from the internet and `curl` from internet urls. That adds dependencies to cluster spin up.09:09
daleesjakeyip: yes, so while i'm wary of the extra internet dependencies, we'll just continue to use manifests with our carried for the remaining lifetime of our Heat clusters.09:10
mnasiadkadalees: interesting, I can have a look - but Helm chart gives us support for multiple versions without need to update manifests09:11
daleesso i'm not sure i need to add requirements to these calico that don't need to affect me.09:11
jakeyipdalees: I am curious if we merge this, how much will it affect you carrying those patches?09:11
jakeyipI'm concerned if there are deployments carrying their own calico like you, and this is a breaking change for them09:12
daleesi think we'd need to disable this new script and instead include the static calico manifest that matches `calico_tag`, yeah.09:13
mnasiadkaI'm fine with carrying that one downstream with us, as long as we'll get rid of Tiller ;-)09:14
jakeyipmnasiadka: I think we may have to do that for now, until we have more time to evaluate Calico better09:14
daleesno issues removing tiller, and installing helm in the proposed way :)09:15
mnasiadkagoodie09:15
jakeyipI am not in a good position to do it as we don't carry patches to handle calico, so I'm blind09:15
jakeyipprobably dalees and mnasiadka collaborate more on that next cycle? I will help.09:15
mnasiadkanext cycle we should rather deprecate Heat driver ;-)09:16
jakeyipwell if we can get magnum-capi-helm in, then heat still needs to stay at least 1 cycle :P09:16
jakeyipI like your ambition mnasiadka :P 09:17
jakeyipso Tiller will go, that's decided.09:18
jakeyipHelm move? https://review.opendev.org/c/openstack/magnum/+/908423 09:18
mnasiadkaand hopefully https://review.opendev.org/c/openstack/magnum/+/908423 as well09:18
opendevreviewMichal Nasiadka proposed openstack/magnum master: Move Helm client install to separate script  https://review.opendev.org/c/openstack/magnum/+/90842309:19
opendevreviewMichal Nasiadka proposed openstack/magnum master: Calico deployment with Tigera Operator  https://review.opendev.org/c/openstack/magnum/+/90850109:19
jakeyip#topic Calico09:19
jakeyip#agreed Remove Tiller this cycle09:19
mnasiadkadalees: will you submit the manifest update so users get something working out of the box?09:19
daleesmnasiadka: yeah, cool; If my comments block the helm installed calico then I owe that this week09:21
daleesit'd be nice to have either and default to manifest, but not sure how right now.09:21
mnasiadkawe could have a label calico_use_helm09:22
mnasiadkaor something like that09:22
mnasiadkaand default to false09:22
mnasiadkaif you update the manifest in a separate change - I can rebase the Helm one and add a label09:22
jakeyipthere's no way to make the current https://review.opendev.org/c/openstack/magnum/+/908501/14/magnum/drivers/common/templates/kubernetes/fragments/calico-service.sh work at all? 09:23
mnasiadkathere is, we need to update the manifest to newer version09:24
jakeyipe.g. certain calico_tag, etc?09:24
daleesjakeyip: I think that one is old; so I'll propose a newer manifest to replace and lock the manifest to a certain `calico_tag`. 09:24
mnasiadkaproblem is, it won't support the current default calico_tag I think09:24
mnasiadkaand we have the Heat data limit - so we can't really have two big manifests09:25
jakeyipdalees: cool09:25
daleesyeah, we can only embed ~2 calico manifests. the Helm install really helps there09:26
mnasiadkaI think the easiest way forward is to bump the calico_tag default to something that works with 1.28 or whatever we claim is supported in docs09:27
mnasiadkaor tested09:27
mnasiadkasecond thing is, I think we need a note in the docs that we don't test/support EOL versions of Kubernetes, so if it doesn't work - then it doesn't work09:28
mnasiadkabut I'll leave the manifest update to dalees ;-)09:29
jakeyipmnasiadka: yeah I put something like that in the reno for occm change09:30
jakeyipanyway the change with reno has been +w :) 09:31
jakeyipso calico last bumped to 3.21.2 in yoga. https://review.opendev.org/c/openstack/magnum/+/779378 09:31
jakeyipat that time we were testin with k8s v1.2309:31
jakeyipso I guess it must be newer k8s broke it09:31
daleesoh that's not too old. I'll have a try with it and add a new version at least, anyway.09:32
daleesmaybe it is too old, but it's not as old as i thought ;)09:33
jakeyipit may have been one of those breaking changes 1.21 -> 1.23 -> 1.2509:33
mnasiadka#link https://docs.tigera.io/calico/latest/getting-started/kubernetes/requirements#kubernetes-requirements09:33
mnasiadkahere they claim they only really test latest versions09:33
jakeyipyeah it's prob not worth debugging and if we can replace the manifest with something that works with k8s v1.27 it will be the easiest09:34
mnasiadka+109:35
daleesyep +109:35
jakeyip#agreed Push Calico Helm to next cycle09:36
jakeyip#action dalees to send up newer calico manifest09:36
jakeyippossibly will miss feature freeze ^09:37
jakeyiplet's get on to next, can't worry about that too much for now09:37
jakeyip#topic Beta Drivers09:37
jakeyipBeta drivers https://review.opendev.org/q/topic:%22beta_driver%2209:37
jakeyipit's clean to go in now. not 100% sure of usefulness given the drama and uncertainty. last week we agreed no harm putting it in for this cycle09:38
jakeyipstill agreeable?09:39
jakeyipit may be a useful tool next cycle merging magnum-capi-helm09:39
mnasiadkaif we want to merge it09:40
mnasiadkaI don't like the drama, and I mentioned I also like the idea of driver being independent (so master branch and tags only) - as long as it's properly tested in CI09:40
opendevreviewMerged openstack/magnum master: Update cloud-provider-openstack registry  https://review.opendev.org/c/openstack/magnum/+/90934409:40
mnasiadkaWe're not really good in backports ;-)09:40
jakeyipI think still useful even if out of tree in separate repo09:40
mnasiadkaAnd we shouldn't backport features, so always there will be some issues09:41
jakeyipbecause a packager may package the driver, then it will conflict09:41
jakeyipmnasiadka: not sure what you mean for backports?09:41
mnasiadkawell, let's assume the driver is in tree09:41
mnasiadkawe merge a feature in master09:42
mnasiadkabut we can't really backport that today in stable/2023.2 or whatever stable branch09:42
mnasiadkaso people backport that downstream anyway09:42
daleesI don't mind the beta feature going in, it looks ready. not sure if it'll be useful if drivers are out of tree, but it can be removed if it's not used.09:42
mnasiadkawith independent release cycle of a driver in a separate repo - you can get the latest and greatest driver code (as long as it passes stable Magnum CI tests)09:42
jakeyipyeah ok09:43
jakeyipit may still be useful for out of tree drivers by letting them be hidden for 1 cycle by default09:44
mnasiadkaand Kubernetes changes so often, that I'm pretty sure every new Kuberenetes version will need something in the driver09:44
jakeyipjust because https://github.com/stackhpc/magnum-capi-helm/blob/main/magnum_capi_helm/driver.py#L60-L64 still conflicts with https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/driver.py#L38909:45
mnasiadkaI'll have a look in beta drivers later, added to my review queue :)09:46
jakeyipthanks09:47
jakeyip#topic magnum-capi-helm09:49
mnasiadkaI guess I should start09:50
jakeyipyeah go for it09:50
mnasiadkaSo basically StackHPC wants to move the driver from https://github.com/stackhpc/magnum-capi-helm to OpenDev - to be an out of tree driver still, but detangle that from SHPC ownership and move under Magnum governance09:51
mnasiadkaWe will work on getting cross-repository CI working for every magnum/ and magnum-capi-helm/ change09:51
jakeyip"OpenStack" governance :) 09:52
mnasiadkaYes, OpenStack governance09:52
mnasiadkaThe driver repo would have independent release cycle - so we would just publish new versions as tags09:52
mnasiadkaAnd strive to make it working with all non-EOL/unmaintained Magnum versions09:52
mnasiadkaAnd of course add relevant documentation in both driver repo and magnum main repo09:53
jakeyipsounds like a good halfway point to me09:53
jakeyipwho will make up the magnum-capi-helm core?09:54
mnasiadkaThe regular magnum-core + current driver developers (John Garbutt and Matt Pryor) most probably09:54
mnasiadkaBut regular magnum-core only is also fine with us, since I'm a core 09:54
mkjpryorI am happy to join as a core reviewer for magnum-capi-helm09:55
mkjpryordalees: we would also like a core reviewer from Catalyst, if you or Travis are happy to do it09:55
mkjpryorTo avoid it being a single-company thing09:55
jakeyipI think it'll be good to have John and Matt as core. I will be happy to join, but they can drive the direction09:55
daleesI'd not want to lose mkjpryor's reviews, though I guess he can continue reviewing in either case.09:56
daleesmkjpryor: I'll discuss with travisholton, but I'm happy to be involved09:57
mkjpryor:thumbsup:09:57
jakeyipawesome09:58
mkjpryorSo there is also the question of the governance of the Helm charts09:58
jakeyip#agree magnum-capi-helm as an out-of-tree driver09:58
mkjpryorCurrently, although they are an open-source project, they sit in the stackhpc namespace on GitHub09:58
jakeyip#agreed magnum-capi-helm as an out-of-tree driver09:58
jakeyipdalees made a repo for it already09:59
mkjpryorThe problem with moving them is we rely very heavily on GitHub Actions for CI, and we don't have the capacity to port to Zuul right now10:00
mnasiadkaI think we could discuss the Helm charts on the PTG again10:01
daleesthe helm charts are also used in a wider scope than just the magnum-capi-helm driver, so the reviewers may need to be aware of that.10:01
mkjpryorWhat we are proposing in the interim is to create a new "azimuth-cloud" organisation on GitHub to host all the Azimuth repositories, including the capi-helm-charts, the cluster-api-addon-provider and cluster-api-janitor-openstack10:02
mkjpryordalees: we would like you or someone else from Catalyst to join this org as a maintainer or owner10:02
mkjpryorNot for all of Azimuth, obviously10:03
mkjpryorUnless you want to :-)10:03
mkjpryorBut we want to make it clear that it is not a StackHPC "product" but rather an open-source project10:03
mkjpryorWhich we provide support for10:03
daleesmkjpryor: ok, I'll discuss with others at Catalyst and get in touch.10:04
mkjpryorLooking forward, I think we are looking to contribute Azimuth and all its components to a foundation (TBC)10:04
jakeyipI am not sure if that will appease the objections. I don't really have an objection10:04
mkjpryorMy understanding is that the main objection now is not to point to a "single vendor" repository.10:05
mkjpryorIf the repository was not single vendor, and especially if it belonged to a foundation like CNCF or LF, that would be less of an issue I think?10:05
mkjpryorEven if it is not OpenInfra10:05
jakeyipI won't know, it may be good to check in with Julia first before attempting the work10:06
jakeyipas I said, I don't have an objection. my point is that there are so many images magnum uses which are 'single vendor'. this isn't any difference really.10:07
mkjpryorI guess it is actually no different to, for example, Calico in that sense10:07
jakeyipmaybe they just want it mirrored or something, so in case stackhpc delete the original repo, the mirror still exists10:07
mnasiadkaI think the difference is those images/Helm charts/manifests are for 'addons', which some Helm charts are basically driver mechanics (like the one used to create a Kubernetes cluster)10:07
mkjpryorTrue10:08
mnasiadkaThat's why for me it's a PTG item - maybe we could split out the ,,core'' Helm charts required for the driver somewhere10:08
mkjpryorThe alternative would be to move the capi-helm-charts, cluster-api-addon-provider and cluster-api-janitor-openstack under OpenStack governance as "part of" Magnum10:09
mnasiadkamagnum-capi-helm-charts repo is there already, but I think we'll tackle that after handling the driver code move10:09
mkjpryorIt would be possible to have a version of the Helm charts that doesn't use the addon provider, if we think that is best10:09
mkjpryorThe addon handling would be worse, but I guess it becomes an optional thing10:10
mnasiadkaMight be, I think we're already over time10:10
jakeyipI am concerned with the github actions. will they eventually be movable? 10:10
mnasiadkaThey will be complicated, especially if the repo uses some bots to update dependency versions10:10
mkjpryorIt will be work to move10:10
jakeyipI see10:11
mnasiadkaSo I'd like to focus on moving the driver code for now and discuss if we could make the scope of magnum-capi-helm-charts repo smaller to things that do not change that often10:11
mkjpryorI agree10:11
jakeyipok I think I'd like try to wind up in the interest of time10:11
mkjpryorI think we are still going to move the Azimuth repos out of the stackhpc namespace on GitHub as well, for several reasons10:12
mkjpryorBut we should discuss at the PTG10:12
jakeyipyeap10:12
jakeyipalright any last items?10:12
mnasiadkajakeyip: can you comment and +1 the project-config/governance changes?10:12
jakeyip#agreed discuss the helm charts at the PTG10:12
jakeyipmnasiadka: yes I will. after I end this I will add the irc link ;)10:13
mnasiadkaFanstatic, thanks10:13
jakeyipcool if there's nothing else, let's end this meeting10:13
jakeyip#endmeeting10:13
opendevmeetMeeting ended Wed Feb 28 10:13:56 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:13
opendevmeetMinutes:        https://meetings.opendev.org/meetings/magnum/2024/magnum.2024-02-28-09.00.html10:13
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/magnum/2024/magnum.2024-02-28-09.00.txt10:13
opendevmeetLog:            https://meetings.opendev.org/meetings/magnum/2024/magnum.2024-02-28-09.00.log.html10:13
jakeyipthanks everyone for coming, please feel free to stay and chat10:14
daleesthanks all; sorry I won't stay - it's late :)10:14
jakeyipthanks dalees10:14
mnasiadkathanks for running the meeting :)10:16
jakeyipmnasiadka: I've +1 the project-config change :) 10:17
jakeyipmnasiadka: zuul doesn't like you on the governance https://review.opendev.org/c/openstack/governance/+/910240 or releases https://review.opendev.org/c/openstack/releases/+/910299 part10:18
jakeyipI'll +1 those after you've talked zuul around :) 10:18
mnasiadkayes, because repo is missing10:18
mnasiadkaonce project-config merges - those will be fine10:18
mnasiadkabut if you can +1 the governance patch also - that would help10:19
jakeyipyeap done10:21
jakeyipheading home :) 10:22
jakeyipalthough I've +1 project / governance, we may not hear the end of this. packagers may still complain. I think I will update with an email to them informing what is happening. let's see10:33
jakeyiptheir input is important because we have downstream users who rely on packages. 10:34
jakeyipanother downstream consumer will be kolla images :)10:35
mnasiadkaYeah, that one is covered by me10:42
opendevreviewMichal Nasiadka proposed openstack/magnum master: WIP: Test oslo.db bump  https://review.opendev.org/c/openstack/magnum/+/91050612:41
opendevreviewMichal Nasiadka proposed openstack/magnum master: WIP: Remove use of autocommit  https://review.opendev.org/c/openstack/magnum/+/91051214:21
opendevreviewDale Smith proposed openstack/magnum master: Support Calico 3.26.x  https://review.opendev.org/c/openstack/magnum/+/91055122:10

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