18:02:35 <alazarev> #startmeeting sahara
18:02:35 <openstack> Meeting started Thu Sep 11 18:02:35 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:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:02:38 <dmitryme> o/
18:02:39 <openstack> The meeting name has been set to 'sahara'
18:02:57 <alazarev> I’ll chair the meeting today
18:03:15 <NikitaKonovalov> hi
18:03:43 <alazarev> ErikB, NikitaKonovalov, RobLevas, SergeyLukjanov, aignatov, alazarev, bob_nettleton, crobertsrh, dmitryme, elmiko, jspeidel, mattf, skostiuchenko, sreshetnyak, tellesnobrega, themistymay, tmckay, tosky, ylobankov: meeting time
18:04:47 <SergeyLukjanov> o/
18:04:53 <SergeyLukjanov> I'm mostly not here today
18:05:03 <crobertsrh> hello/
18:05:24 <alazarev> ok, let’s start
18:05:26 <alazarev> #link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda
18:05:45 <alazarev> #topic sahara@horizon status (croberts, NikitaKonovalov)
18:06:11 <NikitaKonovalov> The status has not changed much
18:06:25 <NikitaKonovalov> we have some bug fixes and visual improvements on review
18:06:31 <crobertsrh> Yeah, there are a few bug fixes on review
18:06:47 <NikitaKonovalov> but these changes are not getting any attention from horizon team
18:06:52 <alazarev> I have 6 patchets on review in horizon
18:07:04 <crobertsrh> I have one change -1 workflow for now (swift trusts UI-side)...waiting for sahara merge of all the bits.
18:07:24 <alazarev> two of them are -1 waiting for new python client
18:07:36 <alazarev> -1 workflow
18:08:01 <alazarev> probably wil discuss this on Juno status topic
18:08:50 <alazarev> #topic sahara-juno-post-merge-changes
18:08:54 <alazarev> #link https://etherpad.openstack.org/p/sahara-juno-post-merge-changes
18:09:59 <alazarev> oh, this is for dashboard too
18:10:14 <crobertsrh> Oh..that reminds me...
18:10:25 <crobertsrh> Is the "Storm" integration still happening for Juno?
18:10:33 <crobertsrh> I haven't heard or seen much of it lately
18:11:10 <alazarev> yeap, I haven’t heard too
18:11:14 <SergeyLukjanov> alazarev, it's nested list object - just a link
18:11:31 <SergeyLukjanov> crobertsrh, sounds like nope
18:11:34 <alazarev> SergeyLukjanov: yeap
18:11:39 <SergeyLukjanov> I hope it'll be early K
18:11:45 <crobertsrh> Agreed...I will move that item to my Kilo pad that I'm starting
18:11:45 <SergeyLukjanov> alazarev, time to change topic
18:11:53 <alazarev> #topic News / updates
18:12:14 <SergeyLukjanov> #info now we have rss for specs
18:12:25 <SergeyLukjanov> #link http://lists.openstack.org/pipermail/openstack-dev/2014-September/045721.html
18:12:25 <elmiko> all the swift-auth patches are up, just waiting on gerrit to merge. could use a few more reviews on the last 2 patches.
18:12:36 <SergeyLukjanov> #info FFEs list - http://lists.openstack.org/pipermail/openstack-dev/2014-September/045448.html
18:12:40 <elmiko> that rss feature is cool
18:12:51 <SergeyLukjanov> #info summit sessions brainstorming - http://lists.openstack.org/pipermail/openstack-dev/2014-September/045435.html
18:12:57 <alazarev> SergeyLukjanov: is it supposed to be more useful than emails over gerrit?
18:13:03 <alazarev> SergeyLukjanov: rss
18:13:14 <SergeyLukjanov> alazarev, it's just an rss for approved specs
18:13:29 <alazarev> SergeyLukjanov: oh, it’s for approved
18:13:47 <SergeyLukjanov> folks, please, pay attention on summit sessions brainstorming
18:13:59 <tmckay> elmiko, I think all your patches are approved except for the doc one
18:14:11 * SergeyLukjanov disappearing
18:14:13 <tmckay> elmiko, do you have one that's not?
18:14:42 <elmiko> tmckay: yea, the one before doc. zombie periodic hasn't been workflow'd yet
18:14:55 <tmckay> yeah, did it
18:14:56 <elmiko> oh wai,t nvm
18:15:00 <elmiko> missed that one
18:15:09 <elmiko> and thanks =)
18:15:21 <tmckay> that's what I'm here for :)
18:16:21 <alazarev> I’ve found out that our pylint job near doesn’t work, so made some work on it, review are welcome: https://review.openstack.org/#/c/120837/
18:16:48 <tmckay> I don't have a lot of news, I've been doing a lot of reviews the last several days.  I have some ideas about how to use mesos as a component, I'll play some more and write a spec soon
18:17:29 <alazarev> ok, let’s move on
18:17:36 <alazarev> #topic Juno status and FFEs (SergeyLukjanov)
18:17:51 <tmckay> elmiko, we talked about a security guide
18:17:58 <tmckay> elmiko, any ideas on that?
18:18:24 <tmckay> maybe we don't have enough content at this point
18:18:33 <elmiko> tmckay: sure, we could start with the proxy domain stuff, and move on from there?
18:18:48 <elmiko> maybe we need to round up topics to start with
18:18:53 <tmckay> alazarev, although, didn't we want to publish a list of the ports that should be added to secgroups?
18:19:26 <elmiko> tmckay: maybe also something to talk about at summit?
18:19:26 <tmckay> we have secgroups, but I don't think we give any guidance (unless I missed it)
18:19:59 <tmckay> guidance == port list
18:20:14 <tmckay> well, endpoint list, whatever you want to call it
18:20:19 <alazarev> tmckay: probably we should share port list
18:20:33 <tmckay> for Juno?  Do you know the list? :)
18:20:53 <alazarev> tmckay: don’t think it is good idea for Juno
18:21:07 <tmckay> okay, that's fine with me
18:21:26 <alazarev> SergeyLukjanov: juno status update?
18:21:32 <tmckay> lets talk about a security doc for Kilo at Summit (if not before), like elmiko said
18:21:46 <alazarev> tmckay: +1
18:21:53 <elmiko> i added an item to the topic list etherpad
18:22:06 <tmckay> great
18:23:12 <alazarev> it looks like Sergey is not here, as I know Juno goes well, we will have rc around Sep 25
18:23:46 <alazarev> #topic Open discussion
18:23:52 <tmckay> yay!
18:24:23 <tmckay> so, it seems from the activity today, we can merge anything that is not a new feature and which doesn't break string freeze
18:24:40 <tmckay> this is my first freeze with +2 :)
18:24:56 <tmckay> I want to make sure I don't break anything
18:25:05 <alazarev> do we have string freeze now?
18:25:24 <tmckay> I thinks so, let me check the juno schedule and email
18:25:29 <alazarev> yeah, need to be more careful
18:25:52 <tmckay> https://wiki.openstack.org/wiki/Juno_Release_Schedule
18:25:59 <tmckay> this says it was all Sep 4
18:26:57 <alazarev> #link https://wiki.openstack.org/wiki/Juno_Release_Schedule
18:27:32 <alazarev> does anyone know why we check only critical errors by pylint?
18:27:51 <tmckay> maybe only because pylint made a lot of noise
18:28:09 <tmckay> I've found before that turning on pylint later in a project can be very noisy
18:28:11 <elmiko> no idea
18:28:39 <tmckay> getting rid of all warnings can be a lot of work for existing code if it hasn't been on since the beginning
18:28:55 <alazarev> I have guess “it works somehow after it was stolen from nova” :)
18:28:57 <tmckay> maybe we should work toward clean pylint in the background
18:29:19 <tmckay> non-voting, til it's clean
18:29:32 <elmiko> sounds like a good idea, i ran it after alazarev's patches went up and it didn't produce much output for me
18:29:45 <alazarev> tmckay: we have nova-developed script that checks only new warnings, so it will not -1 for old issues
18:29:58 <tmckay> oh, nice
18:30:14 <tmckay> then I would try more than just critical
18:30:18 <tmckay> see what happens
18:30:24 <elmiko> is there any documentation in our stuff about using pylint?
18:30:25 <crobertsrh> +1 to "see what happens"
18:30:46 <alazarev> elmiko: after patch - “Unique errors reported by pylint: was 1046, now 1046.”, before patch there were 57
18:31:11 <elmiko> alazarev: crazy! where did you see that report?
18:31:16 <tmckay> heh, only 1000, that's nothing ;-)
18:31:44 <tmckay> at 30 seconds per erorr to fix, that's only ...
18:32:02 <alazarev> elmiko: just “tox -e pylint”
18:32:28 <elmiko> huh, that's what i did but it looked clean. i must have missed something.
18:33:28 <elmiko> no big deal, i'll read up more.
18:33:51 <tmckay> fixing pylint errors would be a great project for new contributors
18:34:02 <tmckay> get familiar with gerrit, etc
18:34:45 <elmiko> +1
18:34:57 <alazarev> probably we should extend patterns for methods, vars, etc, I don’t see anything wrong with name “test_add_instance_to_node_group_id” (longer than 30 chars)
18:35:47 <alazarev> but we can do it one-by-one
18:36:20 <elmiko> makes sense
18:36:36 <alazarev> anything else to discuss?
18:36:54 <tmckay> nothing from me
18:37:16 <elmiko> nothing from me
18:37:23 <alazarev> okey
18:37:30 <alazarev> thank you folks!
18:37:32 <alazarev> #endmeeting