15:00:39 #startmeeting openstack search 15:00:39 Meeting started Thu Dec 8 15:00:39 2016 UTC and is due to finish in 60 minutes. The chair is sjmc7. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:44 The meeting name has been set to 'openstack_search' 15:00:48 o/ 15:00:59 https://etherpad.openstack.org/p/search-team-meeting-agenda 15:01:00 morning 15:01:05 o/ 15:01:24 might be a really quick one today 15:01:32 o/ 15:02:40 ok, let’s get started; some others may dribble in 15:02:49 #topic Elasticsearch-5 15:03:20 I fired up a fresh devstack with es-5 and everything seemed to work fine, with the exception of our devstack plugin 15:03:43 elastic.co changed the location of downloads. i filed https://bugs.launchpad.net/searchlight/+bug/1648255 to fix that 15:03:43 Launchpad bug 1648255 in OpenStack Search (Searchlight) "devstack plugin doesn't support elasticsearch 5.x" [Undecided,New] - Assigned to Ruslan Gustomyasov (rusik) 15:03:43 o/ 15:03:52 But other than that, think everything’s fine with it 15:04:28 So I may try to put a patch up to use the IP type for ipv6 fields if elasticsearch 5 is being used 15:05:06 well, that's super nice that changes don't seem to be required. 15:05:19 just to see it work... 15:05:22 Yeah. I think they made all their breaking changes with v2 15:05:57 That also means we could set ES 5 to be the CI default for ocata 15:06:27 hmm... i wonder if we should or not. 15:07:30 i mean should it be whatever is most widely deployed? or most recent? 15:08:02 dunno. i’d go with what people would install if they were deploying it from fresh, but if there aren’t any compatibility issues it doesn’t matter either way i suppose 15:08:53 given all the performance increases in 5, it seems like it would be what we'd recommend. 15:09:00 yeah 15:09:02 hi 15:09:06 hello! 15:10:07 well, i’ll see about making that change and then toss a coin about updating the default / CI version 15:10:13 hi caowei_ 15:10:45 #topic python 3.5 test jobs 15:10:48 that sounds reasonable... 15:10:54 i guess there are not too many deployments right now 15:11:09 no, probably not 15:11:35 sorry, i jumped the gun a bit there, over-caffeinated 15:11:43 so maybe newer version will be better 15:12:00 sort of on that note i see the fuel ccp is adding searchlight now: https://review.openstack.org/#/c/408651/ 15:12:28 cool 15:12:53 i’ve still not looked much at the os-ansible patch, i need to do that 15:14:23 ok.. any more on that? 15:14:57 not from me. 15:15:05 I'm just +1 on the move to v5 15:15:07 Me neither 15:15:13 but do we need a v2 test job? 15:15:21 we can’t have both 15:16:09 unless we make the py27 and py34 tests run with different versions 15:16:16 which is an option, although potentially confusing 15:16:42 fwiw, you probably want to make the call ASAP since O-2 is next week. I'd also vote for increasing it for newer deployers trying it for the first time :) 15:16:55 the more votes the merrier 15:17:07 You could do py27es2 etc, like Horizon does with Django. 15:17:18 (I think) 15:17:25 yeah… infra just spent 2 weeks unravelling our custom jobs 15:17:32 Ah 15:17:37 you’re next! 15:17:46 So you are not in their good books :) 15:18:01 well, i am now. i won’t be if i add one back :) 15:18:24 i'd a slightly +1 on py27 using es2 and py34 / py 35 being es 5 15:18:46 just to ensure we don't do something that breaks es2 15:18:59 not so keen on doing that because it overloads the test, but i guess it’d be ok if people understand that we’ve done it 15:19:12 talking of which 15:19:18 https://review.openstack.org/390699 got proposed for searchlight-client to enable py35 tests last week 15:19:24 +1 for both es2 and es5 tests 15:19:36 we should do the same for python 3.5, so maybe could use py35 for es 5 and py34 for 2 15:19:37 Well, you'd add a second test. But a single test run for py27 seems sensible 15:20:25 we might be able to do it properly with a second test; i think the infra objection was that the jobs were custom for searchlight 15:20:37 if it’s parameterized it’d be ok. i’ll look into it 15:21:07 since rob’s here, this brings me onto the next topic 15:21:13 #topic searchlight-ui reviews 15:21:25 there are a number of SL UI reviews from a while back 15:21:40 TravT: are they all still valid? i was planning to try to crank through them today 15:21:51 and is there anything needs to go into horizon itself? 15:23:42 https://review.openstack.org/#/q/status:open+AND+(openstack/searchlight-ui) 15:23:47 let me see... 15:24:42 i think tyr's sl-magic search patch can be abandoned 15:25:10 the themeable one was dependent on getting some theme work landed in horizon, but i think hurgleburgler didn't get that landed in horizon 15:25:39 i think i could update the instance usage aggregation patch 15:27:07 yeah, i guess any where the dependency didn’t merge are unlikely to be able to get merged 15:27:29 i can try running that one again and seeing if i'm wrong 15:27:47 robcresswell: did you start moving any instance stuff to horizon master? 15:28:08 TravT: No not yet, way too much on my plate :) 15:28:14 ok. 15:28:22 TravT: Waiting for some of my current patches to land before I start doing more, so just reviewing right now 15:29:40 Should be able to work on that in a week or so. Maybe over Christmas when I've got sick of family :) 15:29:50 :) 15:30:05 11am christmas day then? 15:30:32 * TravT pictures rob walking in on everybody eating breakfast and announcing he's got better things to do 15:31:09 TravT: That's about right 15:32:04 ok, last up 15:32:09 #topic ocata-2 15:32:16 As Rob mentioned, O-2 is next week (doesn’t time fly) 15:32:30 after that we won’t be adding any significant features 15:32:49 https://review.openstack.org/#/c/393617 15:33:23 yeah, i’ll take another look at that today 15:33:24 i got this one up, maybe have a look if you guys have time 15:33:30 Thanks 15:33:35 will do. it looked mostly all the way there 15:33:51 i won’t do a total freeze on all patches after o-2, but just no big changes that could break stuff 15:34:16 Sure 15:34:35 so that of course brings up the pipeline 15:34:43 looks like lei-zhupdated it 15:34:50 lei-zh: ^ 15:35:04 yeah, that's one of the big changes : ) 15:35:21 yeah, i’m gonna take another look at that as well 15:35:27 \o/ 15:35:29 Kevin_Zheng: did nova side land for notifications for server groups? 15:35:39 It would be really great if that could land 15:35:56 I've updated it today and will add more tests to cover 15:36:04 They 15:36:07 Have 15:36:12 ok, cool 15:36:18 But in old style 15:36:52 you mean unversioned? 15:37:01 But I already make it not always call nova API so not that much traffic 15:37:29 Yes and the data load is quite limited 15:37:52 i'd think server group changes are not very frequent 15:38:45 Yes, but I have already done it as security group rules when update and it works well 15:39:23 ok. i’ll be able to test that today as well 15:39:43 :) 15:40:27 that was all i had on the agenda. if anyone’s got anything else, go for it 15:40:30 #topic open discussion 15:41:01 Nothing from me, thanks for the updates :) 15:41:13 I'll be on vacation next week, but will try to keep an eye on pipeline patch 15:41:34 yeah, i’m likely to be out for 2-3 weeks as well 15:41:52 so i will pass the reins to travis 15:42:24 * robcresswell pictures sjmc7 like Santa passing over sleigh reins 15:43:04 i think we should plan on cancelling a few meetings... Dec 22, Dec 29 15:43:29 yeah, probably 15:43:56 although those weeks it would be fine for yingjun, lei-zh, Kevin_Zheng, others to meet if one of you guys want to run the meetings. 15:43:59 although a lot of folks don’t disappear for a week over christmas 15:44:55 yeah, we can get two +2s to make things work:) 15:45:34 sounds like lei-zh is volunteering to run those weeks. 15:45:38 :) 15:45:44 :) 15:45:59 ok, if there’s nothing else, thanks everyone 15:46:25 thank you! 15:47:31 thanks, bye:) 15:47:54 thanks sjmc7 15:48:25 #endmeeting