09:02:17 #startmeeting magnum 09:02:17 Meeting started Wed May 8 09:02:17 2024 UTC and is due to finish in 60 minutes. The chair is jakeyip. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:02:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:02:17 The meeting name has been set to 'magnum' 09:02:21 #link https://etherpad.opendev.org/p/magnum-weekly-meeting 09:02:30 o/ 09:02:49 #topic Roll Call] 09:02:53 #topic Roll Call 09:02:55 o/ 09:02:55 o/ 09:03:00 \o 09:03:10 eager today dalees :) 09:03:30 haha, I'm actually only here once not twice. 09:03:41 #topic review 09:04:50 I have gone thru some of the magnum-ui. I am not super good at -ui so I won't be able to catch mistakes. I'll just +1. 09:05:18 I hope mnasiadka will help to +2 and you should be free to merge from there. 09:05:21 is that ok? 09:05:38 thanks jakeyip - we can fix them if they arise but still useful to read and run them to try it out once they all merge 09:06:27 I'm ok with that; I feel good about the changes but don't promise 0 bugs. mnasiadka has raised a good point on one, so I split that part out to separate changeset. 09:07:03 cool. good work there :) . my main aim is not block it. 09:07:25 floating_ip vs master_lb_floating_ip_enabled has always confused me a bit, so maybe that's could affect others if they rely on previous behaviour. 09:08:41 ricolin was pinged for the kubeconfig action button change, so perhaps he can help review/test there. 09:08:44 I was under the impression it follows CLI but then again the CLI doesn't make sense 09:09:47 I find the X-enabled / X-disabled redundant, I think I raised it before but was overruled 09:10:57 consistency is more important, but perhaps that's not there either ;) 09:12:23 anyway, thanks for the time on the ui reviews. Sorry there are lots, but hopefully things look+work better in that dept :) 09:12:26 'master' is a contriversial term in master_lb_floating_ip_enabled though :) 09:13:58 in the same review you renamed the master -> control plane yet called this master_lb_floating_ip_enabled ... hah 09:14:28 I'm only changing UI visible strings, not label names or the API at this stage. 09:15:08 those probably need a spec and a deprecation period 09:16:11 yeah I know... 09:17:07 I don't think I have any questions at this point 09:17:20 I'll bring them up in reviews or at next meeting if I have any 09:17:32 ok 09:18:51 I sent up some easy ones, please take a look 09:19:53 Jake Yip proposed openstack/python-magnumclient master: Update Python runtime for 2024.2 https://review.opendev.org/c/openstack/python-magnumclient/+/918507 09:20:34 any more reviews? 09:21:16 https://review.opendev.org/c/openstack/python-magnumclient/+/918507 https://review.opendev.org/c/openstack/magnum/+/918506 09:21:44 that's all immediate ones for now, I'll have a look at those others - if you could link into meeting agenda 09:23:16 ok I want to talk about the versioning for capi though 09:23:21 #topic capi 09:23:45 any thoughts about tags / version for magnum-capi-helm and magnum-capi-helm charts? 09:25:01 do you mean whether they follow the opendev cycles or their own releases? 09:25:52 we have marked them as independent. just need to come up with our own versions now 09:26:20 Add magnum-capi-helm deliverables as independent https://review.opendev.org/c/openstack/releases/+/910299 09:26:29 right, cool 09:27:17 I'll have a look in the ui changes today 09:27:42 The plan for magnum-capi-helm is to add first release notes and prelude and release 1.0.0 09:27:47 and start bumping versions from there 09:27:54 I'll try to find time for that next week 09:28:54 mnasiadka: can we tag 0.x for it for now? it will help us branch it and start testing patches on nectar 09:30:28 FYI for Nectar we carry our own branches with patches. Some repos we branch off a tag and have our patches on them. Then when next tag is done we branch again and cherry-pick patches still needed 09:31:09 I was planning on following stackhpc tags for now, 09:31:23 but there is now an issue where magnum-capi-helm has diverged 09:33:10 https://github.com/stackhpc/magnum-capi-helm vs https://github.com/openstack/magnum-capi-helm 09:33:14 we follow a similar model, and we'll be looking to update our branch really soon. Looking forward to 1.0.0! 09:33:39 dalees: do you now follow openstack/ or stackhpc/ ? 09:34:08 Sooner we do 1.0.0 and switch to that, the better - the stackhpc repo will be retired after that 09:34:49 ok I think maybe not worth solving magnum-capi-helm for now, since 1.0.0 is almost here 09:34:59 internally we just choose a tag and branch, no big deal 09:35:14 how about magnum-capi-helm-charts? 09:35:17 jakeyip: we havn't synced except to cherry pick in some fixes. so stackhpc for now, but we'll switch this upcoming sync, i think 09:36:22 dalees: ok, may be helpful if you can make sure your cherry-picks are in openstack/magnum-capi-helm before we cut 1.0.0 :) 09:37:18 yep, coming around to do that soon. cut 1.0.0 anyway, ours can come in soon - most are already there. 09:38:33 ok. for magnum-capi-helm-charts I am working with infra to push 09:38:35 https://review.opendev.org/c/openstack/project-config/+/918287 09:39:25 dalees: what do you do for this repo? 09:40:34 this is where most of our internal changes are (eg. to ignore keypairs, set defaults), so we do the same thing - branch and cherrypick our carried changes over that are still relevant. 09:41:33 but again, we've not sync'd fully in a month or two. Coming back soon to catch up and do this in a couple weeks 09:41:37 ok. I suspect I shouldn't wait for upstream then, will just branch in nectar 09:42:10 dalees: did you create any tests? I was trying to get some test working from github actions -> zuul 09:45:37 not fully automated on commit, we tag and that triggers a push to an OCI registry - after which we can build a template and run our cluster build and functionality tests. 09:46:06 and ours are gitlab; so - yet another CI :D 09:47:03 dalees: was thinking of lint or chart-testing (what stackhpc uses) 09:47:24 gate basically 09:47:45 no, check I mean 09:49:54 nah, we just make MR to stackhpc's repo ;) will need them in the zuul tests! 09:50:39 yeah ok then I guess I'll continue working on that then :) 09:51:58 dalees: one more question - do you build images or packages? 09:53:19 jakeyip: for what? 09:53:42 for magnum 09:54:00 container images, with openstack-loci 09:56:16 ok. thanks. 09:56:20 nothing else from me 09:56:30 dalees / mnasiadka: you have anything else? 09:56:44 nope 09:56:45 one question 09:57:30 at some stage, I want to change the Magnum API response for `nodegroup show` to include server uuids of nodes in that group. Will this need a spec? 09:58:52 I assume you're planning to introduce a new API microversion - did we ever have specs for that in the past? 10:01:59 yeah, that's probably the way to do it. I'll have a look and see, there aren't many specs created. 10:02:51 I'm not a fan of paperwork, but spec may help in firming your thoughts and for discussion. 10:03:56 ok - it'll also provide a place to explain "why" 10:04:04 more than a commit message, anyway 10:04:30 that's all then, thanks 10:04:32 yeah 10:04:41 cool 10:04:49 #endmeeting