15:01:18 <TravT> #startmeeting openstack search
15:01:19 <openstack> Meeting started Thu Sep 17 15:01:18 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:22 <openstack> The meeting name has been set to 'openstack_search'
15:01:44 <TravT> o/
15:01:49 <rosmaita> o/
15:01:51 <nikhil_k_> o/
15:02:00 <david-lyle> o/
15:02:21 <lakshmiS> o/
15:02:22 <sjmc7> hey
15:02:33 <TravT> has sigmavirus24 been around recently?
15:02:44 <rosmaita> was talking to him earlier
15:03:10 <TravT> here's the agend
15:03:12 <sigmavirus24> sorry
15:03:18 <TravT> #link https://etherpad.openstack.org/p/search-team-meeting-agenda
15:03:20 <sigmavirus24> I'm doing $work things on a vidyo call
15:03:24 <sigmavirus24> can't really focus on an IRC meeting
15:03:32 <TravT> sigmavirus24: yeah, that's hard.
15:03:44 <TravT> #topic release planning
15:04:33 <TravT> So, i just asked and was told to go ahead and move all the blueprints and bugs implemented to be targeted at liberty RC1
15:04:41 <TravT> just did that with blueprints.
15:04:43 <TravT> will do that with bugs
15:04:53 <TravT> and then will remove the liberty 1, 2, 3 milestones.
15:05:06 <sjmc7> when's the rc date?
15:05:39 <TravT> don't have concrete on that?  turns out the person i was pursuing for help yesterday was out sick.
15:06:14 <TravT> david-lyle: nikhil_k_ is tomorrow the date for horizon / glance RC1?
15:06:25 <david-lyle> TravT: next week
15:06:36 <TravT> ok, that's all i've know as well.
15:06:36 <david-lyle> FFE should be in by the end of the week
15:06:42 <nikhil_k_> TravT: early next week
15:06:44 <TravT> just didn't know an exact date
15:06:56 <david-lyle> project dependent
15:07:02 <david-lyle> when you're ready
15:07:19 <TravT> i think we're looking to be in good shape by end of next week on searchlight
15:07:42 <TravT> https://blueprints.launchpad.net/searchlight/liberty
15:08:09 <TravT> we'll defer a couple on the bottom
15:08:25 <TravT> but there is one i want to add
15:08:36 <TravT> https://blueprints.launchpad.net/searchlight/+spec/field-faceting
15:09:00 <TravT> steve's been working on it
15:09:09 <sjmc7> i have! it's pretty close to finished
15:09:09 <TravT> and i'm looking to consume it today with the horizon plugin
15:10:17 <TravT> the other BP with good progress is https://blueprints.launchpad.net/searchlight/+spec/plugin-config-options
15:10:36 <TravT> i'll look to provide a real review on that today if ekarlso has already addressed your concerns sjmc7
15:11:10 <sjmc7> i was just looking at that. one minor thing but that's very close
15:11:25 <TravT> ok, then i'll go ahead and look it over.
15:11:58 <TravT> sigmavirus24: this might be a good one for you to review as well if you can.
15:12:10 <TravT> https://review.openstack.org/#/c/223318/
15:12:54 <TravT> so otherwise, we have to address bugs
15:12:55 <TravT> https://bugs.launchpad.net/searchlight
15:13:24 <TravT> there are a few that i've found working on horizon plugin that affects searching.
15:13:42 <TravT> Need to normalize created_at / updated_at
15:13:48 <sjmc7> i've been working my way through them :)
15:13:51 <TravT> #link https://bugs.launchpad.net/searchlight/+bug/1496461
15:13:54 <openstack> Launchpad bug 1496461 in OpenStack Search (Searchlight) "Unable to search / sort based on create date or update date" [High,New]
15:14:10 <sjmc7> i've got some proper time to spend on this for a few days at least
15:14:24 <TravT> basically, some data (nova servers) use created / updated as field name and have a certain date format
15:14:49 <TravT> and others (designate) use created_at and updated_at with a slightly different date format
15:15:01 <TravT> the field name in particular is the problem for searching
15:15:11 <TravT> i can make queries that work around it
15:15:26 <TravT> but i don't think we should force users to do that.
15:15:36 <TravT> and i don't know how to deal with sorting
15:15:44 <sjmc7> sorting we can deal with
15:16:00 <sjmc7> understanding what kind of string search you're trying to do is trickier
15:16:38 <TravT> so, an idea is that we normalize that every doc has one or the other of the two and they can keep their original field.
15:16:58 <sjmc7> for created and updated yes, i think we can normalize those
15:17:08 <TravT> i'm not sure what is the better standard.  created_at  updated_at  vs created  / updated
15:17:09 <lakshmiS> so multiple formats?
15:17:24 <TravT> does anybody know if this is published anywhere?
15:17:32 <TravT> rosmaita: is this in the api working group?
15:17:35 <sjmc7> which is more popular?
15:18:04 <rosmaita> TravT: don't know
15:18:13 <sjmc7> i think updated_at is more commonly used
15:18:22 <sjmc7> nova, neutron at least
15:18:25 <rosmaita> yeah the _at is very popular
15:18:45 <rosmaita> TravT: did you mean the _at or the actual content of the filed?
15:18:57 <TravT> both i suppose
15:20:01 <sjmc7> the content should be iso 8601
15:20:14 <lakshmiS> i think we should have both fields in timeinmilliseconds additional to other format
15:20:16 <TravT> nova servers actually use created.  not the _at
15:20:57 <sjmc7> hmm... you sure? our plugin doesn't :)
15:21:02 <TravT> yep
15:21:36 <TravT> searching searchlight with created returns nova as well
15:22:15 <sjmc7> ok. maybe it's a coin toss then :)  i prefer _at
15:22:48 <TravT> well, i can go either way... just wanted to know if there was a recommended api standard for openstack
15:23:32 <TravT> we also need to better index the names in a standard way.
15:23:37 <TravT> https://bugs.launchpad.net/searchlight/+bug/1488236
15:23:38 <openstack> Launchpad bug 1488236 in OpenStack Search (Searchlight) "Sorting name fields does not behave as expected" [Undecided,New]
15:25:03 <TravT> anyway, these are affecting my horizon plugin work.
15:25:16 <sjmc7> that one we can fix with the elasticsearch suggested way
15:25:25 <TravT> yeah, i think so too.
15:25:47 <TravT> With the horizon plugin, it still lives locally.
15:25:49 <sjmc7> though only for explicitly mapped fields
15:26:04 <TravT> true
15:26:48 <TravT> i encountered a few bugs with upstream horizon widgets that are affecting my searchlight panel and have bugs submitted on them and hopefully somebody working to fix them.
15:27:38 <TravT> but i think on track for a very demoable panel by next week
15:27:49 <TravT> moving on...
15:27:53 <TravT> #topic functional tests
15:28:18 <TravT> looks like lakshmiS fixed the merge conflict
15:28:23 <sjmc7> i will test it again today
15:28:26 <lakshmiS> yeah i rebased it
15:28:34 <TravT> ok, i'll look then.
15:28:42 <sjmc7> the config options endre's been adding will help with it
15:29:04 <TravT> hmm, so should we get those in first?
15:29:58 <sjmc7> not necessarily. let's see how close each of them are
15:30:06 <TravT> ok.
15:30:27 <TravT> getting functional tests in feels like the best first step
15:30:40 <TravT> to prevent regressions.
15:30:41 <sjmc7> yeah
15:31:14 <lakshmiS> or else every change commited will require a fix in functional test patch
15:31:22 <lakshmiS> it should be other way around
15:31:36 <sjmc7> yeah, ok
15:31:54 <TravT> ok, are there any specific review and bugs needing discussion in IRC today?
15:31:59 <lakshmiS> https://review.openstack.org/#/c/221307/
15:32:20 <lakshmiS> nikhil_k: can you take a look at it
15:32:20 <TravT> nikhil_k_: ^
15:32:31 <TravT> what with all the failures?
15:32:35 <lakshmiS> the failures are not related to patch itself
15:32:48 <lakshmiS> every other patch is failing currently in zuul
15:33:14 <TravT> well, that's fun
15:33:37 <lakshmiS> maybe overload since it fails to install requirements
15:34:15 <lakshmiS> but if glance team can take a look at it and test it to see if its generating notifications that would be helpful go get reviews
15:34:27 <lakshmiS> s/go/to
15:34:29 <TravT> sigmavirus24: ^ glance patch
15:34:44 <sjmc7> ah, yeah
15:36:09 <TravT> I don't have any other agenda topics. anybody else?  If not, was thinking we could adjourn to the openstack-searchlight channel and just spend 30 minutes on reviews and interacting.
15:36:29 <TravT> http://tinyurl.com/searchlight-reviews
15:36:41 <TravT> maybe we could close out a couple of those
15:37:39 <sjmc7> no, i don't
15:37:44 <sjmc7> just reviews
15:37:54 <TravT> ok, i think that'd be the best use of time
15:38:02 <TravT> at this stage.
15:38:14 <TravT> #endmeeting