16:27:06 #startmeeting kolla 16:27:08 Meeting started Wed Jun 15 16:27:06 2016 UTC and is due to finish in 60 minutes. The chair is rhallisey. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:27:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:27:12 The meeting name has been set to 'kolla' 16:27:26 #topic Kolla-kubernetes 16:27:42 did anyone have any further comments 16:27:50 I appreciate any review guys 16:28:11 Yeah, I think I'm obsessed with getting us to the point where we're not carrying 7 patches on the Kolla side. 16:28:22 rhallisey, i will also do 16:28:38 wirehead_, it's because kolla-kube is new, we're sending out patches like crazy 16:28:42 it won't happen forever 16:28:46 :) 16:28:48 :) 16:28:53 thanks coolsvap 16:29:20 is there anything non-committers can do to help ? 16:29:34 Mech422, you can try it out :) 16:29:44 so looking at the topics.. 16:29:54 # topic Refactoring of build.py 16:29:55 I think there was some convo about the Kolla gates. 16:29:57 rhallisey: yeah - I'll prolly fire up a test run this weekend :-) 16:30:06 On the openstack-dev mailing list this morning. 16:30:07 #topic Refactoring of build.py 16:30:26 let's keep moving we're 30min in 16:30:44 no inc0? 16:30:56 rhallisey: he said he couldn't attend today 16:31:00 ok 16:31:04 I'll give a quick summary 16:31:53 inc0 has a bunch of patches up that also need review (sorry for nagging). The patches will making everything much more configurable 16:32:07 they should be easy reviews 16:32:28 #topic do we need tqdm? 16:32:37 #link https://review.openstack.org/#/c/325529/ 16:32:41 rhallisey, i added it 16:32:46 coolsvap, go for it 16:32:55 i was in the requirements meeting earlier today 16:33:07 where they wanted to know if we need tqdm 16:33:12 #link https://review.openstack.org/#/c/325527/ 16:33:14 i was looking for harlowja_ 16:33:32 and i need cores looking at the review 16:33:41 proposed by harlowja_ 16:34:03 I know inc0 tried it out. I haven't yet 16:34:14 and whether we want them in or not 16:34:27 and provide update on the requirements review 16:35:01 awsome, thanks coolsvap 16:35:22 #topic Non ini config 16:35:40 this might have been a inc0 topic also 16:36:02 this came up a few weeks ago on the mailing list 16:36:04 are we talking the merge_config? 16:36:09 yeah 16:36:20 we talked this in the ML. 16:36:35 i suggested custom merge modules which sdake seemed to like, never went any further 16:37:07 1. solution is using more merge stragy, like override, append 16:37:23 do you have a link to the thread 16:37:26 * rhallisey is looking 16:37:53 http://lists.openstack.org/pipermail/openstack-dev/2016-May/093936.html 16:38:00 #link http://lists.openstack.org/pipermail/openstack-dev/2016-May/093936.html 16:38:04 is that right? 16:38:15 perfect thx 16:38:17 http://lists.openstack.org/pipermail/openstack-dev/2016-May/093936.html 16:38:23 correct 16:39:05 unless someone is prepared to write those merge modules I would say we need an easier solution 16:39:14 pbourke, I didn't follow the thread closely, was there a solution agreed upon? 16:39:18 ok 16:39:20 rhallisey: not really 16:39:20 stupid question...doesn't that awesome config file tool support OS configs yet.. 16:39:28 dam - let me get name real quick 16:39:31 Mech422: crudini? 16:40:00 pbourke, so we may need to bump that thread and get the discussion going again 16:40:19 pbourke: no - RH did one that parses like every config file in the system 16:40:27 I read though and see if I have an idea 16:41:07 pbourke: http://augeas.net/ 16:41:11 augeas 16:41:32 interesting 16:41:52 i think the apache conf file is the hardest one. it is hard to tokenized. 16:41:54 pbourke: you have to 'teach' it the file format - but then its REALLY nice for updatign stuff 16:42:26 is augeas support apache config file ? 16:42:30 pbourke: Here's what it can handle already: http://augeas.net/stock_lenses.html 16:42:40 #link http://multivax.blogspot.co.uk/2011/02/managing-apache-config-with-augeas.html 16:42:55 might be a runner 16:43:06 we should look into it and follow up on the mailing list 16:43:11 thanks Mech422! 16:43:16 pbourke Mech422 how about we follow up on the ML 16:43:25 Jeffrey4l: I think so - its RH tool - so apache is under 'http' in that list 16:43:27 breath some life into that thread 16:43:40 thanks for the pointer Mech422 16:43:48 np 16:44:11 seems cool 16:44:30 k let's move to gates 16:44:32 it would be useful to more then just Kolla too... 16:44:49 #topic Gate stability and voting 16:44:56 #link http://lists.openstack.org/pipermail/openstack-dev/2016-June/097401.html 16:45:18 dmsimard made a good point about our gates 16:45:26 1. gate is buggy now. need more eye on it. 16:45:30 there are a bit flaky and are not voting 16:45:39 I agree Jeffrey4l 16:46:04 2. i think it is time to remove the `non-voting` flag to the ubuntu/centos gate job. 16:46:15 +1 16:46:29 considering kolla's priorities for N, this is definitely up there. Gating has been a weakness for kolla 16:46:29 +1 16:46:31 in this way, it will enforce the commiter to notice the build/deploy gate result. 16:46:55 that will force us to fix the flaky gates 16:47:05 mandre, that's a good point 16:47:18 Sam used to mention mirrors as a major blocker for making the gates voting 16:47:33 I dont fully understand it though tbh 16:47:47 so we're already using mirrors for pip and ubuntu packages 16:48:05 there is apparently mirrors for centos, since a few weeks ago 16:48:14 kolla failed most not because the repo mirror. 16:48:19 there's centos mirrors all around the world though no? 16:48:35 hi 16:48:40 pbourke: centos mirrors hosted in infra 16:48:41 dcwangmit01, hey :) 16:48:48 yes. centos mirrors around the world and it will use the fastest ones. 16:49:03 mandre: that would be faster sure, but I dont see how lack of infra mirrors could ever block kolla dev 16:49:46 mandre, what's the url? kolla do not use the centos mirror from infra. 16:49:51 will say one thing, making flaky mirrors voting will put off new contributors 16:50:09 let me find the announce email 16:50:21 Yeah. I know that dcwangmit01 tried several times to get a full passing set of gates and every time a different set failed. 16:50:50 http://permalink.gmane.org/gmane.comp.cloud.openstack.infrastructure/4286 16:50:51 pbourke, it could, but so will broken code that gets merged because of flaky gates 16:50:56 pbourke, but it is one thing we must do. otherwise, new commit may introduce more and more bugs. 16:50:57 Then again, flaky non-voting gates is will also spoil the average noob dev's tea. 16:51:08 rhallisey: 95% of failures are not code related 16:51:09 imo 16:51:21 they will rage quit 16:51:33 I was obsessive about "recheck"'ing the tests, each time getting a different set of failures for different reasons 16:51:44 I think a better approach is to start collecting a list of all failures from now on 16:51:47 create bugs for them 16:51:48 I do agree, but then that's lame to think our gate isn't passing 95% of the time 16:51:59 Im not saying they fail 95% of the time 16:51:59 Well, we can always split up the gates a bit more. 16:52:11 mandre, cool we can enable the centos infra mirror in kolla. 16:52:14 im saying when the do fail 95% of that is not related to the patch 16:53:10 9 mins left, now people are aware of the issue I suggest they reply to the ML thread 16:53:17 and we come up with some solutions 16:53:23 ya agreed 16:53:37 pbourke, do you want to start a thread or shall I? 16:53:43 or we could add onto daves 16:53:51 rhallisey: say we just use daves 16:54:07 k let's continue the discussion there 16:54:13 ok. 16:54:15 #topic Open Discussion 16:54:39 https://review.openstack.org/329808 16:54:39 here. 16:54:50 need review :D 16:55:06 is there any reason we wanted to enforce the new kernel 16:55:23 Jeffrey4l: did you check the log for the original commit? 16:55:30 Oh, so I noticed a few +2's on our Kolla patches already, but if someone could review https://review.openstack.org/#/c/327925/ that blocks a lot of other patches from being merged. 16:56:14 pbourke, the doc say aufs not works very well on the old kernel ( < 3.19 ) 16:56:18 didn't 14.04 not work for a time? 16:56:24 maybe that's why? 16:56:29 I've had issues building Centos for roughly the same reason. 16:56:55 wirehead_, you mean build centos on the ubuntu? it is a bug from aufs. 16:57:22 rhallisey, 14.04 works. Our CI is use 14.04 for host os. 16:57:35 No, building Centos images from stock Docker because of the same issue with AUFS. 16:57:42 not now, but a few months ago 16:57:55 I thought there was some discussion about it 16:57:58 could be wrong 16:58:13 oh one more thing everyone 16:58:17 even though aufs do not works. We should recommend the user to use other storage driver, rather than upgrade the kernel. 16:58:23 rhallisey, no idea for that. 16:58:30 since I know some people were here at 16:30 UTC 16:58:49 Jeffrey4l: I can get behind that. 16:58:52 according to the ML proposal the meeting is moved to 16:00 UTC 16:59:09 just a heads up for those that were late. We are at 16:00 UTC now 16:59:18 Jeffrey4l, kk 16:59:24 1 minute left! 16:59:29 rhallisey, we may need re-claim the meeting time and update the wiki page. 16:59:45 Jeffrey4l, its already up for review 16:59:50 i think might have been merged 16:59:51 cool 16:59:55 wirehead_, thanks. 17:00:02 Jeffrey4l, ya I think sdake is already on top of it 17:00:07 ok thanks everyone! 17:00:10 but i am still not sure how it came half n hour early for me 17:00:15 #endmeeting kolla