| strigazi | #startmeeting magnum | 09:02 |
|---|---|---|
| opendevmeet | Meeting started Wed Feb 9 09:02:14 2022 UTC and is due to finish in 60 minutes. The chair is strigazi. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:02 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:02 |
| opendevmeet | The meeting name has been set to 'magnum' | 09:02 |
| strigazi | #topic Roll Call | 09:02 |
| strigazi | o/ | 09:02 |
| dalees | o/ | 09:02 |
| strigazi | Hello dalees , first time in this meeting? | 09:03 |
| dalees | Yes, I'm working at Catalyst Cloud on Magnum now Fei Long has moved on. | 09:04 |
| strigazi | dalees: nice | 09:05 |
| dalees | I think we met in Barcelona Kubecon, Ricardo introduced us a few years back. | 09:05 |
| dalees | anyway, hi! | 09:05 |
| gbialas | o/ | 09:06 |
| strigazi | dalees: I remember it, I couldn't tell from the irc nick | 09:06 |
| strigazi | o/ gbialas | 09:06 |
| strigazi | #topic Stories/Tasks | 09:08 |
| strigazi | #link https://etherpad.opendev.org/p/magnum-weekly-meeting | 09:08 |
| strigazi | (dalees: Ricardo says hi, he's next to me) | 09:09 |
| strigazi | gbialas: I managed to merge some of your patches last week | 09:10 |
| strigazi | And I have pushed 827668: fcos-k8s: Update to v1.22 | https://review.opendev.org/c/openstack/magnum/+/827668 | 09:10 |
| gbialas | Yes, I saw that. Huuuge thank for this. | 09:10 |
| gbialas | This is also very handy :) | 09:11 |
| strigazi | I will bump it to 1.23, it shouldn't need anything else | 09:11 |
| strigazi | have a look at it if you can | 09:11 |
| dalees | strigazi, :-) | 09:11 |
| strigazi | gbialas: let's try to update to 1.23.3 and then merge the rest of the patches? | 09:13 |
| gbialas | strigazi: 1.23.3 -> you mean k8s version ? | 09:15 |
| strigazi | gbialas: yes | 09:15 |
| gbialas | Ok. We can do this. | 09:15 |
| strigazi | the patch above, 1.22 was the main painpoint since it deprecated quite some apis | 09:16 |
| tobias-urdin | o/ | 09:16 |
| strigazi | tobias-urdin: \o | 09:17 |
| gbialas | Yeah, I see that it do a lot more that just "update to v.1.22" :) | 09:17 |
| *** mnasiadka_ is now known as mnasiadka | 09:18 | |
| strigazi | gbialas: api version changes bite in many places | 09:18 |
| mnasiadka | o/ - sorry for being late | 09:18 |
| gbialas | strigazi: Yeah, I know how it looks. | 09:19 |
| strigazi | mnasiadka: \o | 09:19 |
| strigazi | I think we are done with reviews from last week, let's move to: | 09:21 |
| strigazi | #topic Open Discussion | 09:21 |
| * dalees is pleased to see FCOS `35.20220116.3.0` in there too. | 09:21 | |
| strigazi | For the ClusterAPI driver, since Stig is not here we can skip. But have a look at it 824488: Add Cluster API Kubernetes COE driver | https://review.opendev.org/c/openstack/magnum-specs/+/824488 | 09:23 |
| strigazi | Anyone wants to bring something up? | 09:24 |
| mnasiadka | I saw some old change trying to stop using hyperkube - is there a plan to do anything with it? Current situation is a bit sub-optimal I would say ;-) (fresh kubernetes versions not working out of the box without hyperkube_prefix/kube_tag settings) | 09:24 |
| strigazi | mnasiadka: IMO, since we plan to use CAPI and we can get updated hyperkube builds from rancher easily, we can leave it as it is | 09:25 |
| mnasiadka | ok then | 09:25 |
| strigazi | mnasiadka: we can set the default to the rancher build | 09:26 |
| jakeyip | o/ sorry I'm late, getting used to TZ changes | 09:26 |
| mnasiadka | but for CAPI a user would need a pre-existing k8s cluster to deploy, which changes things a bit | 09:26 |
| mnasiadka | strigazi: would make sense, since the current default probably is EOL version of Kubernetes | 09:26 |
| strigazi | mnasiadka: I added an entry for the next meeting | 09:28 |
| strigazi | mnasiadka: in the agenda https://etherpad.opendev.org/p/magnum-weekly-meeting | 09:28 |
| mnasiadka | strigazi: I see it, have it opened :) | 09:29 |
| dalees | I've got a couple of (basic) questions. | 09:30 |
| strigazi | mnasiadka: for the CAPI driver that needs an existing k8s cluster, maybe leave a comment in the spec? I think it can be bring your own cluster or use a magnum cluster | 09:31 |
| mnasiadka | strigazi: will do | 09:31 |
| strigazi | jakeyip: \o | 09:32 |
| strigazi | dalees: shoot | 09:32 |
| dalees | How many others in magnum community are using rolling upgrade vs recreate clusters? I'm currently interested in FCOS35 as there's a kernel CVE fixed in there, and have found a couple of rolling upgrade bugs to fix. | 09:33 |
| strigazi | dalees: we (at CERN), always recreate | 09:34 |
| strigazi | dalees: we suggest user to leverage LBs (openstack manage or not) to redirect the workloads | 09:34 |
| tobias-urdin | we've had to recreate customers clusters when moving to rancher hyperkube images :( | 09:35 |
| tobias-urdin | even though we just wanted to get a newer k8s to labels and upgrade | 09:35 |
| tobias-urdin | added some info to meeting agenda | 09:35 |
| jakeyip | we (Nectar) haven't tested out rolling upgrades properly, so we don't recommend | 09:35 |
| tobias-urdin | (we've previously been able to upgrade when using old community hyperkube images) | 09:36 |
| dalees | ok, interesting - thanks. maybe explains some of the codebase author sections :). When I have some patchsets created for these fixes, can I just link against story https://storyboard.openstack.org/#!/story/2008628 or should I use/create another? | 09:36 |
| strigazi | tobias-urdin: we can replicate the images to our registry, would this help? | 09:37 |
| strigazi | tobias-urdin: from docker.io/rancher to docker.io/openstackmagnum | 09:37 |
| tobias-urdin | hmm, i'm not really sure but i don't think it would solve it, i don't think it defaults to using docker.io/openstackmagnum on existing clusters | 09:37 |
| dalees | strigazi, is docker.io/openstackmagnum zero rated for image pulls, or normal unauth'd pull limits apply? | 09:38 |
| strigazi | tobias-urdin: indeed, it's the old official repo | 09:39 |
| strigazi | dalees: limits apply, which is an issue for the heat-agent | 09:40 |
| dalees | strigazi, ack | 09:41 |
| strigazi | @all, Do you think we should mirror the heat agent to another registry? quay.io or ghcr.io or both | 09:47 |
| jakeyip | hosting on a non rate limited registry will be nice, but are there any users currently impacted by this? afaict most cloud providers seems to have their own registry? | 09:49 |
| dalees | we're working to solve the pull limits issue with an internally hosted registry, so it affects us now but won't soon. | 09:49 |
| strigazi | @all Anything else to bring up? | 09:53 |
| strigazi | let's end the meeting then, see you next week! | 09:56 |
| strigazi | #endmeeting | 09:56 |
| opendevmeet | Meeting ended Wed Feb 9 09:56:25 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:56 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/magnum/2022/magnum.2022-02-09-09.02.html | 09:56 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/magnum/2022/magnum.2022-02-09-09.02.txt | 09:56 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/magnum/2022/magnum.2022-02-09-09.02.log.html | 09:56 |
| gbialas | See you!!! | 09:57 |
| tobias-urdin | thanks, see you later :) | 09:57 |
| dalees | Thanks, I will bring more silly questions next week. Good to meet you all. | 09:57 |
| *** ykarel is now known as ykarel|away | 16:48 | |
| opendevreview | Stavros Moiras proposed openstack/python-magnumclient master: Cluster config update https://review.opendev.org/c/openstack/python-magnumclient/+/788689 | 23:17 |
| opendevreview | Stavros Moiras proposed openstack/python-magnumclient master: Cluster config update https://review.opendev.org/c/openstack/python-magnumclient/+/788689 | 23:20 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!