14:00:01 #startmeeting kolla 14:00:01 Meeting started Wed Mar 15 14:00:01 2023 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:01 The meeting name has been set to 'kolla' 14:00:04 #topic rollcall 14:00:04 o/ 14:00:07 \o 14:00:10 [o] 14:00:32 o/ 14:01:20 o/ 14:02:17 \o 14:03:16 #topic agenda 14:03:16 * CI status 14:03:16 * Release tasks 14:03:16 * Regular stable releases (first meeting in a month) 14:03:16 * Current cycle planning 14:03:18 * Additional agenda (from whiteboard) 14:03:18 * Open discussion 14:03:20 #topic CI Status 14:03:36 CI seems green 14:03:39 #topic Release tasks 14:04:01 R-1 week 14:04:31 In theory we should be prepared to cut stable branch and RCs, but it would be good to try to get the podman support in. 14:04:57 #topic Current cycle planning 14:05:17 So, current cycle is Antelope still, there are some podman related patches that we could try to get in 14:05:41 https://review.opendev.org/q/topic:kolla-podman 14:06:45 What I'm looking for is a CI job testing the podman deployment and upgrade on debian/rocky/ubuntu (ideally aarch64) as well 14:07:01 mhiner: ihalomi - is that somewhere? 14:07:18 here: https://review.opendev.org/c/openstack/kolla-ansible/+/865182/12 14:08:23 this is only testing docker - can't see any new CI jobs? 14:09:52 yes, now it deals just with adding the option to run on podman 14:10:22 right, so we would need to define new CI jobs, if you need help with that - I can have a look 14:11:11 that would be great, thanks 14:11:31 ok, will do 14:12:00 looking at the whiteboard, but not seeing any other candidates for squeezing in 14:12:38 So, the next PTG is approaching - 27-31 Mar 2023 14:12:50 #link https://etherpad.opendev.org/p/kolla-bobcat-ptg 14:12:55 That's the PTG planning etherpad 14:13:11 I've penciled in three sessions 14:13:14 Monday - 13.00 - 17.00 UTC (general, Kolla and Kolla-Ansible) 14:13:14 Tuesday - 13.00 - 15.00 UTC (Kolla-Ansible) 14:13:14 Thursday - 13.00 - 15.00 UTC (Kayobe) 14:13:57 Last time we finished Kolla & Kolla-Ansible in one day, so I think we could use the second day to invite operators (similar to the operator hour last PTG) 14:14:03 Any comments? 14:15:01 Mark Goddard proposed openstack/kolla-ansible master: Fix OpenStack exporter scrape with internal TLS & FQDN https://review.opendev.org/c/openstack/kolla-ansible/+/877483 14:15:58 I think it is a good idea 14:16:02 Ok, seems it fits for everyone 14:17:05 #topic Additional agenda (from whiteboard) 14:17:20 k.yarovoy - kolla-build transition to DockerClient, zuul gives build errors for some jobs. Can someone please take a look at it? https://review.opendev.org/c/openstack/kolla/+/825786 14:17:41 added RP+1 on this one, because that's from the podman lot 14:17:50 will try to have a look, if others can - then it would be nice 14:18:13 this patch would also need some CI jobs testing podman builds 14:18:33 Next one 14:18:34 (mnasiadka) - Docker Hub no more 14:19:03 So, Docker Hub is going to drop Free Teams support - that means more or less Kolla images will get removed in 30+ days 14:19:37 We could apply for free account for open source teams - but that would require us to put that we support solely Docker and Docker Desktop in README - if I remember correctly 14:20:06 #link https://www.docker.com/community/open-source/application/ 14:20:48 how can we support desktop version?) 14:20:56 or switch to quay.io then? 14:21:17 even if we would get this - it's only for a year 14:21:20 +1 for switch 14:21:29 well, we switched to quay.io long time ago 14:21:37 by default kolla-ansible fetches images from quay 14:21:38 ghcr as a backup? 14:21:41 completely switch 14:21:52 remove dockerhub images 14:22:06 bbezak: yes, that was my idea - to switch to GHCR or something else as a backup 14:22:30 ghcr have free account? 14:22:31 ok then - let's re-discuss this on the PTG (if anything new arises) and implement 14:22:36 mmalchuk: yes 14:22:57 Verification of a change to openstack/kolla-ansible stable/yoga failed: Use loadbalancer to connect to etcd https://review.opendev.org/c/openstack/kolla-ansible/+/874402 14:23:12 think it limited 14:23:31 500MB 14:23:37 storage))) 14:23:52 we could also consider to stop publishing images completely. deployments should learn to build their own anyway 14:24:09 good idea! 14:24:16 the limit is only for private repositories on GHCR 14:24:50 frickler: well, we've been there multiple times - yes, we encourage, but I don't think we should build the images in CI every time :) 14:25:10 that's going to be a flakey experience at least 14:25:30 for CI maybe we can use the opendev registry 14:26:28 I think the easy part now, is to remove the publish jobs and credentials for Docker Hub - if we stop publishing to Quay.io - there's going to be more chaos than anything (for operators using those images) 14:26:52 We can discuss on the PTG (again) if we want to stop publishing at all, but it needs to be correctly communicated 14:27:32 Feel free to add the topic to PTG etherpad 14:27:57 ok 14:28:45 Ok then, moving to Open Discussion 14:29:11 #topic Open discussion 14:29:17 Anything? Anybody? 14:29:45 does stackhpc publish public images? or anyone else other than osism? 14:30:53 Michal Nasiadka proposed openstack/kolla-ansible stable/yoga: Add OpenSearch https://review.opendev.org/c/openstack/kolla-ansible/+/875729 14:31:23 frickler: stackhpc doesn't 14:32:02 also, kind of related, seeing https://review.opendev.org/c/openstack/kolla/+/877346 I wondered whether we should drop docker mentions in the readme and replace with generic "container" wording 14:33:47 might be 14:35:32 maybe also rename kolla_docker to kolla_container? 14:37:25 we might think about it, but first let's get CI jobs validating podman ;-) 14:37:32 ok, thanks for coming! 14:37:36 #endmeeting