15:00:36 #startmeeting kolla 15:00:36 Meeting started Wed Jul 29 15:00:36 2020 UTC and is due to finish in 60 minutes. The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:39 The meeting name has been set to 'kolla' 15:00:49 patience yoctozepto :) 15:00:54 o/ 15:00:58 #topic rollcall 15:01:03 #chair mgoddard 15:01:03 \o 15:01:04 Current chairs: mgoddard yoctozepto 15:01:14 mgoddard mnasiadka hrw egonzalez yoctozepto rafaelweingartne cosmicsound osmanlicilegi bbezak - meeting live 15:01:15 o/ 15:01:32 [o 15:01:39 is the cuckoo pushing me out of the nest? :p 15:01:44 \o 15:02:33 mgoddard: the nest is yours 15:02:45 #topic Agenda 15:02:51 * Roll-call 15:02:54 * Announcements 15:02:55 ** Kayobe & Kolla @ London Open infra virtual meetup tomorrow https://www.meetup.com/OpenInfra-London/events/272083028/ 15:02:58 * Review action items from last meeting 15:03:00 * CI status 15:03:02 * Victoria release planning (kayobe) 15:03:04 * Victoria release planning (kolla & kolla ansible) 15:03:05 * Kolla klub and kall 15:03:07 #topic Announcements 15:03:10 #info Kayobe & Kolla @ London Open infra virtual meetup tomorrow 15:03:14 #link https://www.meetup.com/OpenInfra-London/events/272083028/ 15:03:26 Open to anyone to join 15:03:56 The other two topics look great 15:04:07 Anyone else have anything? 15:04:30 not me 15:04:47 #topic Review action items from last meeting 15:04:48 added to calendar 15:04:51 There were none 15:04:55 #topic CI status 15:05:21 the stein issue has been fixed, thanks mnasiadka 15:06:14 any new CI issues I haven't seen yet? 15:06:43 did not have much time to look at ci this week 15:07:31 #topic Victoria release planning (kayobe) 15:07:45 I think priteau is busy 15:08:04 mnasiadka, dougsz, jovial[m] 15:08:51 How is kayobe looking? 15:08:53 I’m also busy - but can respond to queries 15:08:59 Nothing from me on this 15:09:05 https://tiny.cc/kayobe-review-dashboard2 15:09:26 mnasiadka: congrats on the core nomination :-) 15:09:50 lots of nice backports with a single +2. Let's get them over the line this week 15:10:04 yoctozepto: thanks ;) 15:10:45 if everyone wants to add RP+1 to a patch, that might encourage some reviews 15:11:45 should have some time on friday for reviews 15:12:38 great 15:12:47 #topic Victoria release planning (kolla & kolla ansible) 15:13:06 Does anyone have a feature/work item they'd like to discuss? 15:13:36 focal needs work 15:13:43 infra too 15:14:31 I want focal for hacluster :-) 15:14:48 CI said 'yes' on k-a change for focal and needs reviews 15:15:17 hacluster needs some cleanup and little discussion but I opt for doing that async from meeting unless you have immediate questions on it 15:15:32 sorry, got disconnected 15:15:32 hrw: nice 15:15:35 and order of kolla/kolla-ansible patches may need to be changed (now k-a depends on kolla patches) 15:15:51 infra needs reviews 15:15:57 * hrw done 15:16:02 hrw: one patch for each or multiple (as you use plural)? 15:16:30 I haven't had much time to look at the queue, spared free cycles on hacluster 15:16:56 hrw: hopefully it's not a cyclical dependency? 15:16:59 yoctozepto: whole set of infra patches (2 for k, 1 for k-a) 15:17:13 mgoddard: imho k-a can be done without k part 15:17:23 hrw: ok 15:17:40 I guess we should be able to add support for focal without immediately dropping bionic 15:17:43 mgoddard: it is mostly move to focal on CI and some 'we want focal not bionic' 15:17:51 I can see this 15:17:52 https://review.opendev.org/738994 15:17:52 patch 738994 - kolla - ubuntu: move to 20.04 Focal - 13 patch sets 15:17:53 and this 15:17:58 https://review.opendev.org/#/c/743502/4 15:17:58 patch 743502 - kolla-ansible - ubuntu: move to 20.04 Focal - 4 patch sets 15:18:08 and bionic is marked as supported still so upgrade job works 15:18:14 splendid 15:18:24 yoctozepto: 502 is simple, 994 is not complicated too 15:18:47 hrw: I can't see the 2nd for kolla 15:18:49 where is it? 15:18:59 yoctozepto: 2 for infra, 1 for focal 15:19:04 ah, ok 15:19:20 do we need to consider migrating from bionic to focal? 15:19:45 or rather, does kolla-ansible need to support both 15:20:22 or do we assume that the OS upgrade happens between ussuri deploy and victoria upgrade? 15:20:27 mgoddard: for v we may support both in k-a and in whiskey go for focal only 15:20:49 so users will have a time for switch (like train did for centos) 15:20:49 wallaby :) whiskey also a good name 15:20:53 I would opt for supporting both 15:21:02 whiskey lost due to alcoholism :-) 15:21:12 lame 15:21:15 mgoddard: who would remember release names... we are on vicky now, right? 15:21:25 apparently 15:21:27 ubuntu plays much nicer with us than centos did 15:21:52 yoctozepto: it is easier to migrate 2y os than 5y one 15:22:07 mostly because of 3.6->3.8 rather than 2.7->3.6 :D 15:22:08 #continue 15:22:20 so should we be running CI jobs for xenial and bionic in victoria? 15:22:21 hrw: yup, that part of ubuntu is nice 15:22:31 mgoddard: bionic and focal, yes 15:22:38 I would vote for that case 15:22:55 at least for the primary jobs 15:23:10 it's not strictly necessary, if we require the OS to be upgraded 15:23:11 hacluster (so masakari with it) will require focal 15:23:19 for a rolling reinstall we need to support both 15:23:24 true that 15:23:36 mgoddard: we should abandon/drop xenial now 15:23:37 anyhow, it's easier to upgrade than centos was 15:23:44 that xenial made me smile :-) 15:23:46 xenial definitely 15:23:50 mgoddard: time for xenial->bionic was 2y ago 15:24:17 mgoddard: we should move to focal on CI and have bionic in upgrade job 15:24:21 I suppose we will at least need bionic for upgrades 15:24:41 to show users "we want you to go focal in V but support bionic if you upgrade" 15:24:41 could use running bionic containers on focal hosts 15:24:43 if we are not doing host OS uprade in CI 15:24:49 with message that bionic is gone in W 15:24:57 ussuri doesn't work on focal 15:25:03 due to host OS precheck 15:25:08 mgoddard: that's why upgrade CI job is on bionic 15:25:08 (at least) 15:25:12 we can change that 15:25:14 if it works 15:25:15 ;p 15:25:16 could 15:25:25 we should not 15:25:34 bionic->focal upgrade time is on V 15:25:54 yeah, but the question is whether this is u->os->v or u->v->os 15:26:10 well, that was lame nomenclature 15:26:14 but you get the point 15:26:34 yoctozepto: it is u->v. with u/bionic -> v/bionic or u/bionic -> v/focal 15:26:37 os upgrade can happen before or after openstack upgrade 15:26:42 while we do not handle OS upgrade 15:27:14 still the question is whether bionic containers work better on focal or focal ones on bionic 15:27:16 and u/bionic -> v/bionic -> (v/focal) -> w/focal 15:27:17 :D 15:27:38 that's my opinion but I do not deploy ubuntu ;d 15:27:48 deprecate 15:27:49 :D 15:27:50 red hat page suggested host >= container is best due to kernel 15:28:20 which implies upgrade to focal first, then deploy V 15:28:21 yeah, they did 15:28:30 so bionic containers on focal then 15:28:52 switch to focal and ignore precheck for upgrade jobs 15:29:04 in the pre-upgrade deploy task 15:29:14 but to test that we'd need to support focal in ussuri 15:29:26 so we wouldn't really be testing what we advocate 15:29:45 I wonder how nasty a host OS upgrade in CI would be 15:29:51 maybe it's possibel 15:30:21 infra folks will hunt us down 15:30:46 is it worse than containers? 15:30:55 probably 15:31:06 more cumbersome at least 15:31:09 I would -1 OS upgrade patch 15:31:29 could use asking someone actually doing ubuntu... 15:31:31 and -2 on second try 15:31:35 like osmanlicilegi 15:32:02 how they approach this for them 15:32:26 centos folks discussing ubuntu feels wrong ;d 15:32:34 and hrw just replaces everything :D 15:33:33 it seems like the change required to support focal is minimal, so maybe it doesn't matter too much either way 15:34:29 one thing is for sure - you can't follow the centos8 model 15:34:48 we don't want to ;d 15:34:49 as we won't provide focal and bionic containers for any single release 15:35:40 maybe the mailing list is the place for this? 15:35:47 anyone want to send something out? 15:35:59 mgoddard wants to, we know it ;d 15:36:01 lay out the options, see what people think 15:36:58 #action mgoddard to message openstack-discuss about focal & victoria upgrade 15:37:18 hrw: while you're in the hot seat 15:37:20 infra images 15:37:24 what's the status? 15:37:31 are we blocked by tripleo? 15:37:34 need review 15:37:47 tripleo does not block us from reviewing and testing 15:38:00 can we merge the feature in a disabled default state to avoid breaking them? 15:38:18 we are free to ignore tripleo until merge 15:38:27 yes, but it would be good to merge 15:38:37 it's a big thing to leave until late in the cycle 15:38:38 mgoddard: do review, suggest 'merge disabled' 15:38:56 as I already forgot that you asked for such feature 15:39:34 I'm just trying to find a patch to merging 15:39:48 do you have no persistent memory outside of gerrit? 15:40:01 I thought you had some huge NAS? :) 15:40:03 mgoddard: too easy to forget 15:40:53 mgoddard: but it's probably not replicated well enough 15:41:43 other features? 15:41:49 headphoneJames: how is TLS? 15:42:04 Marcin Juszkiewicz proposed openstack/kolla-ansible master: CI: drop not used Xenial nodeset definitions https://review.opendev.org/743788 15:42:24 is it great! 15:42:45 is it now? 15:43:05 the next greatest thing after k-a that is 15:43:22 so far it is very secure 15:43:33 nobody can use it :-) 15:43:44 headphoneJames: what are you focussing on at the moment? 15:43:58 ironic 15:44:08 and what about nova backend? is it fixed with the timeout? 15:44:17 the service, not the adjective 15:44:34 nova seems clean, though now needs a rebase 15:45:05 but it passed %100, couldn't find any RemoteDisconnect 15:45:15 I guess we should match the timeout to the haproxy timeout? 15:45:48 sensible 15:46:38 https://etherpad.opendev.org/p/tls_tasks 15:47:06 move installation of httpd etc. to openstack-base image 15:47:11 that would be a nice easy win 15:47:41 ok, will do that next 15:47:55 do you have an idea what you're aiming for this cycle? 15:48:37 finish supporting all core API services 15:48:50 then letsencrypt support 15:49:19 diurnalist pushed letsencrypt patches 15:49:40 https://review.opendev.org/741339 15:49:40 patch 741339 - kolla - Add LetsEncrypt images for cert request/renewal - 2 patch sets 15:49:49 https://review.opendev.org/741340 15:49:50 patch 741340 - kolla-ansible - Add support for LetsEncrypt-managed certs - 1 patch set 15:49:54 I haven't looked at them yet 15:50:01 would be good if you could 15:50:19 oh nice 15:50:25 will take a look 15:50:53 cool 15:50:57 added myself to review 15:51:46 I feel like this one is underrated: https://blueprints.launchpad.net/kolla-ansible/+spec/mariadb-ssl-support 15:51:53 and https://blueprints.launchpad.net/kolla-ansible/+spec/memcached-ssl-support 15:53:22 let's move on 15:53:32 #topic Kolla klub and kall 15:53:36 Klub tomorrow 15:53:52 https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_4_Sw/edit# 15:54:25 If anyone has any downstream patches they think might be generally useful, please share 15:54:39 (you don't need to bring the patch, just discuss it) 15:55:31 #topic Open discussion 15:55:36 Anyone have anything? 15:57:02 I may be less active as I change assignment at Linaro a bit 15:57:16 to not cloud stuff 15:58:04 what are you moving to? 15:58:24 server architecture. qemu, firmware etc 15:58:33 nice 15:58:56 sounds interesting. Hopefully still some time for kolla 16:00:32 times up 16:00:36 thanks everyone 16:00:37 #endmeeting