| opendevreview | Ghanshyam proposed openstack/magnum-tempest-plugin master: Add stable branch jobs on the plugins master gate https://review.opendev.org/c/openstack/magnum-tempest-plugin/+/725695 | 01:18 |
|---|---|---|
| opendevreview | Ghanshyam proposed openstack/magnum stable/train: DNM: test tempest 26.1.0 tag https://review.opendev.org/c/openstack/magnum/+/825242 | 03:51 |
| strigazi | #startmeeting magnum | 09:00 |
| opendevmeet | Meeting started Wed Jan 19 09:00:16 2022 UTC and is due to finish in 60 minutes. The chair is strigazi. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| opendevmeet | The meeting name has been set to 'magnum' | 09:00 |
| strigazi | #topic Roll Call | 09:00 |
| strigazi | o/ | 09:00 |
| tobias-urdin | o/ | 09:00 |
| oneswig | o/ | 09:00 |
| bbezak | o/ | 09:00 |
| parallax | \o | 09:00 |
| strigazi | Thanks for joining the meeting tobias-urdin oneswig bbezak parallax | 09:01 |
| oneswig | Thanks for arranging it :-) | 09:01 |
| strigazi | Agenda (from header): | 09:01 |
| strigazi | #link https://etherpad.opendev.org/p/magnum-weekly-meeting | 09:01 |
| gbialas | o/ | 09:02 |
| strigazi | o/ gbialas | 09:02 |
| strigazi | #topic Stories/Tasks | 09:02 |
| strigazi | #topic Add Cluster API Kubernetes COE driver | 09:02 |
| strigazi | #link https://review.opendev.org/c/openstack/magnum-specs/+/824488 | 09:02 |
| strigazi | oneswig: do you want to start the discussion on it? | 09:03 |
| oneswig | Thanks for raising this strigazi. In the team we have the cluster api end of an implementation in good shape | 09:03 |
| oneswig | It has been developed with Magnum integration in mind | 09:03 |
| oneswig | The concept is to use an external k8s management cluster for kubernetes cluster provisioning and management. | 09:04 |
| jakeyip | hi o/ | 09:04 |
| oneswig | We get to draw on a good deal of operator functionality for relatively little Magnum code. | 09:05 |
| oneswig | Our hope is that the development of the driver itself is fairly lightweight, but there may be significant effort needed around regression testing of Magnum, plus any assumptions in the code made for the heat-centric design | 09:06 |
| oneswig | Making those changes without disruption is where the art lies | 09:07 |
| strigazi | tobias-urdin and others non-stackHPC, are you aware of the spec? What do you think? | 09:07 |
| tobias-urdin | I read it just now, I wasn't aware of it but welcome it :) | 09:08 |
| jakeyip | I am not familiar with cluster api but I like what it can bring, e.g. less reliant on heat and removes need for keystone trusts | 09:09 |
| strigazi | oneswig: what would be nice to add in the SPEC is some direction on the implementation, break it onto some tasks | 09:10 |
| oneswig | You're right, it's very light on concrete detail. I'll try to change that this week | 09:10 |
| strigazi | eg add the appcreds generation code, the base class for CAPI in drivers, the helm chart maintenance | 09:10 |
| oneswig | +1 | 09:11 |
| strigazi | oneswig: It doesn't have to be in detail, just to make some self contained tasks with order. eg appcreds generation should be first i guess | 09:11 |
| strigazi | jakeyip: trusts and appcreds are not too different as concepts, but appcreds are definitely better | 09:12 |
| strigazi | oneswig, will we need to host our own helm charts somewhere? | 09:13 |
| strigazi | not the code, the tarballs | 09:13 |
| oneswig | Not sure what the best plan is there. | 09:13 |
| oneswig | Ideally it would dovetail with CERN's work | 09:14 |
| jakeyip | what is CERN's work? | 09:14 |
| strigazi | jakeyip: all add-ons internally we have them in a single helm chart. | 09:15 |
| strigazi | a metachart, as it is usually called. It's a common pattern in helm | 09:15 |
| strigazi | We kind of do it in magnum ATM but in the code: | 09:15 |
| strigazi | https://github.com/openstack/magnum/blob/master/magnum/drivers/common/templates/kubernetes/fragments/install-helm-modules.sh | 09:17 |
| strigazi | the ideal thing would be to move this outside the code | 09:17 |
| strigazi | eg https://gitlab.cern.ch/helm/releases/cern-magnum | 09:18 |
| strigazi | tobias-urdin: jakeyip: makes sense? | 09:18 |
| parallax | +1 | 09:20 |
| jakeyip | yes | 09:20 |
| tobias-urdin | yes | 09:20 |
| strigazi | The SPEC implies smth similar | 09:21 |
| strigazi | https://review.opendev.org/c/openstack/magnum-specs/+/824488/1/specs/yoga/clusterapi-driver.rst#88 | 09:22 |
| strigazi | The addons that mention installed with helm can be tracked in a similar way | 09:22 |
| oneswig | It would certainly simplify automation effort, I think | 09:23 |
| strigazi | In our case, we host in a private registry. We could ship it in the code base which would be strange or host a magnum chart somewhere | 09:23 |
| strigazi | i don't think we can solve this now, but maybe we raise it in the ML? | 09:24 |
| strigazi | We could use a provider, dockerhub, github, to start | 09:25 |
| jakeyip | can you clarify what you mean by this ^ ? | 09:26 |
| strigazi | this chart here: https://github.com/openstack/magnum/blob/master/magnum/drivers/common/templates/kubernetes/fragments/install-helm-modules.sh#L72 | 09:27 |
| strigazi | Is created and installed locally on the node at cluster creation | 09:27 |
| strigazi | We could host this chart on a provider and at cluster creation, you can pass just values for this metachart and the chart version | 09:28 |
| strigazi | operators in the CT can define values for this chart that control all components and users can override on creation | 09:29 |
| strigazi | It will replace instead of these bash scripts https://github.com/openstack/magnum/tree/master/magnum/drivers/common/templates/kubernetes/helm | 09:30 |
| strigazi | jakeyip: makese sesne? | 09:30 |
| jakeyip | hm, is it only values that can be overridden? is it possible for magnum have a default chart and infrastructure providers can host and customize their own? | 09:30 |
| strigazi | jakeyip: magnum operators should be able to use their own, not the only the default | 09:31 |
| strigazi | jakeyip: we should provide a default to have a base working | 09:31 |
| jakeyip | cool | 09:31 |
| strigazi | jakeyip: or not, at CERN we will use definitely a more complicated due other things that exist only at CERN | 09:32 |
| strigazi | but all clouds will have their own, eg custom storage classes for cinder etc | 09:33 |
| strigazi | we move on, more questions on it? | 09:33 |
| oneswig | +1 | 09:34 |
| strigazi | oneswig: we'll wait for an update from you and then push code | 09:36 |
| strigazi | #topic Open Reviews | 09:36 |
| strigazi | from the list in https://etherpad.opendev.org/p/magnum-weekly-meeting | 09:36 |
| strigazi | I have already looked at all of them, I'll add feedback today | 09:37 |
| gbialas | Thx. | 09:37 |
| strigazi | Does anyone want to discuss something about them? Any issues? | 09:37 |
| gbialas | For soem reason yesterday zuulu added -1 because of tox failed on edocs... No idea why. | 09:38 |
| strigazi | parallax: you left a question in the etherpad | 09:38 |
| strigazi | gbialas: did you recheck? | 09:39 |
| bbezak | I've noticed this recently in wallaby - https://github.com/kubernetes/cloud-provider-openstack/issues/1738. Will take a look at it to fix that. | 09:39 |
| strigazi | bbezak: thanks | 09:39 |
| gbialas | Not yet. Bus afaik it is failing localy also. | 09:39 |
| parallax | well, yes - I'm wondering what's the future for the particular drivers | 09:40 |
| strigazi | fedoda-coreos will be with us for a bit more, the others we can start dropping. Mesos should be first since its archived | 09:41 |
| parallax | e.g swarm | 09:41 |
| strigazi | parallax: note that you can disable drivers in magnum.conf so that they can not be used | 09:41 |
| parallax | do you deprecate first, then drop in the next cycle? | 09:41 |
| strigazi | parallax: let's deprecate and send an email to the ML? then in Z we drop? | 09:42 |
| parallax | that makes sense I think | 09:42 |
| strigazi | cool | 09:44 |
| strigazi | #topic Open Discussion | 09:44 |
| jakeyip | there was also bay and baymodel deprecation | 09:44 |
| jakeyip | I think https://review.opendev.org/c/openstack/magnum/+/803779 | 09:45 |
| strigazi | jakeyip: I think we can drop these, wdyt? | 09:45 |
| jakeyip | yes would like to see them gone. need a deprecation strategy though, e.g. what about magnumclient? | 09:46 |
| jakeyip | thinking deprecate in client first then api, does that makes sense what is the normal process? | 09:47 |
| strigazi | jakeyip: in the past it was two releases, but I think we bay/baymodel we can be flexible since they are not maintained in a while | 09:47 |
| strigazi | jakeyip: i'd drop and also notify the ML | 09:48 |
| jakeyip | great | 09:49 |
| jakeyip | i can help with testing out some of the reviews in the etherpad, I am guessing that is priority | 09:49 |
| strigazi | excellent | 09:49 |
| strigazi | let's wrap up the meeting? | 09:50 |
| strigazi | said twice | 09:51 |
| strigazi | thanks everyone, see you next week! | 09:51 |
| strigazi | #endmeeting | 09:51 |
| opendevmeet | Meeting ended Wed Jan 19 09:51:35 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:51 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/magnum/2022/magnum.2022-01-19-09.00.html | 09:51 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/magnum/2022/magnum.2022-01-19-09.00.txt | 09:51 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/magnum/2022/magnum.2022-01-19-09.00.log.html | 09:51 |
| strigazi | jakeyip: I'm getting a coffee, you'll be here a bit later? | 09:52 |
| jakeyip | not related to meeting, what k8s/magnum version does everyone run? | 09:52 |
| jakeyip | strigazi: yes | 09:52 |
| bbezak | 1.21 ussuri in prod | 09:53 |
| jakeyip | we are 1.21 / u too, wondering if we can do 1 | 09:56 |
| jakeyip | 1.22 or 1.23 when we get to v / w | 09:56 |
| strigazi | jakeyip: we are in train (with a lot of patches) and run 1.{20,21,22} | 10:22 |
| strigazi | jakeyip: the main issues are version deprecations | 10:23 |
| strigazi | jakeyip: I think only calico was the issue, if we get the calico patch (mentioned in the etherpad) it should be ok | 10:25 |
| jakeyip | i see. does 1.22 work, do I need to do | 10:26 |
| jakeyip | anything special (other than rancher hyperkube) | 10:26 |
| strigazi | jakeyip: for us it works, we have our own hyperkube but rancher should be the same | 10:27 |
| jakeyip | cool thanks | 10:28 |
| opendevreview | Grzegorz Bialas proposed openstack/magnum master: Support extra_network and extra_subnet labels https://review.opendev.org/c/openstack/magnum/+/775793 | 14:46 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!