15:00:24 #startmeeting kolla 15:00:24 Meeting started Wed Feb 6 15:00:24 2019 UTC and is due to finish in 60 minutes. The chair is egonzalez. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:28 The meeting name has been set to 'kolla' 15:00:37 #topic rollcall 15:02:19 o/ 15:03:43 o/ 15:04:57 Hi, meeting agenda havent changed in a few weeks, no progress has been made since then 15:05:05 #topic announcements 15:05:39 Vote for summit talks is open, be sure to vote your favourite talks 15:05:49 thats all from me, any other update? 15:07:38 hi, is it the right time for general discussion? 15:07:44 yep 15:07:49 #topic open discussion 15:08:07 hi 15:08:11 managed 15:08:20 I wanted to chat a little bit about the patch series I've pushed recently 15:08:24 https://review.openstack.org/#/q/status:open+project:openstack/kolla+branch:master+topic:restrict-pkg-binary-distro 15:09:38 sure, what about? 15:09:49 we've been a bit lax about what goes inside our "binary" image templates, I wanted to fix it by checking in the gate for forbidden instructions, such as gem install, pip install etc 15:10:38 the rational being that binary image should only install software packaged for the distribution 15:10:56 if all required items exist in distro in needed versions 15:11:15 that will make many of our supported services unsupported the next day 15:11:27 like promethus only will be available for source 15:12:25 yeah, right... some of our images labeled as "binary" are really "source" images 15:12:42 for example prometheus 15:12:45 I like the idea but as Debian/stretch maintainerkindof I know that many things we may lack 15:13:17 so I consider that our prometheus "binary" image is a bug 15:13:59 or we may reconsider old idea of getting rid of binary/source from image names etc 15:14:08 whats considered a binary package? only rpms or debs or something doesnt need to be compiled 15:14:35 anyway, I've pushed the script to check for what's inside the binary templates, and pushed also a few patch to correct the mistakes I've found along the way 15:14:41 please take a look 15:15:00 ok, will look 15:15:49 egonzalez: I'm including everything that's packaged for the distro, so packaged in deb or rpm 15:16:13 mandre: so none of arm64 images are binary 15:16:16 everything else don't belong to binary distro IMO 15:16:20 we build dumb-init 15:16:55 hrw: dumb-init was the only thing I wasn't able to get rid of :) 15:16:59 not that I care much about binary images 15:17:10 mandre: grab package from Debian, extract, use dumb-init binary 15:17:28 mandre: I saw that idea somewhere in ohter container project 15:18:06 hrw: there's a package for rhel actually, we should be able to have it in centos without too much difficulty 15:18:09 but then it is no longer 1.1.3 15:18:19 or whichever ancient we use 15:18:48 thanks, that's all for me 15:19:14 what im more worried about is backwards compatibility 15:19:29 mandre: are you close to my burger place? you ended right when I got burger... 15:19:30 oh, almost forgot, egonzalez I've seen you posted a comment about depecation cycle 15:19:57 and current users needed to build both source and binary, in that case if i were an operator i'd just move to source everything 15:20:23 I think deprecation doesn't apply here 15:20:41 mandre yep, probably k8s images can be removed if nobody else are using them (we may need to ask first) 15:20:58 mandre: if I deploy debian-binary-prometheus* images now then on upgrade I will not get updates 15:21:14 unless someone does the work the package the apps 15:21:42 I've added release notes about the image being source only 15:21:46 with nowadays ops culture I highly doubt ;( 15:22:59 if I deployed debian-binary-prometheus* images and later realized it pulled binaries from github, I would feel cheated 15:23:21 can we talk about debian/arm64 CI job? 15:23:26 https://review.openstack.org/#/c/557659/ one 15:23:58 sure 15:24:15 mandre thanks, anything else on this topic? 15:24:32 egonzalez: no, I'm good this time 15:24:41 developer who was behind it got moved to other stuff so looks like it may land on my plate 15:25:20 I would like to get some opinions can we get that merged or should it get abandoned or sth 15:26:00 hrw: how much work is needed to polish the job? 15:26:46 mandre: have to dig in it as had other issues to handle 15:27:42 more CI is good, let's not abandon the patch if we can get it to work 15:27:50 ok, will continue 15:28:07 I assume you'll maintain that CI job? 15:28:21 unless gema assigns someone else 15:28:23 seems to work but randomly failing with timeouts of 3h 15:28:36 it is in china so maybe networking issues again 15:29:04 there are plans to move it to uk to get stability 15:29:13 hrm, maybe in that case is better not use infra mirrors and have your own in linaro cloud? 15:29:35 we will move it to uk and there is normal network access 15:29:44 and then we will decide to official or infra mirrors 15:29:50 sounds good? 15:29:53 nice 15:30:06 lgtm, patch looks ok 15:30:07 sounds like a plan 15:30:25 thanks 15:30:27 once is stable the job we may move to regular job from experimental 15:31:08 and do like nova has - several CI running separatelly? so will not block other jobs 15:31:55 yep, is 3rd party and cannot be voting iirc 15:32:03 yep 15:32:24 thx 15:33:04 thanks for the work 15:33:08 and burger is gone. 15:33:18 egonzalez: it simplfies work for us 15:33:41 as now I get fail/pass info once per week 15:33:54 which now means fail due to pip being pip 15:35:30 hrw a periodical job may help too, so dont have to check experimental every day to see if still working 15:36:11 egonzalez: zuul knows how to do periodic 15:36:18 iirc 15:36:46 tbh, experimental job doesn't provide much value unless you're creating a new CI job 15:36:53 yep, but need to add it to the list https://github.com/openstack/kolla/blob/master/.zuul.d/centos.yaml#L19 15:37:11 it has to run in the check pipeline non-voting to be a little useful 15:37:11 ok 15:37:59 hi folks, I'm here but in a workshop at the moment 15:38:15 yep, what we've been doing in k-a is add job which only runs on files changes and run allways as periodical, just to not over use infra resources 15:39:28 that's all from me 15:39:49 cool, thanks hrw 15:39:59 any other topic to discuss today? 15:41:20 any core team changes planned? 15:41:55 i'm thinking on one, if have some suggestions? 15:42:03 mgoddard: want to promote someone? 15:42:53 I mentioned someone to egonzalez a while ago, I think they have been more involved since 15:43:20 yep, i need to talk with him, been busy with $job recently 15:43:39 $life :( 15:43:53 spaking of life... 15:43:59 * hrw moves to next place 15:44:06 thanks for discussion guys 15:44:08 +1 15:45:26 egonzalez: this makes me think, we need to update kolla-coresec group 15:45:59 lots of people no longer in the core team in it 15:46:12 kolla-coresec group? 15:46:18 i'm not even in that group 15:46:24 there was a clean up a while ago. Were those people removed? 15:46:57 kolla-core was cleaned yes 15:47:01 maybe mandre meant kolla-core? 15:47:05 people in there still involved 15:47:20 mgoddard: https://launchpad.net/~kolla-coresec/+members 15:47:31 TIL 15:47:33 the people who get notified about CVE and 15:47:50 should probably have PTL in there :) 15:48:07 3 ex-PTLs 15:48:08 yep would be a good idea :) 15:48:21 will need to ask steven about that 15:48:26 mandre: do you have the ability to update that group? 15:48:35 or egonzalez? 15:48:40 no idea of the existence of the group 15:48:46 sdake is the admin 15:49:02 hi 15:49:04 I can't edit the group 15:49:08 which group 15:49:29 kolla-coresec 15:49:31 sdake https://launchpad.net/~kolla-coresec/+members 15:49:36 hey sdake, could you add egonzalez as admin on https://launchpad.net/~kolla-coresec/ ? 15:50:04 wahtis your launchpad id egonzalez 15:50:25 sdake egonzalez90 15:52:11 alright, need to go, thx guys 15:52:20 anyway, this expands outside the meeting discussion 15:52:25 fixed - anjoy 15:52:26 sorry 15:52:28 mandre thanks for comming 15:52:32 sdake thanks 15:52:33 I thought this was the channel, not the meeting :) 15:53:16 sdake no problem 15:53:23 any other thing to talk today? 15:57:35 lets end the meeting 15:57:41 thanks for comming today 15:57:44 #endmeeting