15:01:33 #startmeeting kolla 15:01:34 Meeting started Wed Mar 11 15:01:33 2020 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:37 The meeting name has been set to 'kolla' 15:01:39 #topic rollcall 15:01:41 \o 15:01:48 o/ 15:01:50 /o\ 15:02:19 mnasiadka: ? 15:02:24 osmanlicilegi: ? 15:02:43 (sad Christian does not join us) 15:02:46 yoctozepto , heya 15:03:14 cosmicsound: hey-hey (meeting running) 15:04:08 #topic agenda 15:04:15 * Roll-call 15:04:16 * Announcements 15:04:18 ** CentOS 7 jobs dropped on master 15:04:20 ** Kolla SIG/club signup: https://etherpad.openstack.org/p/kolla-sig 15:04:22 * Review action items from last meeting 15:04:24 * CI status 15:04:26 * infra images - what to do with patches? postpone to V proposal 15:04:28 * https://review.opendev.org/698753 adds support for Kolla 15:04:28 patch 698753 - kolla - WIP: Create 'infra' type of images - 19 patch sets 15:04:30 * https://review.opendev.org/707599 adds 'non-infra-base' image (not required for ^^ but can be useful to show split) 15:04:30 patch 707599 - kolla - WIP: introduce non-infra-base image - 5 patch sets 15:04:32 * https://review.opendev.org/706982 k-a patch 15:04:32 patch 706982 - kolla-ansible - WIP: Use 'infra' type of images - 8 patch sets 15:04:34 * Kolla --SIG-- (aka Kolla Klub?) https://etherpad.openstack.org/p/kolla-sig 15:04:36 * Ussuri release planning (kayobe) 15:04:38 * Ussuri release planning (kolla & kolla ansible) 15:04:40 #topic announcements 15:04:59 #info CentOS 7 jobs dropped on master 15:05:22 While we have not removed support for CentOS 7, prepare for it to break at any time 15:05:29 and we have https://review.opendev.org/692450 to eradicate c7 from master 15:05:30 patch 692450 - kolla - WIP: Remove support for CentOS 7 - 11 patch sets 15:06:25 ++ 15:06:41 yoctozepto: busy like hell 15:06:48 * hrw at kolla and horizon meetings at same time 15:06:50 true. Will need something similar for kolla-ansible at some point 15:07:08 #info Kolla SIG/club signup open 15:07:10 #link Kolla SIG/club signup: https://etherpad.openstack.org/p/kolla-sig 15:07:14 #undo 15:07:14 Removing item from minutes: #link https://etherpad.openstack.org/p/kolla-sig 15:07:21 #link https://etherpad.openstack.org/p/kolla-sig 15:08:08 All kolla users/operators/developers welcome - will discuss more later 15:08:30 Any others? 15:08:40 nope 15:08:55 #topic Review action items from last meeting 15:09:07 dougsz to write bug report about nova SSH nproc issue 15:09:15 dougsz finally did it 15:09:25 thanks 15:09:41 #link https://bugs.launchpad.net/bugs/1866190 15:09:42 Launchpad bug 1866190 in kolla-ansible "Number of SSH connections can be restricted by nproc" [Undecided,New] - Assigned to Doug Szumski (dszumski) 15:09:55 #topic CI status 15:10:33 #info Kolla CI broken due to horizon, pyscss & setuptools 46 15:10:51 #link https://bugs.launchpad.net/kolla/+bug/1866961 15:10:51 Launchpad bug 1866961 in kolla ussuri "ImportError: cannot import name 'Feature'" [Critical,Triaged] 15:10:59 we are going to discuss it with horizon team at the end of their meeting (same time as kolla one) 15:11:06 with hrw on #openstack-meeting-alt 15:11:24 joined 15:11:33 there is a workaround for it - we can downgrade setuptools to <46 in openstack-base 15:11:44 imho for now it's the only way 15:12:03 well there is a blacklist in requirements, but it won't last long 15:12:10 its too late 15:12:18 virtualenv gets latest virtualenv 15:12:19 we don't read gr 15:12:23 virtualenv gets latest setuptools 15:12:34 hmm 15:12:36 so once we use upper-constrains etc we have v46 15:12:56 we could reinstall based on gr 15:13:01 just like devstack actually does 15:13:50 to be honest I prefer to install "setuptools<=46" rather than use GR there. 15:14:01 GR will fail once 46.0.1 came 15:14:01 <46 15:14:06 yes. < 15:14:16 it seems like the best option at the moment 15:14:37 ok. will send patch for review after meetings 15:14:41 gr does that 15:14:44 for master and train 15:14:44 hopefully distros will not pick up 46 15:14:45 <46 15:14:53 gr does !=46 last I saw 15:14:58 yoctozepto: it does now? was !46.0.0 15:14:58 hmm 15:15:12 sorry, you could be right, I saw too many things 15:15:18 can't unsee 15:15:51 I've seen things you people would not believe... and better do not try to google for them. 15:15:55 ok. Let's see what horizon say later, but sounds like we have a plan 15:16:08 yeah, it was lame 15:16:09 next thing? 15:16:15 something odd happening in Stein&Train regarding in-kolla ceph (yoctozepto) 15:16:28 mhm, observed, all jobs fail 15:16:38 not ubuntu afair 15:16:40 but centos 15:17:36 doesn't look great 15:17:38 http://zuul.openstack.org/builds?project=openstack%2Fkolla-ansible&job_name=kolla-ansible-centos-source-ceph# 15:18:12 last pass on 4th 15:18:14 I am not a fan of ceph recently. too many rebuilds 15:19:16 cat: /var/lib/ceph/osd/a1ad5231-566a-4af1-aa47-038cbccbf2c0/whoami: Permission denied 15:19:20 https://bae8a59a03658584228a-8f7750086e5a0cc034f577473702e18b.ssl.cf2.rackcdn.com/711905/2/check/kolla-ansible-centos-source-ceph/5e93b6b/primary/logs/ansible/reconfigure 15:19:24 weird, eh? 15:19:26 funky 15:19:33 mgoddard: might be related to new packages from Storage SIG 15:19:36 did not have time to deal with it 15:19:40 oh right 15:19:49 raise a bug, assign to me - I'll look into that (but soonest tomorrow) 15:20:12 #action mgoddard to raise a bug on Ceph job fails 15:20:23 #action mnasiadka to look into Ceph job fails 15:20:35 * yoctozepto to cheer them up 15:20:45 Hi everyone, quick question, let say I want to rebuild a container run command in order to test what's going on with a failing one 15:20:45 #topic infra images - what to do with patches? postpone to V proposal 15:20:56 if I want to use dumb-init 15:21:05 hi Fl1nt we're just in the meeting atm 15:21:10 https://review.opendev.org/698753 adds support for Kolla 15:21:10 patch 698753 - kolla - WIP: Create 'infra' type of images - 19 patch sets 15:21:14 https://review.opendev.org/707599 adds 'non-infra-base' image (not required for ^^ but can be useful to show split) 15:21:15 patch 707599 - kolla - WIP: introduce non-infra-base image - 5 patch sets 15:21:23 https://review.opendev.org/706982 k-a patch 15:21:23 patch 706982 - kolla-ansible - WIP: Use 'infra' type of images - 8 patch sets 15:21:33 @mgoddard, ok sorry, which time will be best to reach out lately? 15:21:40 ok, infra stuff 15:21:44 Fl1nt: in about 40 minutes 15:21:45 Fl1nt: in 50 minutes 15:21:51 ;d 15:21:53 ok noticed that, thx 15:22:05 non-infra-base is now dependency of infra patch 15:22:20 as it gives nice separation we need 15:22:52 it only stores INSTALL_TYPE variable basically as we do not need it in 'infra' images 15:23:05 https://blueprints.launchpad.net/kolla/+spec/infra-images has a bit more info 15:23:28 * yoctozepto diving in blueprint 15:23:59 with feature freeze in ~month I would prefer to postpone it to V cycle and concentrate our efforts on adding C8 and removing C7 15:24:41 as infra images do not give us nothing new basically and require time to test, improve docs etc 15:24:52 makes sense 15:25:09 although there may be some small things we could do in U 15:25:18 non-infra-base only iirc 15:25:26 rest of stuff is self contained and simple 15:25:48 do we need a non-infra-base image? It looks like it only adds ENV var 15:25:52 we need 15:26:06 if you have ENV in base then binary-base != source-base 15:26:15 and we need ENV for binary/source images 15:26:25 yeah, but only 2 images depend on it - kolla-toolbox and openstack-base 15:26:29 we could just add ENV to those 15:26:36 +1 15:26:37 so non-infra-base is better/easier than injecting ENV to all binary/source images like I did before 15:27:01 that's not what I'm suggesting 15:27:03 mgoddard: ok. can be done simply 15:27:37 ~unrelated: should kolla-toolbox depend on openstack-base? 15:27:40 mgoddard: there can be other binary.source images than those two 15:27:57 monasca-thresh and openswitch-netcontrold were on list 15:28:25 and we have to rewrite dockerfiles anyway then injecting ENV vars is simple 15:29:11 mgoddard: there was attempt to do that 15:29:24 mgoddard: k-t is always binary, o-b is binary/source 15:29:29 netcontrold should be infra 15:30:01 it is either binary or source 15:30:08 currently, yes 15:30:08 as 'only one way' 15:30:15 but it should be infra 15:30:40 ok 15:30:57 monasca-thresh is a weird one because it depends on storm 15:31:21 might need to make a special case for it 15:31:35 there will be some exceptions probably 15:31:39 yeah 15:31:42 always :) 15:32:24 ok, so that's non-infra-base 15:32:39 there are two hard parts IIRC 15:32:46 yes? 15:32:57 1. how to build images with a common base 15:33:06 2. how to provide a smooth transition 15:33:26 let's start with 1 15:33:29 1. build binary and then source on same machine, then push 15:33:43 the best option 15:33:57 otherwise you have to build binary, push, pull, build source, push 15:34:05 which result in huge network use 15:34:11 or 15:34:13 which is worse than we have now 15:34:18 build base, push 15:34:29 then 3 separate jobs to build binary, source, infra 15:34:39 or :D 15:34:41 right 15:34:47 with pipelines 15:34:49 mgoddard: ++ 15:35:09 CI is one thing 15:35:15 we should also think about what users will want 15:35:29 generally they do not want to build both source & binary 15:35:33 --noinfra switch gives old style images 15:35:58 and then for k-a we need to implement "use_infra_images: boolean" in globals.yml 15:36:18 this is for the transition? 15:36:43 not only 15:37:18 if user1 wants own images then they can do kolla-build --noinfra to get only source images and deploy from them. 15:37:33 or builds source and gets infra+source ones 15:37:53 you do not need to build both binary/source images. 15:37:59 as user 15:38:07 we as project have 15:39:26 it would be good to aim to have everyone on the same pattern eventually 15:39:45 2. transition - now upgrade is from blablah-horizon:stein -> blablah-horizon:train right? 15:39:52 i.e. remove --noinfra in the long term 15:40:13 so it will be blablah-binary-mariadb:train -> blablah-infra-mariadb:ussuri etc 15:40:52 when you run 'docker ps' is it still 'mariadb' container 15:41:31 I don't see why we would want to keep them separate 15:41:35 but I never did k-a upgrade so hard to tell 15:41:41 you mean for external integrations? 15:41:53 k-a will handle it 15:42:05 mgoddard: --noinfra was added as someone asked for old way 15:42:23 +1, it will probably be required not to break tripleo 15:42:31 they can do --noinfra ;D 15:42:34 (and k-a) 15:43:00 yoctozepto: "I don't see why we would want to keep them separate" 15:43:10 could you expand? 15:43:26 mgoddard: infra still source/binary 15:43:36 yoctozepto: expand? 15:43:38 mgoddard: I guess we could fix up tripleo 15:43:50 hrw, mgoddard: your discussion about --noinfra switch 15:44:22 so you think we should not provide a --noinfra switch? 15:44:28 mgoddard: exactly 15:44:32 ok 15:44:33 just my gut feeling 15:44:37 our way or the highway 15:44:44 exactly 15:44:48 lol 15:44:51 now switching topic a bit 15:44:58 horizon stays with pyscss for ussuri 15:45:12 so we must use the workaround forever 15:45:19 thank you for your attention :-) 15:45:39 we will shout at then in V 15:45:45 is there no way to fix pyscss? 15:45:46 and then deprecate horizon 15:45:57 mgoddard: very easy, harder to do release 15:46:01 mgoddard: fork, rename 15:46:02 why? 15:46:13 mgoddard: abandoned :S 15:46:21 then fork? 15:46:32 mgoddard: 16:32 < rdopiera> hrw: we don't have the resources to take on more projects 15:46:34 mgoddard: horizon does not like forks :-) 15:46:44 so maybe we fork 15:46:48 kolla does not like pinning setuptools 15:46:49 it is logged channel so I will not comment 15:46:56 and propose patch to horizon 15:47:18 yoctozepto: and will you maintain it? it has huge amount of issues and some PRs... 15:47:35 hrw: issues closed :D "final version" 15:47:36 and once you fork people will came with ideas, changes, issues and expect you to maintain 15:47:41 we only need to get it past this issue 15:47:58 pyscss46 ;D 15:48:29 tbh, I don't mind pinning setuptools but I think it will come back to bite us 15:48:38 sooner or later but will 15:48:48 devstack will break on 46.0.1 15:48:58 anything will 15:49:01 ^ indeed 15:49:17 requirements fix was done in a rush without realizing what needs to be done 15:49:31 that's my personal opinion 15:49:35 +1 15:49:39 +1 15:49:52 anyway, suggest we pin and ignore for now :D 15:49:52 ok, what's next on agenda? 15:49:58 it's not longer yours, nor personal now 15:50:12 #topic Kolla --SIG-- (aka Kolla Klub?) https://etherpad.openstack.org/p/kolla-sig 15:50:37 almost ate you alive for calling it SIG 15:50:43 indeed 15:50:58 WILL EVERYONE JUST STOP CREATING SIGs 15:51:09 I thought they were supposed to be a lightweight thing 15:51:10 yeah, we got the message there 15:51:16 nvm 15:51:17 supposedly not 15:51:25 I don't really care what we call it 15:51:29 Kolla klub 15:51:33 i like "Kollaborators" for members of Kolla Klub 15:51:44 yeah 15:51:55 shame the etherpad is now called kolla-sig :) 15:51:56 let's do something good 15:52:04 mgoddard: oopsie :-) 15:52:29 anyway, if anyone is listening/reading - do sign up https://etherpad.openstack.org/p/kolla-sig 15:53:05 mgoddard: are we listing only one role? 15:53:13 mgoddard: aren't you operators as well? 15:53:16 suggest if people start discussions here we direct them to the pad? 15:53:32 mgoddard: +1 15:53:42 yoctozepto: you can call yourself the fairy godmother if it pleases 15:53:43 you can always create new etherpad and add info in old one with link to proper one 15:54:05 mgoddard: oh yeah 15:54:35 I'll give it a few more days then start approaching some people more directly 15:54:37 kolla club :D 15:54:50 you signing up cosmicsound ? 15:54:51 mgoddard: :O 15:54:55 nope 15:54:56 Marcin Juszkiewicz proposed openstack/kolla master: openstack-base: pin setuptools < 46 to get horizon working https://review.opendev.org/712485 15:55:00 assassins among us 15:55:16 cosmicsound: out of interest, why not? 15:56:35 So once we have a few more names on the list, how should we proceed? 15:56:45 Schedule a first meeting, to discuss... 15:57:32 ...how great we are 15:57:58 conspiracy theories about making openstack grate again 15:58:26 good idea 15:58:44 it grates all the time, hrw 15:59:02 I think first meeting should be a meet and greet, and work out the scope of the group, plan future meetings etc. 15:59:09 +1 15:59:13 +2 15:59:14 +1 15:59:16 as we have no other idea 15:59:26 we need to gather them ;D 15:59:32 get people to sign up for bios/case studies etc. 15:59:47 Tue/Thu same time as this meeting? 15:59:55 for start 16:00:05 I have other ideas (expressed on ML), but want to hear what others think 16:00:22 let's poll for times 16:00:34 we have emails 16:00:47 but often this time slot gets picked 16:01:06 #topic open discussion 16:01:18 none 16:01:22 Any other things to cover before we close? 16:02:01 one question 16:02:04 sure 16:03:23 Not sure how to follow-up with tripleo regarding making uwsgi available for install 16:03:51 mgoddard , i did not made any contribs to code for kolla 16:04:12 was thinking is more suitable for whom contributed code 16:04:12 cosmicsound: nevermind. kolla-klub is kind of devs/users stuff 16:04:29 cosmicsound: to gather ideas from users etc 16:04:30 cosmicsound: it is primarily for operators 16:04:31 right well me i 16:04:36 +1 16:04:41 in* 16:04:58 generalfuzz: you mean? 16:05:00 other people have been confused about that, I will try to make it more clear 16:05:02 if this brings me closer to a production ready k-a deployment 16:05:13 seems best way to meet more people involved 16:05:18 https://review.opendev.org/#/c/710879/ 16:05:19 patch 710879 - kolla - Install uwsgi for Keystone - 14 patch sets 16:05:24 that is the plan :) 16:05:28 exchange ideas or share knowledge alike 16:05:49 generalfuzz: there is the #tripleo channel 16:05:54 cosmicsound: I assume that we have far more users than developers in kolla. and we implement developers' ideas rather than users' ones as we do not know them 16:06:22 generalfuzz: and cloudnull is our local point of contact 16:06:54 ok, thanks 16:06:58 generalfuzz: macros.enable_extra_repo(['epel']) is what you need btw 16:07:09 or sth like that I named it 16:07:23 hrw: where? 16:07:32 will comment in gerrit 16:07:40 thanks 16:08:12 generalfuzz: the package would be provided by RDO rather than tripleo, but both are connected teams 16:08:28 ohmy 16:08:31 generalfuzz: I think for PoC EPEL is fine 16:08:42 integrating external ceph, aint so simple as planed 16:09:16 generalfuzz: have you looked at how to run uwsgi? Does it need to be a second container, or second process in a container? 16:09:33 We can probably end the meeting and carry on 16:09:38 Thanks all 16:09:41 #endmeeting