18:02:03 #startmeeting sahara 18:02:04 Meeting started Thu Sep 25 18:02:03 2014 UTC and is due to finish in 60 minutes. The chair is alazarev. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:02:08 The meeting name has been set to 'sahara' 18:02:20 #link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda 18:02:40 #topic sahara@horizon status (croberts, NikitaKonovalov) 18:02:51 o/ 18:03:07 o/ 18:03:11 * SergeyLukjanov mostly lurking 18:03:13 hi again 18:03:20 all my patches are merged except https://review.openstack.org/#/c/118493/ 18:03:26 +1’s are welcome 18:03:36 how about +2s ? :) 18:04:34 tmckay: +2s are welcome too, but… slightly wrong audience 18:04:55 ah, horizon, lol. I didn't look 18:05:01 can't hijack w/ a shellshock ? 18:05:29 Nikita, Chad, any news? are we ok for J? 18:05:30 yeah, for open topics, we should discuss being nice and fixing up all our images for shellshock 18:06:57 it looks there is no our horizon huys, let’s move on 18:06:59 I think we're in ok shape. Sergey has our patches on the radar of their core team 18:07:10 crobertsrh: great! 18:07:11 sorry...I was distracted (baby crying) 18:07:14 #topic News / updates 18:07:22 all of the changes we need for Juno has been added to th rc1 mandatory list 18:07:27 (re horizon) 18:07:39 SergeyLukjanov: great too! 18:07:45 did our +.5 talk on sahara in paris get promoted to +1? 18:07:56 mattf, nope 18:07:58 i've been working on reviews and a few small bug fixes. also doing a bunch of downstream work to get Sahara j3 into RDO. 18:08:11 SergeyLukjanov, demoted to -1? 18:08:25 finally my patch was merged about updated rest api stuff 18:08:28 #info the new client release 0.7.4 is out and it will be a "juno release" version of client 18:08:41 anything outstanding for Sahara for Juno? Bugs, documentation that must still be fixed or reviewed? Blueprint status cleanup? 18:08:46 mattf, sounds like this 18:08:50 darn 18:08:56 we had a good run 18:09:06 mattf: 0.5 usually means 0, there is a rumor that person declined his topic becomes banned 18:09:13 aignatov, oh, a topic! We need to put checks back in so that doc-only changes (.rst files) don't run CI 18:09:24 or, agree that we can ignore failed CI on those and just approve 18:09:45 instead of beating on CI until it passes 18:10:05 changed Copyright notice on the user guide. Does the cluster run? 18:10:25 * tmckay shakes head ^^ 18:10:42 if it is not too hard I would vote on auto +1 on non-code patches 18:10:45 tmckay: I thinnk all of us agreed that we need such checks 18:10:49 I created images for Juno release 18:11:22 aignatov, should we make an action item out of it? What do we need, blueprint and spec? Who knows CI enough to write a spec? 18:11:42 sreshetnyak: tmckay was asking about the bash versions in those images. we might need to respin them to catch the shellshock vulnerability. 18:12:15 sreshnetnyak, yes, I wonder if it's worth adding post-install elements to DIB to patch shellshock. 18:12:25 Alternative is just wait for normal OS patches and respin later 18:12:39 well fedora already has the patches in F20 18:12:42 +1 to respin later 18:12:43 I wanted to get familiar with CI stuff for a long time, I can volunteer on this 18:12:50 +1 respin when os fixed 18:12:53 I think it's nicer to patch DIB ourselves in cases where the patch isn't in general updates yet. But, maybe others disagree 18:13:01 I bet shellshock isn't our biggest security threat 18:13:11 * mattf agrees 18:13:14 crobertsrh: agreed 18:13:14 elmiko: I'm not sure the Fedora patches are complete... yet 18:13:25 tosky: they're not, but they pass the first smell test 18:13:27 tmckay: anyway, we can approve pathches with non-related to docs -1s from CI 18:13:47 okay, wait for later. That was easy. 18:13:51 tnckay, I will check version of bash on the images 18:14:11 alazarev, +1 on volunteering 18:14:35 #action alazarev volunteers to add a blueprint/spec for doc-change-only filter on CI 18:14:59 sreshnetnyak, thanks 18:15:08 can we pre-+2 that spec? heh. 18:15:15 tmckay: probably it is easier just do it without spec :) 18:15:31 okay. just following rules ;-) 18:16:14 i'd agree that it's not substantial enough to warrant a spec 18:16:23 aignatov, +1 on +2 for doc changes with failed CI. From now on I'm just going to approve, no recheck 18:16:58 #agreed merge doc bugs even with -1 from CI 18:17:01 hmm, okay, how do nuke the #action? Or just leave it and mark it done next week 18:17:34 tmckay: it is good enough I think 18:17:44 tmckay: ++, approve all those patches 18:17:52 ok, no action items from previous meeting 18:17:53 * tmckay is really into process today 18:17:58 #topic Juno status and FFEs (SergeyLukjanov) 18:18:05 I’ll do the same :\ 18:18:10 so, the rc1 is ready 18:18:16 we've fixed all bugs 18:18:27 and only doc changes are open 18:18:31 the known bugs :) 18:18:32 * tosky hides 18:18:35 lol 18:18:42 #link https://wiki.openstack.org/wiki/Juno_Release_Schedule 18:18:43 sure, known :) 18:18:45 are you a QA guy or somethinig, tosky? 18:18:52 so, we'll have rc1 tag tomorrow 18:19:05 and master will be opened for Kilo dev after it 18:19:08 hidden QA :) 18:19:17 nothing else from my side 18:19:27 #topic Open discussion 18:19:50 sahara bug free, ship it! 18:19:50 aww, too slow. tosky saw it. 18:19:55 SergeyLukjanov: could you look at https://review.openstack.org/#/c/123836/ again, we have the links in place now 18:20:07 Is the Summit schedule correct? I don't see anything Sahara related (at least not as of yesterday) 18:20:37 crobertsrh, do you mean design summit? or summit itself 18:20:40 all, we should pay some attention to https://review.openstack.org/#/c/110576/ It's an interesting question, and might relate to swift creds in spark jobs later on 18:20:50 the first question or idea: reffering to recent patch fixing OSSA in our code, I think we need to have quick security checks someday 18:20:54 summit itself. I suspect our design summit topics are still being sorted out 18:21:21 it's been there a while, I mean to get to it ASAP. The question is whether or not Sahara should carry a compat class, or wrap oozie jobs in such a way that the config values are pulled in transparently 18:22:01 or, just make folks alter their jobs to read the config file (current solution) 18:22:53 aignatov, what kind of quick security checks? 18:22:57 tmckay: maybe a Spark user lib? 18:23:25 tmckay: just quick look by eyes and see what we have now :) 18:23:35 elmiko, possible, the same would relate to the Java action. But you'd still have to at least import it 18:23:48 tmckay: yea, tough issue 18:23:53 I think recent ossa fixed by alazarev was easy to detect :) 18:23:55 aignatov, ah, I thought you meant automated 18:24:06 agreed. Nice work, alazarev 18:24:27 grep “/tmp” sahara -r :) 18:24:37 lol 18:25:27 just realized that the flight to Summit is the day after Halloween. 18:25:36 I don't know if I can make it. Sugar coma. 18:26:29 You'll sleep great after sugaring out 18:26:34 lol 18:26:36 lol 18:26:50 just gotta have the family drop him off at baggage check 18:26:52 BTW, I don’t fly to Summit :( 18:26:57 :( 18:27:19 alazarev, walk? train? hitch? 18:27:22 alazarev: i hope you're not planning on swimming? 18:27:28 ooooh, teleport? 18:27:32 nice 18:27:37 TaaS 18:27:45 that's the real money crobertsrh 18:27:45 I'll get to work on that 18:27:52 travel as a service? 18:27:52 alazarev, that's too bad. We'll do design summit on IRC :) 18:28:00 Teleport aaS 18:28:03 WaaS, wormhole... 18:28:43 will fly to Hawaii, just to reduce pain :) 18:28:47 alazarev: ++ 18:28:48 elmiko, peacekeeper war? 18:28:51 Who *is* going to be at summit? We probably need to sort out our design sessions/leaders soon. 18:28:57 mattf: oooh, nice call /tipsfedora 18:29:14 crobertsh, good point. 18:29:32 i looked at the pad and too much of it is in my color 18:29:49 hey, i added a few token ideas =) 18:30:06 tmckay, crobertsrh, elmiko, mattf ... who else? 18:30:19 tosky, ? 18:30:19 me 18:30:24 I hope :) 18:30:35 SergeyLukjanov, of course, right? 18:30:39 * mattf can only lead sessions early in the conf... 18:30:46 Heh 18:30:48 mattf: should I add something to the pad? 18:30:49 lol 18:30:51 * crobertsrh knows why 18:30:51 and not early in the morning 18:30:57 tmckay, sure 18:30:59 crobertsrh, you are why 18:31:02 lol 18:31:23 tosky, if you have ideas, esp if you're coming 18:31:29 oh, ok 18:31:30 tmckay, bash version on images: http://paste.openstack.org/show/115377/ 18:31:46 * elmiko is excited to party with tosky 18:32:06 It might be a good idea to have a session dedicated to testing and such 18:32:25 sreshetnyak, thanks! So, Fedora is okay already 18:32:26 sreshetnyak: yay fedora! 18:33:46 anything else to discuss? 18:33:53 elmiko, I build Fedora images ~2 hours ago :) 18:34:01 not from me 18:34:09 sreshetnyak: yea =) 18:34:35 CentOS and Fedora images ~2 days ago :( 18:34:45 s/Fedora/Ubuntu 18:35:02 yes :) 18:35:53 ok, thank you guys! 18:35:58 #endmeeting