15:01:13 #startmeeting openstack search 15:01:15 Meeting started Thu Jan 21 15:01:13 2016 UTC and is due to finish in 60 minutes. The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:18 The meeting name has been set to 'openstack_search' 15:01:23 morning 15:01:27 o/ 15:01:47 o/ 15:01:48 o/ 15:02:37 allright, as usual agenda is here: https://etherpad.openstack.org/p/search-team-meeting-agenda 15:02:48 feel free to add 15:03:03 o/ 15:03:13 lakshmiS: this time must be less fun for you now that you are PST 15:03:16 ;) 15:03:43 yeah have to get up early 15:04:07 almost forgot last week :) 15:04:08 well, thanks for making it 15:04:21 so, mitaka 2 is done 15:04:33 i submitted the release tag request yesterday 15:04:35 https://review.openstack.org/#/c/270522/ 15:05:06 and it went through 30 minutes ago. https://github.com/openstack/searchlight/releases/tag/0.2.0.0b2 15:05:15 yay! 15:05:49 for the client, we probably won't do a release until the end of mitaka 15:06:14 gives us some time to play with it before setting it in stone 15:06:43 yep, agree with that 15:06:54 ++ 15:07:07 lhcheng found some feedback on it for us last night after the first two patches merged 15:07:19 so we should take a look at that 15:08:00 https://review.openstack.org/#/c/249076/ 15:08:13 comment in ps12 15:08:28 from Lin 15:09:08 basically 15:09:10 openstack search resource type list 15:09:13 instead of 15:09:29 openstack search resource-type list 15:09:44 hmm 15:10:29 there doesn’t appear to be any reason given for not using a dash 15:10:48 no, just the dean troyer doesn't like it 15:11:30 i guess i don’t really have a strong opinion on it. seems weird coming from a unix background 15:11:33 i suppose that one of the points of openstack client is some kind of consistency... which i think will be a little hard for us anyway. 15:11:45 i don't know 15:12:19 i'm inclined to see that third patch finished out https://review.openstack.org/#/c/260899/ 15:12:28 since it’s merged, we can note lin’s concern as a separate bug 15:12:42 then spend some time with it and ask for some feedback from the client team and ux team 15:12:57 and deal with as bugs before releasing client 15:13:29 yeah, i’d like to get that search functionality merged 15:13:49 then the client’s at a useful enough state we can release it 15:14:02 i think that approach -- merge & fix bugs -- makes sense, especially pre-official-release 15:14:27 being able to actually use it will make it easier for us to evaluate 15:14:36 moves the bikeshedding to a different patch 15:15:03 :) 15:15:27 I also think my patch to install it with devstack works now (although it seems to be stuck in zuul check queue) 15:15:30 https://review.openstack.org/#/c/268358/ 15:16:21 will test that:) 15:16:31 thanks 15:16:48 it is a little easier to test now that your first two patches merged yingjun 15:17:03 now there’s actually something there for it to register as an entry point? :) 15:17:20 yeah, kind of makes a bit of a difference... ;) 15:18:13 #topic bp and bug review slot 15:18:46 so, now that we're in mitaka 3 timeframe, i thought we should do a full BP and bug review time like we've done at the beginning of other milestones 15:19:10 we can either agree on an hour or so in addition to this meeting or perhaps dedicate next week's meeting to it 15:19:58 happy to do either; i think we should try to do it sooner than later 15:19:59 this is to just "groom" the list and help ensure priorities are set 15:21:18 yep. but we also need to start doing the work 15:21:27 hmm, i dropped connection 15:21:41 any copy paste action? 15:21:43 i’m gonna buy you an internet connection for christmas 15:22:03 i bought a fancy new ac1900 router over the weekend, hoping that might help 15:22:19 no, you didn’t miss anything, except that i am concerned that the longer we wait to decide on specs the less time we have to do them 15:22:28 do people have time tomorrow for spec review? 15:22:33 sure 15:23:11 maybe a little later in the day for lakshmiS ? 15:23:14 after 10:00 PST if its tomorrow since we have our internal meeting before that 15:23:45 tomorrow is my worst day for meetings this week 15:23:57 we could shoot for monday 15:24:19 waiting another week makes me a bit nervous; the cycle deadline is looming 15:24:32 monday should be ok for me 15:24:34 here's my availability: any time rest of today. 1 PM EST or later. 15:24:52 the latter part of that was for tomorrow 15:25:01 1 pm EST or later 15:25:48 after 1pm EST today or tomorrow works for me 15:26:03 me too, i think 15:26:05 these times are probably all bad for yingjun 15:26:11 yingjun: what is your timezone? 15:26:15 yep:( 15:26:24 how about earlier on monday? 15:26:27 23:26 now 15:26:31 my preference would be for tomorrow to get some time before tomorrow's demo 15:26:56 earlier monday work for me 15:27:12 :S i've got something monday AM... 15:27:45 what about this time tomorrow? 15:28:04 ok for me 15:28:05 15:00 UTC tomorrow 15:28:15 i can do that 15:28:47 um… yeah 15:29:21 resounding vote of confidence sjmc7? 15:29:33 checking calendar. yeah, i can do that 15:30:17 lakshmiS: you could delay the swift plugin demo 15:30:47 i will try. i might miss the later part of the meeting to drop off my kid to school 15:30:49 all, just FYI, lakshmiS volunteered to demo the swift plugin in an internal demo meeting tomorrow 15:31:05 good job, lakshmiS ! 15:31:20 nice 15:31:36 minus the notifications though! 15:31:45 ok, i'm a complete moron 15:32:05 tomorrow morning my daughter is giving her first presentation 15:32:21 is she demoing the swift plugin too? 15:32:36 i think the title has something to do with poor parenting 15:32:42 :) 15:32:42 :) 15:32:48 :D 15:32:51 if she does a good job, bring her to Austin 15:33:36 TravT: i went to a thing at my daughter's school where she read a story, and it began "if my dad wasn't always away on business trips" 15:33:44 got a lot of dirty looks from the other parents 15:35:04 wow 15:35:16 okay, here's what i propose 15:35:30 please just go spend time looking at specs today 15:35:41 add comments 15:36:17 and let's have a meeting tuesday at 15:00 UTC if needed. 15:36:26 works for me 15:36:30 +1 15:36:35 Sounds good. 15:36:40 ok 15:36:44 am i looking in the wrong place: https://review.openstack.org/#/q/project:openstack/searchlight-specs isn't showing a lot of specs 15:36:53 there aren't many specs 15:37:02 hurrah! :) 15:37:06 only those that had sufficient complexity 15:37:18 there are also some BPs, though they’re more straightforward 15:37:19 otherwise they are just BPs 15:37:31 they typically don’t need much discussion other than a pririoty 15:37:43 and then in next weeks regular meeting we will do a grooming of the BPs and the bugs for priority and targeting 15:37:46 anyone have an easy link to the BPs to look at? 15:37:50 yep 15:38:05 https://blueprints.launchpad.net/searchlight 15:38:15 https://bugs.launchpad.net/searchlight 15:38:26 ty 15:38:42 primarily the ones we need to look at on bp's are those targetted at mitaka and those without a priority. 15:39:00 thanks rosmaita 15:39:27 i'll send a meeting reminder to those here for the 15:00 Tuesday tie 15:39:30 time 15:39:39 #topic mid cycle 15:39:55 so, i wasn't planning on formally proposing a searchlight mid cycle 15:40:30 but i just wanted to mention that Steve and I both got approval to go to the horizon mid cycle and david-lyle said there will be plenty of room if we wanted to have some time on searchlight 15:40:42 https://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint 15:41:24 i am not doing any travel! 15:41:31 smart man 15:41:57 so, i'm just putting that out there. 15:42:29 i'm really hoping to have the horizon searchlight panel in pretty good shape by then 15:42:53 yeah, that’d be nice 15:43:04 * TravT which would be easier if i stopped spending 95% of my time doing reviews 15:43:44 #topic API docs 15:43:59 Just a note that creating API docs now has a new process 15:44:17 aww :( 15:44:17 so, when we create actual API docs, we should follow it 15:44:28 i've skimmed it and I think it should be better 15:44:37 lakshmiS: looks like they use swagger now 15:45:00 i know the previous API docs were kind of difficult to do and lakshmiS fought with them on glance a bit 15:45:14 Travis, do you have a link to the new process? 15:45:20 http://superuser.openstack.org/articles/what-s-next-for-openstack-application-developer-guides?awesm=awe.sm_hPDfT 15:45:33 Thanks. 15:45:45 Yeah, so just a heads up 15:45:57 #topic Cross Project Liaisons 15:46:22 there has been an active effort to better formalize communication across projects 15:46:47 and the reached out to all the PTLs to look at some specs on it 15:47:08 the most recent one ratified identifying specific liasons for various duties 15:47:20 https://review.openstack.org/#/c/266072 15:47:24 that's the spec 15:47:27 but 15:47:42 here's the wiki with the various liasions 15:47:43 https://wiki.openstack.org/wiki/CrossProjectLiaisons 15:48:05 it defaults to PTL, but there is opportunity for each project to divvy up the duties 15:48:49 i can do it unless anyone else has a burning desire to do so 15:49:34 umm, you can do all of them? 15:49:43 what are you volunteering for? 15:49:45 umm… reading 15:49:51 the oslo one, i hadn’t made it further down :) 15:50:29 relman looks like it probably should be the PTL 15:50:39 i think the interproject liasons could be different to concentrate more on a specific project 15:51:27 yeah, i put my name specifically on relman 15:51:36 guess i can do docs as well, though i don’t think that’d affect us much at te moment 15:51:42 Do we want an interproject liaison for each plug-in? 15:51:42 like searchlight liason for glance 15:51:51 i can do that for glance and swift 15:52:21 ok, i guess you can just add an entry 15:52:42 ok 15:53:07 i added my name for cross project spec liaison as well, but if other's have interest we can add more than one person 15:54:28 for vulnerability management, i thought sjmc7 and i would be good candidates as well 15:55:54 umm.. yeah, i can do that 15:56:04 ok, i'll add both our names their 15:56:06 there 15:57:15 Travis, do you think we need an interproject liaison with Nova? If so I can do that. 15:58:19 I don't know if we need to name one or not, but that'd be great if you do it if we need it 15:58:33 usually the named ones are those that have a really tight inter dependency 15:58:43 Ok 15:58:45 like nova getting angry at glance api 15:58:49 yeah - i’m not sure we’re enough on anyone’s radar for them to come mention things to us 15:59:23 ok, well update the wiki sections appropriately 15:59:30 #topic out of time 15:59:35 well, we're out of time for today 15:59:39 the action is spec review 15:59:59 #action (review specs https://review.openstack.org/#/q/project:openstack/searchlight-specs) 16:00:10 and we'll check in on Tuesday on that 16:00:22 sjmc7, i'll also start looking at your role patch 16:00:26 okey dokey 16:00:28 Thanks everybody! 16:00:32 #endmeeting