15:00:26 #startmeeting openstack search 15:00:27 Meeting started Thu Dec 1 15:00:26 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:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:31 The meeting name has been set to 'openstack_search' 15:00:32 o/ 15:00:36 o/ 15:00:39 o/ 15:00:40 o/ 15:00:41 o/ 15:00:49 morning 15:01:24 https://etherpad.openstack.org/p/search-team-meeting-agenda 15:02:00 probably not going to be a very long one today, will get started 15:02:33 #topic Testing infra fixed 15:02:55 I worked with Andreas Jaeger a bit last week to sort out builds for our stable branches 15:03:11 Because infra was installing elasticsearch, it meant only one version was available for a given test job 15:03:26 And our liberty & mitaka branches weren’t compatible with ES 2 15:03:51 Infra added a stage to run a script in tools/test-setup.sh if it exists for any project 15:04:06 So now each branch can install whatever ES version it wants and we don’t have custom infra jobs for searchlight 15:04:18 cool! 15:04:27 Also makes it easier for devstack potentially 15:04:28 o/ 15:04:45 yeah, that's really nice 15:05:28 Yeah.. i gather there had been some other issues with various projects such that they didn’t want to maintain separate dependencies in the infra job definitions, so there we go 15:05:55 nice to have that sorted out. 15:06:05 Yep. And Andreas did most of the work, which was even nicer 15:06:16 :D 15:06:20 he is a very energetic fellow 15:06:50 :) 15:07:25 which brings me to.. 15:07:27 #topic Elasticsearch 5 GA 15:07:51 The 5.0 GA was a few weeks ago - https://www.elastic.co/blog/elasticsearch-5-0-0-released 15:08:59 I don’t expect any problems with it, but I’ll try to run Searchlight against it to check. We’ll need to decide what to officially support for the ocata release 15:09:26 We can support 2.x and 5.x but it’s awkward to run tests against both 15:09:27 wow: 25% - 80% improvement to indexing 15:10:02 i guess that's why they went from ES2 to ES5 15:10:03 yeah, last week I have a share about searchlight at beijing openstack meetup, someone has asked if we are going to support both es 2.x and 5.x 15:10:36 I think i accidentally ran SL against one of the 5.0 RCs a few months ago 15:10:56 But looking at the release notes nothing jumped out that would be a problem like the 1.x -> 2.0 move was 15:11:15 I think the versioning number change was to bring all their product lines in step 15:11:45 IIRC, v2 indices aren’t compatible with v5 15:11:57 I think due to changes in Lucene 15:12:11 i thnk they say 5 can read 2 15:12:16 but def not 1.x 15:12:44 OK, I’ll check. There’s a migration tool again for this version jump 15:13:06 There’s also a new scripting language 15:13:19 ipv6 support... 15:13:56 Yeah, ipv6 is a big one because we can make IP range lookups work properly, so that might be a reason to make a change. I’m hesitant to make the code aware of the ES version though 15:14:18 There’s also a better/safer scripting language 15:14:20 the new data structures sound good. however, they look like things that we can only use if we were to only support es5... or if we detect es version at indexing time. 15:14:42 Right - and we could do that reasonably easily 15:15:31 They also brought back dots in field names :) 15:15:51 the improvements in es 5 are quite substantial it seems. 15:16:29 Yeah, it’s been a while in the making. I’ll give it a try and see how painful it is; if we can take advantage of some features by detecting version i think i’m ok doing it 15:16:37 IPv6 support would be nice 15:17:35 So lei-zh , if anyone asks again tell them probably this release :) 15:18:05 Moving on.. 15:18:07 #topic Searchlight in os-ansible 15:18:21 TravT pointed this out yesterday 15:18:34 Rackspace added a review to add Searchlight to openstack-ansible - https://review.openstack.org/#/c/404419/ 15:18:59 I’d spoken to Neil a bunch of times about it in past summits but it looks like he finally got asked to work on it, which is good 15:20:23 yeah, nice to see it happening now. 15:20:26 Since it increases our audience, if they come looking for help with it in the RC room please assist them 15:21:01 * TravT make note to fix irc connectivity problems plauging him in the office. 15:22:27 Does anyone here use openstack-ansible? 15:22:55 rosmaita: ? 15:23:07 not me personally, but i know some people 15:23:34 no 15:23:36 We used ansible, but not the openstack project for some reason 15:23:47 So I may lend a hand 15:24:15 OK… 15:24:19 #topic Pipeline patch 15:24:42 lei-zh uploaded a new version of the publishing/pipeline patch yesterday i think? https://review.openstack.org/#/c/359972/ 15:25:02 There’s been some email discussion about the Zaqar use case with rob from horizon 15:25:19 \o/ 15:25:26 Ah, hello 15:25:42 Yeah, I usually lurk in these meetings if I'm around :) 15:26:05 I’ve been reading if not participating - how’s that going? 15:26:46 Interns are researching a few approaches, because we're not entirely certain on the data source yet (so they're looking at Panko too) 15:26:52 and there's a POC by the zaqar PTL 15:27:07 for doing things like table updates via websocket iirc 15:27:24 I dont know where you guys are on the publishing side of things? 15:27:45 We’re trying to get that patch in before o-2 15:28:06 Ah grand 15:28:31 It actually came up in another mailing list discussion about sanitizing oslo.messaging data; Zane suggested that functionality might be something other teams are also interested in, which is something we’ve tried to push a bit at summits past 15:29:08 The pipeline patch is already there, I'm going to add test cases for it 15:29:11 It’d be nice if that was more of a central project one day, but that might still be a way off 15:29:27 I’m going to try to review it today lei-zh 15:29:59 sjmc7: that's good, early feedbacks are appreciated 15:30:09 Incidentally, the ocata-2 milestone is Dec 12th - 16th 15:30:11 It'd be good if something could land; developing on top of multiple WIP patches across multiple services is a bit of a nightmare 15:30:28 sjmc7: Its usually the Thursday specifically, so 2 weeks today :) 15:30:38 yeah, i'd rather see it get it in this milestone. 15:30:38 hurray 15:31:02 otherwise it is too late for folks like rob to make any use of this release 15:31:20 Agreed; it’s a big priority for us this release 15:31:46 yeah, we try to settle down the pipeline as soon as possible, after that can focus on the detail of zaqar publisher 15:31:53 That's good to hear 15:32:25 the two use cases I outlined in the email thread are updating tables via push and being able to provide desktop style notifications, so live feedback in Horizon. 15:33:04 (just for anyone who didnt see the thread) 15:33:14 Yeah, that’d be nice. Zaqar already supports multitenant websockets so if we can feed it appropriately it makes sense 15:33:52 Yeah, we just need some of the code to settle so we can build on top of it. Even if its basic, since we're only really looking for POC work for now. 15:34:16 Right, so we won’t bikeshed too much of it since things’ll likely shift around a bit 15:34:32 Much as i love a good bikeshedding session 15:34:50 That was all i had on the agenda 15:34:55 #topic Open discussion 15:34:59 Yeah, I wouldn't get too hung up over long term issues, at least from our perspective. We're not looking for it to be feature complete first time round :) 15:35:14 It’s Openstack, nobody expects that :) 15:35:19 heh 15:35:45 I have a question 15:35:51 You may ask your question 15:36:09 Searchlight-UI; whats the status there? Anything that can/should be pushed to Horizon? 15:36:18 matt-borland / TravT ? 15:36:45 I'm still rather keen on making sure we stay on top of that for future work, despite the roadblocks people keep putting down. 15:37:03 i think that the flavor stuff in searchlight ui needs to be deleted because we merged that on master. 15:37:04 robcresswell, I would expect that the resource registrations should move into Horizon. 15:37:15 and what TravT said :) 15:37:24 it would be nice if instances were moved to horizon. 15:37:40 Yeah, i recall merging some stuff into our tree end of last cycle that maybe should’ve been in horizon 15:38:01 the key thing is we don't want to just delete it out of searchlight ui unless it is moved to a default activated panel on horizon. 15:38:10 TravT: Understood 15:38:16 yep, and that was why it went into SL-UI 15:38:53 And then I guess the followup question; what's everyone workload right now? I'm just finishing up create-net and tyr's form-preview patch. 15:39:09 I could probably find time to push on instances, and I know others are doing Identity/Users. 15:39:15 however, with the work we did last release to sort of co-locate new and old work on panels and just switch angular on or not, i think that things can merge on horizon even if angular isn't active because the javascript (and registrations) will still be available. 15:39:53 so searchlight ui should still be able to use them even though the panel hasn't been fully turned on... 15:40:34 Double-registrations may get a bit hairy 15:40:58 right, so it is best to delete the registration in searchlight ui and move to horizon. 15:41:02 I think it's only a problem if we double-register table columns. 15:41:24 which we could use .replace for instead of .append if we can't think of anything else. :) 15:43:28 TravT, matt-borland: Do you guys have any time to look at porting some of that content, or should I take that over? I'll probably be mostly free in a week or so. Just before O-2. 15:43:49 I don't have time to port it over 15:44:02 Cool, fair enough 15:44:20 Mostly, the paths have to change, but it's just a lot of code and a few assumptions. :) 15:44:44 Sure 15:44:54 I'll take a look then. Thats all from me :) 15:45:02 thanks robcresswell!!! :) 15:45:04 Ok, thanks 15:45:07 Anything else? 15:45:21 happen to see this part in the doc, http://docs.openstack.org/developer/searchlight/dev-environment.html#the-v2-elasticsearch-client 15:45:30 robcresswell: add me to any reviews though 15:45:38 TravT: Will do 15:45:47 lei-zh: yeah, we can maybe remove that now 15:46:36 ok, I'll take a look at it 15:47:02 Cool, thanks. Ok, if there’s nothing else i’ll end this in a couple of minutes 15:47:23 Thanks sjmc7 15:48:13 Ok, thanks folks 15:48:56 #endmeeting