15:00:58 #startmeeting kolla 15:00:59 Meeting started Wed May 8 15:00:58 2019 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:02 The meeting name has been set to 'kolla' 15:01:07 #topic rollcall 15:01:19 Hi o/ 15:01:19 o/ 15:03:59 quiet one today it seems 15:04:14 #topic agenda 15:04:24 * Roll-call 15:04:27 * Announcements 15:04:29 ** Virtual PTG on 28th May & 29th May @ 12:00 - 16:00 UTC 15:04:30 looks like 15:04:31 * Review action items from last meeting 15:04:33 * Kolla whiteboard https://etherpad.openstack.org/p/KollaWhiteBoard 15:04:35 * Stein release status 15:04:37 * Train summit summary 15:04:39 * Virtual PTG 15:04:41 * Kayobe seeking official status 15:04:43 #topic announcements 15:04:52 #info Virtual PTG on 28th May & 29th May @ 12:00 - 16:00 UTC 15:05:24 We'll use a google hangout/meet for the call, maybe with video we'll see how well it works 15:05:24 I added two entries to agenda 15:05:33 ok 15:05:47 #link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005928.html 15:06:00 ^ has PTG meeting link 15:06:05 thanks hrw 15:06:16 any other announcements? 15:06:55 #topic review action items from last meeting 15:07:04 there were two for me: 15:07:07 mgoddard 15:07:09 mgoddard to try again to disable ocata publishing jobs 15:07:11 mgoddard to add dates to the PTG poll further out 15:07:32 I didn't do 1, but did do 2, and we now have a date for the PTG 15:07:46 #action mgoddard to try again again to disable ocata publishing jobs 15:08:03 #topic Kolla whiteboard https://etherpad.openstack.org/p/KollaWhiteBoard 15:08:19 updated my tasks there 15:09:19 thanks 15:11:09 CI jobs look mostly ok, except for bifrost on rocky and all ansible jobs on stable/stein 15:11:21 #action mgoddard to review CI failures 15:11:38 bifrost is something I ignore all the time 15:11:58 it is breaking too easy 15:12:14 yeah :( 15:12:19 would like to kill it 15:12:34 or atleast drop from CI 15:12:57 we use it in kayobe, so test it there too 15:13:39 it's only periodic or run when you change bifrost, so shouldn't affect most people. Good to be able to test changes though 15:13:56 #topic Stein release status 15:14:08 people asked why there was no 8.0.0 tag 15:14:20 15:03 < StingRayZA> out of interest, when does kolla-ansible 8.0.0rc1 become 8.0.0 ? 15:14:21 I've been a bit out of the loop due to the summit, but I expect we're in the same position as before 15:14:34 mainly we're waiting on centos RDO repo 15:14:50 #link https://review.opendev.org/651601 15:15:33 looks like it might be out: https://cbs.centos.org/koji/buildinfo?buildID=25934 15:15:38 I'll recheck that job 15:15:43 ok 15:15:55 can you add that info to whiteboard? 15:16:11 yeah 15:16:37 thx 15:17:30 done 15:17:35 coolio 15:17:58 Any other questions on the release? 15:18:03 no 15:18:32 Should probably do a review of recent bugs to see if there are any blockers as some people have been testing the RC 15:19:16 I wonder if we ought to tag images as stein-rc1 rather than stein? I think it might confuse people into thinking they're ready 15:19:42 that's for train 15:19:52 not an easy way to do an atomic switch of image tags though 15:19:55 yeah 15:20:08 #topic Train summit summary 15:20:23 #link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005923.html 15:20:30 nice slides 15:20:38 Sent a summary to the ML, think you already saw it hrw 15:20:40 thanks 15:20:46 yes 15:21:22 next topic? 15:21:36 Overall seemed to go well, quite a few people interested in using kolla and/or kayobe 15:21:54 #topic Virtual PTG 15:22:08 Date & time has been agreed 15:22:19 We have some ideas in the etherpad 15:22:25 #link https://etherpad.openstack.org/p/kolla-train-ptg 15:22:43 I think we have a habit of talking about things that don't end up getting done 15:22:54 Any ideas for focussing on things we will actually do? 15:23:14 I need to get that py3 done 15:23:29 Alternatively, making sure we get the important things done 15:23:37 that's number one for me this cycle 15:23:38 yeah, I think that's #1 for Train 15:23:55 aarch64 ci will then just 'jump in' 15:23:58 great 15:24:10 sounds like that's coming on well too 15:24:31 next topic? 15:25:26 #info Please come to the PTG with an idea of priority of features for Train - both for you and kolla overall 15:25:41 hopefully someone will read the meeting notes :) 15:25:47 ;D 15:25:52 #topic Kayobe seeking official status 15:26:10 what is kayobe in 20 words? 15:26:26 Bare metal provisioner & host configurer for Kolla Ansible 15:27:08 the missing part between 'I got rack of servers' and 'deployed OpenStack with k-a'? 15:27:16 we're open to how to approach this - whether a separate project or under kolla governance 15:27:20 exactly 15:27:46 I don't want to use PTL powers to force it in unless the team has bought in 15:27:51 sure 15:28:02 that's good topic for vPTG 15:28:16 sell it to us ;D 15:28:29 how ready for use, how many devs etc 15:28:42 #info Kayobe seeking official status during Train cycle. Please have a think about whether kolla should own it or it should remain separate. Will discuss at vPTG 15:28:54 sure, it's on the list 15:29:01 #topic Debian/Ubuntu Python 3 status (hrw) 15:29:07 #link https://review.opendev.org/642375 15:29:08 tada! 15:29:10 hrw: you're up 15:29:38 so, we are at step when images build and then ansible fails somewhere somehow 15:29:57 horizon, placement-api, cinder-api behave like apache2 is not even starting 15:30:26 do you have a local dev environment? 15:30:41 built images today, will to all in one to check 15:30:48 and then some multinode if needed 15:31:11 it's a lot easier to iterate and debug on ansible there 15:31:17 yep 15:31:40 stopped counting patches to other projects since that whole py3 stuff started 15:31:58 I remember we had issues with the wsgi script having a different name under py3 15:32:26 mgoddard: checked. in debian config files are same for py2/3 but need to investigate 15:32:52 as CI runs ubuntu so ;d 15:33:09 could be that apache is immediately exiting? 15:33:17 config error 15:33:18 any way to crank up the debug logs for apache? 15:33:22 yeah 15:33:26 apache2: Syntax error on line 80 of /etc/apache2/apache2.conf: DefaultRuntimeDir must be a valid directory, absolute or relative to ServerRoot 15:33:37 which is weird as it is set by envvars 15:34:06 mgoddard: debugs are one of things to try for sure 15:34:45 looks like the deploy reached the end 15:34:46 I dislike size of that patch but it could not be smaller ;( 15:34:53 and test-openstack failed 15:35:03 openstack server create errors out 15:35:15 probably due to placement container restarting 15:35:23 bingo! 15:35:42 that's why it is good to discsuss with someone ;D 15:36:31 here's the apache config: http://logs.openstack.org/75/642375/21/check/kolla-ansible-ubuntu-source/cb08acd/primary/logs/kolla_configs/placement-api/placement-api-wsgi.conf 15:36:51 this log is always useful: http://logs.openstack.org/75/642375/21/check/kolla-ansible-ubuntu-source/cb08acd/primary/logs/system_logs/docker-info.txt.gz 15:37:24 ;) 15:37:48 python-path=/var/lib/kolla/venv/lib/python2.7/site-packages! 15:38:16 thanks! 15:38:20 not sure about L80 of apache.conf - I think that's referring to a default config file rather than one we've written out 15:38:34 this one only has 25 lines: http://logs.openstack.org/75/642375/21/check/kolla-ansible-ubuntu-source/cb08acd/primary/logs/kolla_configs/placement-api/placement-api-wsgi.conf 15:38:38 api-wsgi.conf will rpobably be main issue 15:38:53 needs to be fixed anyway 15:39:12 crack open the image and see what configs it has. Sometimes we have to remove defaults in kolla IIRC 15:39:53 "docker run -it -u root CONTAINERID bash" is now far too often in history 15:40:18 I add --rm :) 15:40:44 indeed 15:41:02 'docker image prune' is quick 15:41:06 maybe also see what keystone is doing since it uses apache and seems to be working 15:41:15 reclamed 182GB in 2s 15:41:33 nice 15:42:06 any more on this? 15:42:15 next topic 15:42:24 #topic AArch64 CI status (hrw) 15:42:30 #link https://review.opendev.org/557659 15:42:39 it is more or less ready for use 15:43:04 I went through list of images it builds and removed those which do not build under Debian/aarch64 15:43:24 also removed whole monasca due to pypi dependencies which take huge amount of time to build 15:43:39 and we were crossing 3h time which is maximum available 15:43:46 ouch 15:43:54 are you planning to keep it experimental? 15:44:04 it depends on py3 thing 15:44:27 so once py3 gets in I will change it to normal non-voting 15:44:46 oh ok 15:44:51 now it is easier to run recheck only on it 15:45:16 as I can compare local job on aarch64/amd64 with CI 15:45:55 machine is hosted in London so networking etc is not an issue 15:46:09 have to check did infra added one change into zuul config or not yet 15:46:26 https://review.opendev.org/#/c/557659/44/tests/templates/kolla-build.conf.j2 has info what was removed 15:46:40 https://review.opendev.org/#/c/557659/44/docker/base/Dockerfile.j2 has that infra hack 15:47:24 questions? 15:48:26 Not really, will be a good thing for us to have 15:48:45 So dependencies are infra zuul config and kolla py3. Any others? 15:48:56 https://review.opendev.org/#/c/657370/ but you +2 it already 15:49:06 qemu-kvm thing 15:49:07 ok 15:49:26 Are you going to chase up infra? 15:49:36 rechase 15:49:45 will probably just open a bug for it 15:49:53 they're probably still settling after the summit 15:49:56 and add it into blueprint 15:49:59 exactly 15:50:10 If we're blocked on py3 anyway I guess it's not a huge rush 15:50:21 yes 15:50:44 ok. I guess that's all unless you have anything else? 15:50:49 nope 15:51:12 #topic OpenStack Ansible collaboration 15:51:16 One last thing :) 15:51:34 had a session with the OSA folks at the summit which was interesting 15:51:36 something to share k-a with and vice versa? 15:51:36 #link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005925.html 15:51:52 hopefully we can work together on some things this cycle 15:52:07 and kayobe into it 15:52:16 #info Kolla planning collaborate with OSA project during the Train cycle where possible 15:52:22 yeah, maybe 15:52:26 that's all 15:52:40 thanks for chairing and hints 15:52:47 thanks for attending hrw, would have been lonely otherwise :) 15:52:57 np 15:52:58 :) 15:53:08 #endmeeting