15:01:02 <TravT> #startmeeting openstack search
15:01:03 <openstack> Meeting started Thu Apr  7 15:01:02 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:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:06 <openstack> The meeting name has been set to 'openstack_search'
15:01:53 <TravT> o/
15:02:00 <rosmaita> o/
15:02:01 <yingjun> o/
15:02:09 <RickA-HP> o/
15:03:41 <TravT> okay
15:03:48 <sjmc7> hey, sorry, connection issue
15:03:51 <TravT> so. https://etherpad.openstack.org/p/search-team-meeting-agenda
15:04:08 <TravT> #topic Mitaka release
15:04:19 <TravT> Mitaka is officially released
15:04:28 <TravT> just chatted with thierry about it
15:04:31 <TravT> no more RCs
15:04:36 <sjmc7> woo!
15:04:42 <TravT> \o/
15:04:49 <TravT> Great job everybody
15:04:50 <TravT> !
15:05:13 <TravT> which brings us to:
15:05:22 <TravT> #topic     Candidates for backports (potential 0.2.1)
15:05:34 <TravT> we don't have any more rcs
15:05:45 <TravT> but we can request a point release at any time
15:05:48 <TravT> so 0.2.1
15:06:01 <TravT> and sjmc7 found a couple candidates there
15:06:14 <sjmc7> found/caused
15:06:34 <TravT> Fix for updating nova server on volume attach/detach (sjmc7): https://review.openstack.org/#/c/301943/
15:06:39 <TravT> that's merged
15:06:48 <sjmc7> i already put up a backport review for that one
15:06:57 <TravT> link?
15:07:09 <sjmc7> https://review.openstack.org/302814
15:07:12 <TravT> is anybody opposed to me approving that for stable/mitaka?
15:08:07 <lei-zh1> nope
15:08:14 <rosmaita> seems kind of important
15:08:47 <TravT> okay, then i'm going to do that.
15:09:22 <nikhil> o/
15:09:29 <TravT> sjmc7 want to talk about:     Discussion on https://bugs.launchpad.net/searchlight/+bug/1565028; any fix is going to be a bit unpleasant, not sure about the payoff
15:09:30 <openstack> Launchpad bug 1565028 in OpenStack Search (Searchlight) "Neutron port detach isn't detected by nova event handler" [Critical,New]
15:09:36 <sjmc7> this is a similar issue; detecting port attach/detach events for servers
15:10:09 <sjmc7> the solution’s much less straightforward, but i will have another think about it
15:10:45 <sjmc7> i think this is a much less common occurrence (it only affects explicitly attaching a neutron port to an instance, not automatic port creation)
15:11:07 <rosmaita> i guess this is compounded by the nova-networks vs neutron situation (which i know nothing about other than that it used to be a "thing")
15:11:11 <sjmc7> and we do currently deal with port attach, just not detach, which is troublesome
15:11:22 <sjmc7> yeah, nova networks is another kettle of fish
15:11:35 <sjmc7> nova abstracts some parts of that but not all
15:11:43 <sjmc7> this is one of them
15:11:50 <sjmc7> i actually think it’s kind of a bug on nova’s side in a way
15:11:57 <yingjun> I added nova to the bug, not sure if what’s the nova guys think
15:12:04 <sjmc7> it should send interface-attach/detach events
15:12:18 <rosmaita> i agree
15:12:27 <rosmaita> (though that doesn't help much)
15:12:45 <sjmc7> right. so i don’t know if it’s worth a hacky fix for this
15:13:00 <rosmaita> how bad would it be to have not port info indexed?
15:13:05 <rosmaita> *no
15:13:18 <sjmc7> that’s the other option. it’s nice being able to get servers by IP address
15:13:26 <rosmaita> just wondering if inaccurate data is worse than no data at all
15:13:29 <sjmc7> yeah
15:13:36 <rosmaita> no, you answered the question
15:13:44 <rosmaita> people like to get servers by ip address
15:13:46 <sjmc7> the denormalized fields the nova API gives us cause trouble in this respect, but they are quite useful
15:14:08 <sjmc7> i would like ot persuade nova to have the server notifications match the API output but that seems like a long shot
15:14:23 <TravT> i just wonder how often this happens in the real world?
15:14:50 <rosmaita> well, probably a lot if you have your own subnet
15:14:52 <sjmc7> floating IPs i suspect would be one example
15:14:57 <sjmc7> and yeah, that too
15:15:02 <rosmaita> they are kind of small, may have to add/subtract servers
15:15:17 <sjmc7> maybe a hacky solution is better than none
15:15:29 <TravT> sjmc7, the other events will cause us to update the port details as well, correct?
15:15:36 <TravT> eg. restart
15:15:40 <sjmc7> yes
15:15:42 <rosmaita> TravT: that's a good point
15:15:58 <sjmc7> yeah, anything where we have to reindex servers for another reason will pick up any changes
15:16:07 <rosmaita> maybe we should just leave the bug open until nova fixes it
15:16:15 <sjmc7> so yeah, all these reasons leave me on the fence
15:16:24 <TravT> what is your hacky fix?
15:16:35 <sjmc7> the only solution i’ve got is not very reliable - it’d mean searching for instances matching the port id
15:17:08 <sjmc7> and we’ve stayed away from searching the e-s data during updates because of potential races with updating the search index
15:17:31 <sjmc7> it’d work most of the time
15:18:33 <sjmc7> i guess i can put up a fix and see what it looks like?
15:19:35 <sjmc7> we do need, again, to come up with a general answer for when notifications don’t match API output; we keep running into these kinds of problems
15:19:51 <TravT> I'm probably suffering from amnesia, but i feel like i missed a part of your proposal. are you saying on a *neutron* port event, we'd do this search and update instances appropriately?
15:19:57 <sjmc7> yep
15:21:33 <TravT> okay here's my .02
15:21:57 <rosmaita> so the neutron info is up to date, but the nova is not?
15:22:02 <sjmc7> yep
15:22:24 <TravT> thanks yingjun for adding nova... i think it would be good if sjmc7 cleaned up the description a bit for nova patch team ease of consumption
15:22:54 <TravT> i think the idea you have sjmc7 is interesting, but i'm slightly hesitant to immediately backport to stable
15:23:05 <TravT> so maybe could go on master first for a bit?
15:23:08 <sjmc7> ok
15:23:38 <sjmc7> looking at the code there is actually a pretty serious bug we may have to backport :(  i’ll file it separately
15:23:45 <rosmaita> i don't like this proposal, because the ip search is rough on the nova api
15:24:02 <TravT> rosmaita?
15:24:06 <sjmc7> rosmaita: i wouldn’t search nova’s api, just the SL data
15:24:27 <rosmaita> ok, i misunderstood
15:24:39 <sjmc7> yeah, that’d be a no-no
15:25:12 <lakshmiS_> here's a crazy idea. Make just port as parent of nova and let neutron port updates go there.
15:25:29 <sjmc7> ?
15:25:42 <sjmc7> ports can belong to routers or subnets
15:25:48 <sjmc7> or rather, be attached to
15:26:06 <TravT> hmm... that's be network --> port --> server
15:26:17 <sjmc7> wait, wait
15:26:29 <sjmc7> servers are not logically descendents of ports
15:26:31 <TravT> that seems a bit wrong
15:27:20 <lakshmiS_> hmm let me think through if there is a way to normalize for updates
15:27:39 <sjmc7> the problem is that a port detach contains no information indicating what it was attached from
15:27:49 <sjmc7> err, detached from
15:27:51 <TravT> hmm
15:27:59 <TravT> that seems like it could be a bug / bp on neutron
15:28:10 <sjmc7> spread the wealth :)
15:28:11 <rosmaita> TravT: +1
15:28:38 <sjmc7> in the meantime, what’s the consensus
15:29:18 <rosmaita> i think do nothing, figure eventully server updates will make the data consistent
15:29:25 <rosmaita> leave the bug open
15:29:36 <rosmaita> see if more people complain
15:29:56 <sjmc7> ok. we can maybe bring it to neutron’s attention too
15:30:03 <rosmaita> because i think TravT has a good point that we may not see this very much
15:30:23 <rosmaita> sjmc7: +!
15:30:29 <rosmaita> +1, even
15:30:42 <TravT> is +! the same as a -1?
15:30:55 <TravT> (plus not)
15:31:01 <TravT> ;)
15:31:19 <sjmc7> *tumbleweed*
15:31:24 <TravT> tough crowd
15:31:36 <TravT> okey
15:31:39 <TravT> dokey
15:31:47 <TravT> so, back to 0.2.1
15:32:06 <TravT> i think the volume attach bug alone is worth a point release
15:32:39 <david-lyle> TravT: point release of which?
15:32:40 <sjmc7> ok. i’m filing another related server notification bug that i’ll fix today, so can we hold off until then?
15:32:42 <TravT> is there anything else critical that could be solved in a few days that also should go in point release
15:32:49 <TravT> searchlight
15:32:57 <TravT> it is too late for rc3 (mitaka out)
15:33:01 <david-lyle> we're not release independent
15:33:06 <TravT> but thierry said we can do a 0.2.1 at any time
15:33:14 <david-lyle> oh O_o
15:33:40 <david-lyle> I thought that was owned by stable
15:33:47 <david-lyle> probably shifted again
15:33:52 <david-lyle> ttx would know
15:33:59 <TravT> we own stable for searchlight, but that's what i was told this morning
15:34:09 <david-lyle> interesting
15:35:03 <david-lyle> go back to ignoring me
15:35:05 <david-lyle> :)
15:35:35 <TravT> i think for things that aren't patch releases (e.g. 0.2.x) it would be diff
15:36:18 * david-lyle is tempted to start with "back in my day"
15:36:25 <TravT> lol
15:36:47 <TravT> so, anybody against me putting up a point release once https://review.openstack.org/#/c/302814/ lands?
15:36:54 <TravT> or is there anything else to consider?
15:37:01 <sjmc7> yes :)
15:37:19 <sjmc7> i’ve got another similar change i’d like to get in
15:37:25 <TravT> okay, do share
15:37:32 <sjmc7> i’m filing the bug
15:37:37 <sjmc7> related to the port stuff
15:37:38 <TravT> i really need some time for summit planning as well
15:37:54 <sjmc7> go for it
15:38:06 <TravT> #topic summit planning
15:38:21 <TravT> i need to get things uploaded into eventbrite asap
15:38:32 <TravT> #link https://etherpad.openstack.org/p/searchlight-newton-summit
15:39:21 <TravT> first thing to notice is that we will have some discussion on search in a horizon session. and looks like a good chance there will be a swift session
15:39:44 <TravT> i put links for that at the top
15:39:49 <TravT> next, we have 3 sessions
15:39:54 <TravT> 1 fishbowl
15:39:56 <TravT> 2 working
15:40:15 <TravT> currently 5 ideas listed
15:40:56 <TravT> i'll pause for a minute to let people look at what is there now.
15:41:02 <sjmc7> i’ve got one i haven’t put on there about weaning ourselves off API calls
15:41:06 <TravT> and to add ideas
15:41:36 <TravT> sjmc7: d'oh!  can't believe i don't have that one on after rambling about maybe doing a fishbowl on it
15:41:45 <sjmc7> adding it now
15:42:10 <TravT> i think that would be a good fishbowl and we could also tag neutron, nova, cinder on it.
15:42:26 <TravT> ironic as well
15:42:46 <sjmc7> maybe, but i also mean from our perspective, what our general approach should be
15:46:56 <TravT> lei-zh1: are you there?
15:47:50 <TravT> The pipeline topic surely would benefit from some face to face time, but need to know if anybody from your team will be there to talk about it
15:48:17 <lei-zh1> yes, yuntong will be there
15:48:42 <TravT> will malini be there as well?
15:48:43 <lei-zh1> although he carries some other tasks, but he can have a discussion on that
15:48:45 <TravT> does she care about this?
15:49:45 <lei-zh1> I'll confirm with her about it
15:49:57 <TravT> ok.
15:49:58 <lei-zh1> not sure about her schedule
15:50:44 <TravT> so, i think the cross project aspect of notifications makes that one the most likely candidate for fishbowl out of what we have right now
15:50:57 <TravT> that one meaning the notification topic
15:51:05 <lei-zh1> shall we submit a spec of pipeline, it will be helpful for the discussion
15:51:39 <TravT> so different than the one you already have?
15:52:15 <lei-zh1> I think it's more with pipeline architecture
15:52:37 <lei-zh1> we didn't define that too much on the zaqar plugin
15:52:41 <TravT> ok, if you think it would be helpful to all of us, then please do
15:52:54 <lei-zh1> ok
15:53:40 <TravT> yingjun: any topics you propose or would like to vote for? also do you know if you will be able to come or not?
15:54:16 <TravT> i guess we still need to add david-lyle 's beer bash as an idea
15:54:30 <TravT> ;)
15:54:58 <yingjun> i’ll come to the summit
15:55:04 <TravT> \o/
15:55:13 <TravT> that's great!
15:56:20 <TravT> okay, well please add votes / ideas to the etherpad
15:56:42 <TravT> i'll arrange and upload to eventbrite on monday-ish
15:57:01 <TravT> #topic open discussion
15:57:33 <TravT> does anybody have any other topics?
15:57:44 <TravT> sjmc7, have that bug ready for us to discuss?
15:58:09 <sjmc7> https://bugs.launchpad.net/searchlight/+bug/1567525
15:58:10 <openstack> Launchpad bug 1567525 in OpenStack Search (Searchlight) "port.create.end events are handled incorrectly by nova" [Critical,New]
15:58:31 <sjmc7> in short - novca currently listens to port.create.end for reasons only i could have answered, 7 months ago
15:59:02 <sjmc7> which a) doesn’t make much sense and b) doesn’t handle them correctly. in light of the conversation we had i’m gonna remove the handler for backporting
15:59:25 <sjmc7> and then see if we can handle port updates consistently for Newton until we can get the notifications fixed
15:59:47 <TravT> okay, i'll look at it in detail.
16:00:06 <TravT> time is up for us
16:00:10 <TravT> thanks everybody
16:00:16 <TravT> #endmeeting