Wednesday, 2023-08-30

jakeyipgmann: sorry missed that :( done now.00:43
jakeyipanyone good with angular can take a look at https://review.opendev.org/c/openstack/magnum-ui/+/890158 please?00:44
jakeyipI don't have angular knowledge. not sure if anyone else in Core has. if not, are we able to get other people to help, like horizon devs?00:47
daleesjakeyip: no, though google supports the fact that `success()` is deprecated in Angular and `then()` is preferred.00:59
daleesI've just made changesets to create code repository `magnum-capi-helm-chart`: https://review.opendev.org/c/openstack/project-config/+/893117 and https://review.opendev.org/c/openstack/governance/+/893118 - thanks for the examples, mnasiadka 01:00
daleeswe'll need another for releases (like example https://review.opendev.org/c/openstack/releases/+/824032 ) if it needs to be part of the deliverable, I need to figure out how publishing would work there - it doesn't go to pypi.01:02
gmannjakeyip: thanks02:54
mnasiadkajakeyip: if you're happy with it - I could add me and dalees as release liaisons - so we could also approve releases06:23
mnasiadkadalees: we could have a look how openstack-helm does that06:24
mnasiadkadalees: https://opendev.org/openstack/openstack-helm-infra/src/commit/f234218dba3cfad36513e7701cabf18a7fde217a/zuul.d/jobs.yaml#L38 - here it is06:32
mnasiadkajakeyip: I reviewed most of the secure rbac, lgtm - should we focus on merging it this week?06:33
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313107:00
jakeyipmnasiadka: yes please, I certainly don't mind having more release liaisons.07:25
mnasiadkajakeyip: https://review.opendev.org/c/openstack/releases/+/893133 - here you are ;)07:27
jakeyipmnasiadka: yes keen to move rbac, did you manage to test it out? feels better if we can have some tests07:27
mnasiadkajakeyip: I did test it out on a vm with enforce new defaults, didn't see any problems - we'll have another full cycle of new defaults enabled to fix some oddities07:28
jakeyipmnasiadka: cool. my worry was the previous experience - initially the code looked good until I tested and found certificates api was broken so the cluster can't come up.07:30
jakeyipany luck on tests :D 07:36
opendevreviewMerged openstack/magnum-ui master: sign-certificate-modal.controller.js: replace success() with then()  https://review.opendev.org/c/openstack/magnum-ui/+/89015807:48
opendevreviewMerged openstack/magnum-ui master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/magnum-ui/+/88264207:52
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313108:28
jakeyiphi, mnasiadka,dalees, all anyone around for meeting? 09:00
jakeyipagenda https://etherpad.opendev.org/p/magnum-weekly-meeting09:00
mnasiadkaI'm here09:00
daleesHello!09:01
jakeyipalrighty let's start :) 09:01
jakeyip#startmeeting magnum09:01
opendevmeetMeeting started Wed Aug 30 09:01:12 2023 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#topic Roll Call09:01
jakeyipo/09:01
daleeso/09:01
jakeyipThanks for joining the meeting 09:02
jakeyipAgenda:09:02
jakeyip#link https://etherpad.opendev.org/p/magnum-weekly-meeting09:02
travisholtono/09:03
jakeyip#topic Cluster API09:03
jakeyipSo I've been playing with it and I think it's good. One of the things we discussed last week was to have some sort of gate to keep the driver from being activated automatically.09:04
jakeyipis everyone ok with the method at https://review.opendev.org/c/openstack/magnum/+/891722 ? 09:05
jakeyipit's not verified, but if everyone is OK I will do the necessary to rebase it and get it passing09:06
daleesI agree,  I think there's features to add and probably bugs to fix. But it's a really great base to begin with and the beta flag reduces the risk of merging most of the patches as they are into the capi driver path09:07
jakeyipthanks dalees :)09:07
daleesdo we need to merge this soon, with the milestone almost upon us?09:08
jakeyiplet's carry on, I don't want to overrun the meeting as we have lots to cover. we can loop back to this at the end, for those who are reviewing patches right now.09:09
jakeyipyes I just want an OK from the team, for a couple of patches then I'll do the rebase and we can merge it09:09
jakeyipthe other thing to discuss is the hard problem, naming https://review.opendev.org/c/openstack/magnum/+/892854.09:10
jakeyipthis is because there were a few different var name in different places, so I propose standardising it to 'capi'. similarly this needs an OK from the team before I do the rebase, because it affects everything up the line.09:11
jakeyipanyone has any comments09:11
* travisholton is ok with "capi"09:12
jakeyipthanks travisholton 09:12
daleesyep, your proposed changes are fine09:12
jakeyipok I think these are the only two blockers. if I don't see any objections by the end of the day I'll rebase everything up to https://review.opendev.org/c/openstack/magnum/+/880805 and try to get it passing checks.09:13
daleesfantastic09:14
jakeyip#action jakeyip to rebase the CAPI changes up to 88080509:14
jakeyipdalees: you want to talk about helm repo?09:14
daleesbriefly - I've created the patches to make the gerrit repo and the intended contents are to fork https://github.com/stackhpc/capi-helm-charts/ (apache2 license) and continue development with the Magnum community.09:16
travisholtoni think we'll need https://github.com/stackhpc/cluster-api-addon-provider to start with as well09:16
daleesI'm not sure we want to fork and own that as part of Magnum. That belongs more with the CAPI project?09:18
mnasiadkaLet's try with basic stuff first and see if we need anything else09:18
travisholtonok09:19
jakeyipgreat work, thanks. where do we go from there? do we still need a registry, or do you think we will be able to push to a gh-pages branch? 09:19
mnasiadkawe will push the helm chart to artifacthub09:21
daleesnot sure yet - mnasiadka suggested we look at how openstack-helm publishes and follow that model09:21
mnasiadkajust like openstack-helm does with their charts09:21
mnasiadkaI can take care of that once we get the repo in and move the code there09:21
jakeyipAFAICT, that's how I think it works. They have a workflow that pushes the updated index.yaml to the gh-pages branch https://github.com/stackhpc/capi-helm-charts/blob/gh-pages/index.yaml 09:21
mnasiadkayes, but the repo is in github, so that's logical09:22
jakeyipso the repo https://github.com/stackhpc/capi-helm-charts pages becomes https://stackhpc.github.io/capi-helm-charts 09:22
mnasiadkaopenstack does not use gh-pages or anything similar - so I think we need to push to artifacthub (the usual helm chart place) just like openstack-helm does09:22
daleeswe should follow the opendev model, and not add github if it's not necessary.09:22
mnasiadka+1 for what dalees is saying ;-)09:23
jakeyipyeah but opendev mirrors to github (automatically? not sure). if we can push to https://opendev.org/openstack/magnum-capi-helm-charts gh-pages branch, and that mirrors to github, we may have it for free at openstack.github.io/magnum-capi-helm-chartss09:25
jakeyipartifacthub sounds good too, will someone help explore that?09:27
daleeshappy to explore that and artifacthub with mnasiadka as we get the repo and code in there. I'll suggest the easiest trodden path that helm can use, for the first Magnum release iteration :)09:27
mnasiadkajakeyip: let's not use github09:27
jakeyipoh the other option is the original openstackmagnum dockerhub repo. spyros (previous PTL) gave me access.09:28
jakeyipdockerhub is OCI registry so it should be able to host helm chart too09:28
daleesi suspect the easiest will be whatever openstack-helm has chosen.09:28
jakeyipI agreee. it is good to do it the 'official' way.09:28
mnasiadkagood09:29
daleescapi driver using an OCI registry for the helm charts is a feature that needs ot be added ( travisholton will be contributing soon, or already has )09:29
daleesso that probably isn't the first option to choose.09:29
jakeyipok.09:29
mnasiadkaok, I might have a stupid question (which I asked already) - I'm fine with doing the Helm thing for now - but aren't we closing Vexxhost's adoption of upstream driver by not supporting pykube as an alternative?09:30
jakeyipso we discussed it a bit. it is tricky to support 2 drivers doing the same thing due to how magnum structures the driver code.09:32
daleesmnasiadka: sort of, it'd still work added to Magnum as they do now. It's an alternate capi driver to stackhpc's helm driver and would need a new driver namespace (and driver tuple matching, as jakeyip pointed out).09:32
jrossercan i ask if you're breaking deployments already using the vexxhost code?09:33
jakeyipjrosser: good question. do you have links to the vexxhost code?09:33
jakeyipI think it's https://github.com/vexxhost/magnum-cluster-api (I have a bookmark :D )09:34
jrosseryes09:34
jrosseras an operator and contributor to deployment tooling, it is concerning to me that there are aparrently two parallel efforts here09:35
mnasiadkadalees: I still think we should strive to get more people collaborating on the upstream driver ;-)09:35
daleesI don't think the driver name conflicts, but the tuple matching may, if the capi driver also provides {"server_type": "vm", "os": "ubuntu", "coe": "kubernetes"}  ref https://github.com/vexxhost/magnum-cluster-api/blob/main/magnum_cluster_api/driver.py#L379C15-L379C1509:35
daleesmnasiadka: i agree; I'd like to have been involved in the discussions between vexxhost and stackhpc at the summit as they presented a talk together. Neither are represented in this meeting, unfortunately09:37
mnasiadkadalees: I work at StackHPC, but most of my interests are outside Kubernetes09:37
mnasiadkaBut yes, the interested party should be on the meeting, but probably it's hard to make a meeting for AU/NZ, Canada and Europe ;-)09:38
daleesmnasiadka: ah, apologies!09:38
mnasiadkadalees: I have enough on my plate being Kolla PTL, no apologies needed :)09:38
jakeyipyes I agree, I too would love them to join in the meeting too. we really need help.09:39
jakeyipfor the very first CAPI change https://review.opendev.org/c/openstack/magnum/+/815521/ , mnaser from vexxhost is involved09:40
daleesyeah; I read it as the vexxhost driver created in Oct 2022, perhaps due to slow movement on that. The commits from stackhpc arrived in April 202309:43
jakeyipyeah at that time john's change was 'os': 'cluster_api'09:44
jakeyipjrosser: do you mind sharing more; are you using vexxhost code already?09:44
jrosserjakeyip: yes, but not yet in a production setting09:45
jrosserand i am core contributor to openstack-ansible and have the tooling 90% complete to deploy it09:45
jrosserand on top of that i have 3 real environments with users who would love easy k8s-aas09:46
jakeyipjrosser: thanks for bringing this up. I think we might have been blindsided by this because vexxhost isn't in the meetings, and didn't warn us about it in the reviews.09:47
jrosseri believe their implementation is pretty complete and tested with customers, but i have no affiliation with either vexxhost or stackhpc09:48
jrosseri am more interested in seeing a good outcome all round09:49
mnasiadkaas we all do09:49
mnasiadkajakeyip: maybe worth sending a mail to mnaser and ricolin?09:49
jakeyippersonally I haven't chatted with mnaser yet. I was under the impression that matt, who is a contributor from stackhpc to the clusterapi patches, and did a talk at vancouver with mnaser, would have cleared it with him and what he sent is good.09:50
jakeyipmnasiadka: yes I will write something up09:51
mnasiadkathanks09:51
jakeyipalso mnaser is a core on magnum09:52
jakeyipbut he didn't -2 those patches :D09:52
daleesHe proposed PTL candidacy for Magnum, too: https://review.opendev.org/c/openstack/election/+/89309609:53
daleeswe did discuss this topic in the vPTG, but again it didn't have both relevant parties there (though ricolin was), and a lot has changed in both drivers since March09:55
jakeyipoh ok. I should get into contact with him and see if there's a reason he can't make it to this meeting, maybe timezone or something, and we try to accomodate. also ping him to review the clusterapi patches.09:56
jakeyipanyway we are almost at the hour. anything else for capi? there are two other topics :(09:57
daleesyeah it's 5am in quebec, happy to try and accommodate him. 09:57
daleesnothing more on capi from me09:58
jakeyipI'll quickly update secure-rbac. ricolin has a bunch of reviews that needs eyes. thanks mnasiadka for checking them.09:59
jakeyip#topic secure-rac10:00
jakeyip#topic secure-rbac10:00
jakeyipI'll quickly update secure-rbac. ricolin has a bunch of reviews that needs eyes. thanks mnasiadka for checking them.10:00
jakeyipthere was a bit of bump because the scope changes for trust made some policies irrelevant. but I think we have nailed that. mnasiadka has tested them.10:01
jakeyipI will aim to test up to 893018 and get that in10:02
jakeyipif anyone has time do take a look.10:03
jakeyipanything else for secure-rbac?10:03
jakeyip(let's move vPTG topic to next week)10:03
jakeyip#topic Open Discussion 10:05
jakeyipdoes anyone has update?10:05
travisholtonnot from me10:07
jakeyipdalees, mnasiadka ?10:08
mnasiadkanothing from me10:08
jakeyipnot forgetting jrosser :)10:09
daleesall good here10:09
jrosserno, its fine10:09
daleesappreciate the discussion today, thanks all.10:10
jakeyipalright thanks all for coming! 10:10
jakeyip#endmeeting10:10
opendevmeetMeeting ended Wed Aug 30 10:10:29 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:10
opendevmeetMinutes:        https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-08-30-09.01.html10:10
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-08-30-09.01.txt10:10
opendevmeetLog:            https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-08-30-09.01.log.html10:10
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313111:48
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313112:00
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313112:03
opendevreviewTyler proposed openstack/magnum master: Add extra_network_name label  https://review.opendev.org/c/openstack/magnum/+/89317613:01
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: Add magnum service to rbac tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/87708614:12
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313114:12
opendevreviewMichal Nasiadka proposed openstack/magnum-tempest-plugin master: WIP: k8s driver CI tests  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89313114:13
opendevreviewMerged openstack/magnum-tempest-plugin master: Add clients to tempest plugins  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/87604515:03
opendevreviewMerged openstack/magnum-tempest-plugin master: Cleanup py27 support  https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/89050715:25

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