15:00:53 <sjmc7> #startmeeting openstack search
15:00:53 <openstack> Meeting started Thu Mar 16 15:00:53 2017 UTC and is due to finish in 60 minutes.  The chair is sjmc7. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:56 <openstack> The meeting name has been set to 'openstack_search'
15:01:31 <lei-zh> o/
15:01:33 <sjmc7> Morning all
15:01:37 <Kevin_Zheng_Hex> o/
15:02:07 * gibi is lurking
15:02:26 <lei-zh> Kevin_Zheng_Hex, your new irc nic looks cool
15:02:56 <Kevin_Zheng_Hex> Hah, I cannot use irccloud at home, so I use HexChat
15:03:13 <sjmc7> :)
15:03:24 <sjmc7> Travis is out this week
15:03:38 <sjmc7> so we’ll get started. since gibi is lurking:
15:03:39 <sjmc7> #topic Nova
15:04:10 <sjmc7> i took a look at https://docs.openstack.org/developer/nova/notifications.html and it looks like versioned notifications shouldn’t be too hard to use; the payload is quite similar to the unversioned ones at present
15:04:32 <sjmc7> one thing i wondered is whether we can JUST support versioned notifications or we have to support both
15:05:04 <sjmc7> the main problem with leaving both paths is that the old one won’t get tested
15:05:14 <Kevin_Zheng_Hex> versioned still missed alot
15:05:34 <sjmc7> oh? maybe i didn’t look hard enough :)
15:06:05 <sjmc7> the payloads looked quite exhaustive
15:06:07 <Kevin_Zheng_Hex> sorry, you mean for the nova list case or the whole thing?
15:06:09 <gibi> yeah versioned is not in feature parity with the legacy yet
15:06:22 <sjmc7> i mean in terms of searchlight receiving them
15:06:26 <Kevin_Zheng_Hex> instance is almost done
15:06:27 <gibi> but if you have a list what is the most important thing missing then we can push that
15:06:36 <Kevin_Zheng_Hex> but overall still missed alot
15:07:04 <sjmc7> ok. if there are specific fields that are missing (esp from instances) then file a bug/bp
15:07:13 <Kevin_Zheng_Hex> BTW, I noticed that instance.update didnt send out versioned notification
15:07:30 <Kevin_Zheng_Hex> and the legacy one didnt include description
15:07:45 <sjmc7> gibi: what’s your feeling on how people deploy nova? are they switching to versioned notifications?
15:07:54 <gibi> Kevin_Zheng_Hex: we transformed the instnace.update already so you might hit a bug
15:07:59 <sjmc7> if there are differences between versioned and unversioned that makes me want to just choose one
15:08:38 <gibi> sjmc7: by default nova emits both legacy and versioned but I think nobody really switched to consume the versioned one yet
15:08:47 <gibi> sjmc7: mostly due to the missing feature parity
15:09:08 <Kevin_Zheng_Hex> yeah, too much to notify :)
15:09:26 <gibi> you can see the current status of the versioned transformation here https://vntburndown-gibi.rhcloud.com/index.html
15:09:39 <gibi> this not just includes what is ready but also what has some patch up
15:10:24 <sjmc7> ok. for now then maybe we don’t have to switch to versioned very urgently?
15:10:29 <gibi> anyhow if you can come up a list of important notifications to transform I can make that a priority on the nova side
15:11:08 <gibi> sjmc7: nova - searchlight integration depends on that searchlight switches to versioned notification
15:11:52 <sjmc7> ah, ok. so that means we would need to support both paths?
15:12:19 <sjmc7> or force people to enable both, i guess?
15:12:32 <gibi> sjmc7: by default nova emits both
15:13:52 <gibi> sjmc7: #link https://github.com/openstack/nova/blob/master/nova/conf/notifications.py#L86
15:14:02 <sjmc7> ok.. i’m just trying to figure out whether we can drop support for unversioned or not. it looks like not, given that some types aren’t implemented
15:14:43 <gibi> sjmc7: please list those types and then I will try to progress with those. But yes if someting is missing today then you cannot just use the versioned today but you have to use both
15:14:47 <sjmc7> i guess we can begin on making the change and maybe drop the old code base if it’s appropriate later in the release
15:14:48 <Kevin_Zheng_Hex> yeah, at least for a few releases
15:15:17 <sjmc7> the nova notification handler is already the most complex code we have, and i fear having two slightly different copies of it is going to be even more complicated
15:15:53 <sjmc7> at the very least we’ll begin work to switch over to consuming them, and see how things are going in a few weeks. if there are events that we need missing i’ll let you know
15:16:02 <Kevin_Zheng_Hex> Hmm, actually we have only instance/sg/flavor
15:16:09 <Kevin_Zheng_Hex> handler
15:16:18 <sjmc7> yep. and many of those are implemented
15:16:25 <Kevin_Zheng_Hex> flavor is already versioned
15:16:31 <Kevin_Zheng_Hex> instance is almost done
15:16:50 <Kevin_Zheng_Hex> maybe we can only support versioned
15:17:01 <gibi> sjmc7: cool, thanks!
15:17:35 <Kevin_Zheng_Hex> I mean instance versioned notifications are almost done in Nova side
15:18:26 <sjmc7> yeah, we should look at the list carefully and let gibi know if anything’s missing we really need
15:18:34 <sjmc7> ok, moving on
15:18:40 <sjmc7> #topic BPs tagged for pike
15:19:07 <sjmc7> i’ve updated https://blueprints.launchpad.net/searchlight a bit
15:20:05 <sjmc7> most of what’s on there is work that’s been discussed, but if anyone’s got other stuff then feel free to tag it for pike or let me know
15:20:26 <sjmc7> i’m in the process of adding an ES 5 test job since it’s easy to break things
15:21:53 <sjmc7> #topic reviews
15:22:21 <sjmc7> https://review.openstack.org/#/c/444095/ is a patch on horizon that is part 1 of removing some code from searchlight-ui
15:22:58 <sjmc7> so if anyone’s got time and is able to help test it that would be good. there was a mailing list thread about it last week
15:23:15 <robcresswell> I've asked Richard to focus on getting that done for Pike
15:23:54 <robcresswell> So its pretty much top of our list really
15:24:10 <robcresswell> Ideally we can do it in a way that suits both codebases :)
15:24:28 <sjmc7> ok. my time is pretty limited and my expertise lacking but i’ll help as much as i can :)  i’ll try to get travis to help out with that one
15:24:36 <Kevin_Zheng_Hex> Added to my list
15:24:40 <lei-zh1> question, does it mean that horizon plans to use searchlight-ui code to replace nova server pannel
15:24:55 <robcresswell> yes
15:25:26 <lei-zh1> ok, that's cool
15:25:41 <sjmc7> even aside from that, that code should never really have been in sl-ui to start with
15:25:47 <robcresswell> there'll be some differences though, since we can't force searchlight on people yet. So it'll have to fall back to plain old server filtering.
15:25:48 <sjmc7> it was a function of timing and speed
15:25:59 <robcresswell> sjmc7: Yeah, we weren't getting things merged fast enough :(
15:26:25 <sjmc7> there wer emore important things at the time. it’s good it’s happening now
15:26:28 <robcresswell> Long term, I'd like to get to a stage where we can just tell people to install searchlight though
15:26:45 <sjmc7> if nova gets to a point where its experience is much better with SL that’ll be easier
15:27:19 <Kevin_Zheng_Hex> yeah
15:27:20 <sjmc7> i’d really like to see the kind of thing we demoed in vancouver sometime, the context-less nav bar search
15:28:59 <sjmc7> ok, so any help with that much appreciated. and thanks robcresswell for prioritising it
15:29:43 <robcresswell> I'm a bit less sold on the search-first idea, but yeah, definitely like the faceted search and speed of it.
15:29:54 <robcresswell> and you're welcome. Its long overdue on my part.
15:30:02 <sjmc7> yeah, me too :)  but i like the idea of being able to find stuff quickly
15:30:10 <sjmc7> the other review i wanted to mention was https://review.openstack.org/#/c/444068/ which Kevin_Zheng_Hex put up to make searchlight client a bit more user-friendly
15:30:57 <sjmc7> essentially extracting [‘hits’][‘_source’] from the ES results
15:31:12 <sjmc7> i’ve no objection to doing it if it helps consumption
15:31:42 <sjmc7> in many cases the summary and metadata attached to each result is not useful
15:31:50 <sjmc7> ok, that was all i had on the agenda
15:31:55 <sjmc7> #topic open discussion
15:32:11 <sjmc7> If anyone’s got anything else, you may have the floor, otherwise i’ll call it in a few minutes
15:32:30 <robcresswell> Is there any other content we should be looking at porting to Horizon?
15:32:51 <robcresswell> full panels/widgets etc
15:35:08 <robcresswell> I think that is a no :)
15:35:54 <lei-zh1> robcresswell: wanna know some details about how horizon consuming data from zaqar
15:36:27 <sjmc7> robcresswell: sorry, connection dropped. i think there was a a lot of work done for glance in SL-ui so maybe worth a look
15:37:11 <robcresswell> sjmc7: Interesting, we're actually due to remove the python glance implementation entirely in Horizon, since angular replaced it 2 cycles back I *think*
15:38:05 <sjmc7> splendid!
15:38:18 <robcresswell> I can take a look and see if there is content we should be using though
15:38:46 <robcresswell> lei-zh1: Best bet is to email the guys from the earlier thread. I can't remember the addresses from the top of my head - Calvin and Laurent
15:38:48 <sjmc7> i may be misinformed
15:40:29 <lei-zh1> robcresswell: yeah, I'll email them to get more detail, just forget their irc name : )
15:44:07 <sjmc7> ok, if there’s nothing else, let’s call it here
15:44:27 <sjmc7> have a good morning/afternoon/evening/night
15:44:52 <lei-zh1> thanks, bye
15:45:35 <sjmc7> #endmeeting