14:00:01 #startmeeting kolla 14:00:01 Meeting started Wed Apr 20 14:00:01 2022 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:03 #topic rollcall 14:00:06 o/ 14:08:31 /o\/o\ 14:09:26 #topic agenda 14:09:26 * CI status 14:09:26 * Release tasks 14:09:27 * Current cycle planning 14:09:27 * Additional agenda (from whiteboard) 14:09:27 * Open discussion 14:09:38 #topic CI Status 14:09:48 I think that's quite ok now, since we fixed Victoria and Ussuri? 14:10:59 Yoga will be ready once CI mirror centOS 14:11:14 yup, that's release task :D 14:11:32 I would say that CI is fine 14:12:30 #topic Release tasks 14:12:53 So the only patch that needs to be merged is the CentOS one - and we're waiting for infra mirror sync 14:13:03 I haven't seen other disturbing issues 14:13:09 hrw: what about the Ubuntu horizon thing? 14:13:17 UCA horizon is a problem 14:13:28 not heard anything from UCA team on irc. will reask 14:13:39 ok, do they have a bug filed for this? 14:14:34 not by me and not checked 14:14:38 ok 14:14:50 #topic Current cycle planning 14:15:19 We're on a good path to get rid of binary once and for all 14:15:37 we got rid of it 14:15:40 So I guess that's the ,,theme'' that is progressing now 14:15:44 we are now on cleaning 14:15:55 Yeah, I was thinking about cleaning and getting rid of -source in the image name 14:16:05 yep. short names as we call it 14:16:36 uhttps://review.opendev.org/c/openstack/kolla-ansible/+/837293 needs merge and then I do one patch to kolla and we are on source only with short names 14:16:45 great 14:16:52 then upgrade paths need work but that in 'additional agenda' 14:16:58 ok 14:17:02 #topic Additional agenda (from whiteboard) 14:17:18 let's start with yours 14:17:19 (hrw) Yoga->Zed upgrades 14:17:34 paste rest 14:17:43 new CI job: Y/binary -> Z/source 14:17:51 we need to handle removal of old images (Y/binary ones or Y/source ones as we will have shorter names in Z) 14:17:54 ok 14:18:05 so for now we only test Y/source -> Z/source on CI 14:18:29 as there is no Y/binary -> Z/binary path we need to test Y/binary -> Z/source one 14:18:59 and then we need a way to get rid of old containers as names are changed in both scenarios 14:19:18 kolla/ubuntu-binary-nova-compute -> kolla/ubuntu-nova-compute etc 14:19:25 image names have changed, so that should be handled semi-automatically in existing code 14:19:37 would be bad to have both copies running 14:19:39 if the image name variable gets templated properly 14:19:46 NOTE: I never did upgrades 14:20:02 Ok, I guess we (me, yoctozepto, mgoddard) can help with this one 14:20:36 yoctozepto: you here or not yet? 14:21:04 we don't have CI for binary-upgrade currently, but it makes sense to test the move from binary to source 14:21:17 we need to have it as this will be popular path 14:21:47 and better get it running in first weeks of cycle before we grab Z changes from projects 14:22:18 yup, agree 14:22:34 seems yoctozepto is very late ;) 14:22:44 should we move his topics to next week? 14:23:07 we can discuss them now too 14:23:12 it is EM/EOL 14:23:19 (yoctozepto) EM Victoria 14:23:22 that's obvious 14:23:35 do we need to merge any Victoria patches before we do that last release and mark as EM? 14:23:45 iirc we did but moment 14:24:01 nothing in queue 14:24:10 so we can #action 14:24:29 no open changes in Kolla, one open in K-A (make kolla-build quiet) 14:24:41 ok, merge it and release 14:24:46 and two in Kayobe 14:25:23 mgoddard: https://review.opendev.org/c/openstack/kayobe/+/782703 and https://review.opendev.org/c/openstack/kayobe/+/830069 - either let's merge them or abandon 14:25:54 (yoctozepto) EOL Train 14:25:59 that's more complicated 14:26:25 I vote for EOL despite it being migration point 14:26:58 we have some (not a lot, just a couple) customers on Train, I'll check internally if there are any reasons for not doing EOL - but I doubt there are 14:27:06 ok 14:27:32 #note EMHPC Train then 14:27:33 ;D 14:27:43 #action mnasiadka work on marking Train EOL 14:28:00 ok then, seems like we're done 14:28:03 #topic Open discussion 14:28:08 anything? 14:28:30 ubuntu 22.04 is coming - another thing to your plate ;D 14:28:48 yeah, we know, we'll manage it 14:28:56 external repos will be main pain probably 14:29:04 o/ 14:29:33 infra team will mirror main repos, you need to add UCA mirror probably (I did most of previous ones iirc) 14:29:38 yoctozepto: you just made it to open discussion ;-) 14:30:01 one thing: do we checked core members lists? 14:30:02 mnasiadka: to close the meeting :-) 14:30:29 there are people who I have not seen for a while there 14:30:39 we did, last cycle, I did not remove some people that promised to continue working on Kolla 14:30:45 ok 14:30:51 I can review if they did anything 14:31:19 yoctozepto: re-read meeting and add what you want 14:32:05 * yoctozepto finished reading 14:32:14 I agree that we should revisit the cores' list 14:32:37 as other projects do 14:33:13 re upgrades from binary to source (typeless) - will do 14:33:31 Maksim Malchuk proposed openstack/kayobe master: Cleanup old and deprecated Swift configuration https://review.opendev.org/c/openstack/kayobe/+/838730 14:33:56 I have a question - we're left with admin endpoint for keystone (removed all the others) - what's the ultimate plan with it? 14:34:56 btw - ussuri is EM already? 14:35:37 yes 14:35:50 Ifa0b1b059ca8aafb76b2c25c1dd03209bc001f2d 14:36:32 ok. have to remember 'ignore mnasiadka: remove it 14:36:46 mnasiadka: it even has a random bug (on the whiteboard) 14:36:49 as it uses a high port 14:36:59 anything can randomly pick it up and block the deploy 14:37:22 yoctozepto: I stumbled upon Magnum having issues with lack of admin endpoint today, I think keystoneclient/keystoneauth1 defaults to that... 14:37:56 mnasiadka: ugh? lack of admin endpoint for what? 14:39:17 yoctozepto: lack for admin endpoint for keystone :) 14:39:28 mnasiadka: but it's not removed (-: 14:39:46 or do you mean it is somewhere where you support it? 14:39:48 Yeah, I know - but it's not created by default in devstack 14:40:00 devstack, devstack 14:40:01 Used devstack to test out one thing in Magnum and stumbled across this 14:40:02 this is kolla meeting 14:40:12 So just asked, if we are planning to remove admin endpoint in keystone 14:40:13 just use kolla to test out one thing... 14:40:18 if yes - I need to fix it there :D 14:40:30 are you sure it's not devstack's misconfig? 14:40:30 yoctozepto: write tempest tests in Kolla? come on 14:40:50 mnasiadka: we should run tempest at some point tbh 14:40:58 no need to write, just run 14:41:19 write NEW tests for Magnum, calm down :) 14:41:24 mnasiadka: https://bugs.launchpad.net/cloud-archive/+bug/1969630 is yoga/uca/horizon bug 14:41:42 deprecate magnum in yoga, remove in zed 14:41:55 Tempest in K-A CI? Well, sure, why not 14:42:04 tomorrow we will only worry of Magnum as guns ;D 14:42:31 deprecate and remove OpenStack, why not ;) 14:42:37 mnasiadka: well, you write tempest tests and run them against k-a; I think I am missing the point you are trying to make by running devstack ;-) 14:42:58 yoctozepto: replicate CI and find new problems in devstack :D 14:43:03 mnasiadka: well, magnum is not necessarily the best faring project 14:43:16 mnasiadka: ah, you are now a devstack fanboy, very well 14:43:19 yoctozepto: there's a couple of them, trying to make it better 14:43:22 go get those bash scripts 14:43:31 yoctozepto: don't even get me started :) 14:43:35 anyway, let's finish 14:43:35 :-) 14:43:38 thanks for the meeting! 14:43:39 thus go kolla 14:43:42 #endmeeting