| dalees | hello, anyone around for the meeting this evening? | 08:00 |
|---|---|---|
| dalees | (or morning) | 08:00 |
| jakeyip | hi dalees I am here | 08:03 |
| dalees | hi jakeyip , well let's start a meeting and see where we get to. | 08:03 |
| dalees | #startmeeting magnum | 08:03 |
| opendevmeet | Meeting started Tue Feb 17 08:03:41 2026 UTC and is due to finish in 60 minutes. The chair is dalees. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:03 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:03 |
| opendevmeet | The meeting name has been set to 'magnum' | 08:03 |
| dalees | #topic roll call | 08:03 |
| dalees | o/ | 08:03 |
| jakeyip | o/ | 08:03 |
| dalees | anyone else? | 08:05 |
| dalees | #topic open discussion | 08:05 |
| dalees | nothing particular on the agenda; did you have anything to bring up, Jake? | 08:06 |
| mnasiadka | Hola! | 08:06 |
| dalees | hi mnasiadka | 08:06 |
| jakeyip | hi mnasiadka | 08:06 |
| mnasiadka | I’m still off, but will be back in March - just lurking :) | 08:06 |
| jakeyip | I don't have much, need to talk abt PTL? | 08:09 |
| BigMax | Good morning o/ | 08:09 |
| dalees | Yes sure; two things about PTL - firstly thanks for putting your name forward mnasiadka for next cycle. | 08:10 |
| mnasiadka | No problem :) | 08:11 |
| dalees | secondly, I'm moving on from my current role in a couple of weeks and won't have time for Magnum contributions. Do you want to pick up the PTL role early, mnasiadka ? | 08:11 |
| mnasiadka | Yes, that’s fine | 08:12 |
| mnasiadka | dalees: is there anybody picking up your old role at Catalyst and we should expect them being active here? | 08:12 |
| dalees | thank you, are you okay with mnasiadka picking up PTL for the remainder of this cycle, jakeyip ? | 08:13 |
| jakeyip | yes definitely | 08:13 |
| dalees | mnasiadka: unsure at this stage, mattnorthcott who contributed a feature last year will hopefully make more appearances in patchsets. | 08:14 |
| jakeyip | catalyst will still be running magnum? | 08:15 |
| dalees | #action dalees to pass PTL to mnasiadka for remainder of this cycle, over the next week or two. | 08:16 |
| jakeyip | I wonder how to attract more ops | 08:16 |
| dalees | jakeyip: yes, definitely | 08:16 |
| dalees | jakeyip: yeah, it's tricky. I will try and encourage them to join in. Timezones are one thing (it's 9pm) but also the priority of features vs upgrades/ops. | 08:19 |
| jakeyip | dalees: not saying catalyst, but operators of clouds in general. surely can't be catalyst, nectar, stackhpc running magnum? | 08:19 |
| mnasiadka | Running magnum-capi-helm rather | 08:20 |
| mnasiadka | And I can’t promise helm charts from Azimuth will be the same quality, since johnthetubaguy is moving on as well | 08:21 |
| mnasiadka | I think we need to be more integrated with other drivers out there to have a connection to users | 08:21 |
| jakeyip | i wonder how vexxhost is doing | 08:23 |
| jakeyip | mnasiadka: how's the future for magnum-capi-helm looking? should we look at magnum-cluster-api too? | 08:25 |
| mnasiadka | I have no clue, but I think magnum-cluster-api has more traction in the wider community | 08:26 |
| dalees | seems to, though only a few companies contributing to its development. I see Vexxhost and BBC | 08:27 |
| mnasiadka | I’ll try to get more people working on capi-helm in SHPC, but it won’t help getting it more widely adopted, just a bit more maintained | 08:27 |
| jakeyip | well, every project has issues, but it's better tackled together than separately | 08:27 |
| dalees | the magnum-capi-helm driver is fairly stable. There are certainly features I'd like to add, but they are also for Magnum core. Otherwise the charts are the things that need maintenance now, to keep them moving and relevant. | 08:28 |
| mnasiadka | Well, obviously ideally we should have one driver that fits all, but that’s not the case | 08:28 |
| jakeyip | dalees: hm, true, I wonder if vexxhost also suffers from the nodegroups issues | 08:30 |
| mnasiadka | jrosser: around? How’s your experience with magnum-cluster-api? ^^ | 08:31 |
| mnasiadka | I think SCS also ships with magnum-cluster-api but they are not active here | 08:34 |
| dalees | jakeyip: which nodegroups issues? I know there are some just wondering which you mean. | 08:35 |
| jakeyip | the big effort to make nodegroups be able to inherit and have separate labels, instead of using clusters' | 08:36 |
| dalees | oh yes, I see. mutable labels being the other feature goal, that that would help enable. | 08:39 |
| jakeyip | yeah it's a core piece I think | 08:42 |
| jakeyip | anyway, not your problem now I think! :P | 08:43 |
| jrosser | mnasiadka: andrewbonney is doing a lot of work here with magnum-cluster-api, maybe can comment more accurately than me | 08:43 |
| andrewbonney | aside from specifics it's working for us at present. we have some current issues moving forward with upgrades due to deployment assumptions in the driver which we've reported upstream | 08:47 |
| opendevreview | Grzegorz Bialas proposed openstack/magnum-capi-helm master: Add config to add helm values https://review.opendev.org/c/openstack/magnum-capi-helm/+/951966 | 08:50 |
| dalees | jakeyip: no I won't be continuing now, but I'll pass my PoC on. I don't think it's the right Magnum to Driver interface yet but perhaps I should upload to gerrit anyway as 'draft' or 'closed' so it exists somewhere. | 08:54 |
| jakeyip | dalees: yeah title with WIP is good too, we may be able to pick it up. | 08:55 |
| dalees | also that helm config patch would be good to get some eyes on, it would have helped with a recent issue where k8s dashboard helm chart repo moved locations. | 08:55 |
| dalees | helm config patch: https://review.opendev.org/c/openstack/magnum-capi-helm/+/951966 | 08:56 |
| * dalees will close the meeting shortly. | 08:59 | |
| dalees | thanks for joining and coding with us! | 09:02 |
| dalees | #endmeeting | 09:02 |
| opendevmeet | Meeting ended Tue Feb 17 09:02:12 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:02 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/magnum/2026/magnum.2026-02-17-08.03.html | 09:02 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/magnum/2026/magnum.2026-02-17-08.03.txt | 09:02 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/magnum/2026/magnum.2026-02-17-08.03.log.html | 09:02 |
| opendevreview | Nikita Vokhmintsev proposed openstack/magnum master: resolve resource names to UUIDs when creating cluster templates https://review.opendev.org/c/openstack/magnum/+/971393 | 09:06 |
| jakeyip | thanks dalees . hm interesting, it's either use that patch, or roll a new CT with the updated values and upgrade clusters to it? | 09:06 |
| dalees | jakeyip: injecting helm config overrides in lets you make customisations to values without actually forking and publishin your own charts (we do, it's okay with some pipelines). However the k8s dashboard would have required us to change every published chart. Adding a helm values override would have let us fix it in a Magnum config file. | 09:08 |
| jakeyip | how many charts will need to be changed in your env? and they should be updated anyway? is this a temp patch thing while those charts are rebuild or will you carry this change for a long time? | 09:12 |
| jakeyip | sorry, it's a bunch of Q, can answer another day, I know it's late on your end | 09:12 |
| dalees | it's a good question though. We'll carry it for now, and just remove it when we remove k8s dashboard in k8s v1.35. so it'll phase out. Not many really installed it except our CI, which started failing. | 09:13 |
| dalees | the issue, in case you didn't encounter: https://github.com/azimuth-cloud/capi-helm-charts/issues/652 | 09:14 |
| dalees | (by CI I meant Tempest, which runs regularly) | 09:15 |
| * dalees departs for now. Happy to reply to other things tomorrow! | 09:16 | |
| mnasiadka | andrewbonney: do you have some link to that report? | 09:56 |
| andrewbonney | sure, original report in https://github.com/vexxhost/magnum-cluster-api/issues/868, which is now covered by https://github.com/vexxhost/magnum-cluster-api/issues/881 | 09:57 |
| mnasiadka | andrewbonney: ah, that,s interesting - probably comes from the fact that vexxhost runs their stack inside a k8s cluster | 10:07 |
| andrewbonney | yes, we assumed the same | 10:11 |
| opendevreview | Nikita Vokhmintsev proposed openstack/magnum master: resolve resource names to UUIDs when creating cluster templates https://review.opendev.org/c/openstack/magnum/+/971393 | 10:20 |
| jrosser | mnasiadka: something that vexxhost have put a lot of effort into is getting magnum-cluster-api into the community deployment tools | 11:42 |
| jrosser | i think that this is probably why from an ops/end user perspective there seems to be a lot of traction. certainly from an OSA point of view its just working out-of-the-box, including deployment of the management k8s cluster | 11:43 |
| mnasiadka | jrosser: maybe in OSA and OSH case, but not really in K-A case | 11:43 |
| mnasiadka | But yes, I agree | 11:44 |
| jrosser | whilst i have little/no experience with the stackhpc one, my impression is you need to have more in depth k8s understanding as an operator to get things working | 11:44 |
| mnasiadka | I would like them to be more part of the community, instead of being a bit outside, but that will probably include cooperation in other direction | 11:45 |
| jrosser | andrewbonney has been looking at what we have already got in OSA to re-use for deploying the stackhpc driver | 11:45 |
| jrosser | it looks like relatively little change on top of what we have already | 11:45 |
| mnasiadka | well, it's not really stackhpc driver, because it's in opendev and has some contributions from other companies | 11:46 |
| jrosser | yes of course | 11:46 |
| mnasiadka | But I think first we need magum-core running CI against these two drivers, which I'll work on in the coming cycle | 11:46 |
| jrosser | yeah | 11:47 |
| jrosser | its not just the driver tbh | 11:47 |
| jrosser | having some good story about connectivity between the management cluster and workload clusters is very important for us | 11:47 |
| jrosser | i.e real world architecture rather than devstack | 11:48 |
| jrosser | i put a lot of effort into making that be sensible https://github.com/openstack/openstack-ansible-ops/tree/master/mcapi_vexxhost | 11:49 |
| mnasiadka | jrosser: well, devstack still is better than assuming your openstack services run in the same kubernetes cluster | 12:43 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!