15:00:50 #startmeeting openstack search 15:00:51 Meeting started Thu Apr 21 15:00:50 2016 UTC and is due to finish in 60 minutes. The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:55 The meeting name has been set to 'openstack_search' 15:01:06 o/ 15:01:20 o/ 15:01:22 o/ 15:01:23 o/ 15:01:52 hiya everybody. 15:02:04 agenda for today 15:02:05 https://etherpad.openstack.org/p/search-team-meeting-agenda 15:02:21 #topic Backport 0.2.1 15:02:40 I think we have all but on patch backported 15:02:51 that we should target for 0.2.1 15:02:59 https://review.openstack.org/#/c/307504/ 15:03:22 it would be great if we could get through that one today 15:03:57 note that that one does change the data model a bit 15:04:27 yeah, it leaves me a little nervous as .1 patch 15:04:51 although i think it only changes the explicit model; under the hood, e-s will have been picking one option itself 15:06:06 without this, we still have ES 2.0 issues, though 15:06:19 yep. i’ll look at the other open bug today 15:06:52 i think we really should do it. 15:07:07 deployers lag behind pretty far at times in their upgrade cycle 15:07:47 yep. i’ve no problem backporting stuff given that because e-s is no longer in the ubuntu repos people will install it direct from elastic.co and so by default will get es 2 15:08:06 ok. 15:08:07 does the patch make es fields a little different from api data 15:08:45 yeah, it does, lei-zh 15:08:51 the short version of the problem is 15:08:57 for a field like ‘security_groups' 15:09:22 nova’s API defines it as a dict [{“name”: “default”}] 15:09:22 so I guess it's better to have it in docs 15:09:39 neutron ports as a flat string [“aaa-111-bbb”] 15:09:42 o/ 15:10:24 yeah, that’s a good idea. i don’t know in the general case how we decide what to do with fields like this 15:10:54 if we had multiple index (resource group support) it could be solved with separate indexes. 15:11:14 mmm, though i still don’t really like that as a solution 15:11:22 that is pretty heavy weight 15:11:36 really the problem is that two fields named the same are not actually comparable 15:12:37 “size” is another one; it means different things to cinder and glance 15:12:56 although size is just a storage thing, not a data structure thing 15:13:07 meaning, they are numeric in both cases 15:13:12 but does it make sense to just query on "size"? 15:13:14 it’s the same problem 15:13:29 i see it as a little different 15:13:34 right - a query size==1 makes sense in cinder, but not in glance 15:13:36 i mean a big image and a big volume are quite different 15:13:41 in size case, you have to know the context 15:13:47 in the same way that security_group==default makes sense in nova but not neutron 15:14:31 seems like we need our own qualifier in field names 15:15:22 yeah, i dunno what the answer is. i think for now, we need to make it work with es2 but longer term decide what we intend when field names are the same 15:15:27 in size case, a UI displaying it doesn't really need to know the structural difference between API and SL index 15:15:38 in sec group case, this now introduces that issue 15:16:02 TravT: yep. the alternative is renaming the field in one or both plugins, or changing the structure for Ports 15:16:17 i picked one but i’m fine with any of the 3 options 15:17:59 the only other thing i can think of doing to maintain API compatibility is to massage the data back into API format on the way out 15:18:48 yeah, that’s an option. 15:18:58 i guess i could add that to this patch for now 15:19:06 it would keep backward compatibility for mitaka (stable) 15:19:13 ok, that’s reasonable 15:19:31 i still want to discuss this more next week though 15:19:38 yeah, this is a good topic 15:20:13 ok, i vote for doing that for now to maintain rules of backwards compatibility. 15:20:27 with newton (should be 1.0), we can make a change if needed 15:20:47 ok. sorry to derail things a bit 15:20:51 sounds reasonable 15:21:16 any other bugs to discuss for 0.2.1? 15:21:44 the other one tagged for es-2 15:21:52 https://bugs.launchpad.net/searchlight/+bugs?field.tag=elasticsearch-2 15:21:55 umm.. the weird java error one reported as a ui problem 15:22:08 1570213 15:22:12 i will try to take a look today 15:22:36 ok 15:22:50 look like lei-zh picked up the other one 15:23:37 yes, I'll submit a patch tomorrow 15:23:44 thanks lei-zh 15:24:01 only other thing is to write a release note for the changes. 15:24:15 i can do that once they land. 15:24:39 let's jump to summit discussion 15:24:51 #topic newton summit 15:25:31 #link https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-28&summit_types=2&tags=1728 15:25:40 searchlight is tagged in all those sessions 15:25:40 I have a bad news : ( 15:25:56 lei-zh: oh? 15:26:01 just heard yuntong won't go to summit, I couldn't find others to talk in the session 15:26:29 :( 15:26:30 :( i think we understand what you’re trying to do pretty well with the publishing stuff 15:26:37 sorry for that, but things changed so quickly 15:26:49 it happens, we understand 15:27:00 so, that affects this agenda 15:27:00 https://www.openstack.org/summit/austin-2016/summit-schedule/events/9381 15:27:33 we still can talk priorities 15:27:42 we also could talk about data mapping in that discussion 15:27:49 and normalizing across services 15:28:17 yep 15:29:33 ok, i'll make that change... i'll leave pipeline as a topic 3, although I don't think we'll get to it... 15:30:32 okay, 15:30:48 this video was sent out 15:31:04 to help anybody attending the summit to understand how sessions should be run 15:31:06 Video for session etiquette: https://youtu.be/M4cDyM2s2bc 15:31:11 watch it later 15:31:14 it is only about 6 minutes 15:31:39 That's all I have for today. 15:31:46 anyother summit discussion needed? 15:32:26 nope 15:32:49 okay. don't forget to register for the summit party 15:32:57 hopefully it isn't too late 15:33:05 #topic open discussion 15:33:18 perhaps this has been answered, but any other topics for today? 15:33:45 anyone have any allergies that could affect my choice of pie to bring? 15:34:05 i have bad news on the pie front 15:34:19 * TravT awaits in stunned silence 15:34:20 i can’t eat dairy for a while, which rules out about 50% of my diet 15:34:47 what exactly counts as "dairy"? 15:34:52 luckily beer shouldn't be on that list 15:35:01 TravT: ++ 15:35:02 things that come out of cows, goats or sheep 15:35:10 so eggs are ok? 15:35:18 that’s my other 50%, so yes 15:36:00 well pie crust is mostly just flour and shortening 15:36:16 i will just make sure no milk-based filling 15:36:26 woo! 15:36:32 i wasn't going to bring ice cream, anyway 15:36:46 so your food pyramid which looked roughly like this shouldn't be too affected: http://www.gonis.net/kara/pictures/FDApyramid2.jpg 15:37:29 :) 15:38:03 also, we can all try to communicate via email next week to perhaps meetup for lunch or dinner or Brian's suggestion 15:38:22 so turns out that tuesday pm is the super-big party 15:38:34 but i am still planning to leave it early to go to Antone's 15:38:35 oh 15:38:53 yeah, kind of sucks, i got my days mixed up 15:39:02 we’ll find a day 15:39:40 yeah, let's just try to connect early next week. 15:39:53 all right, well, let's cut out early today 15:40:01 thanks everybody! 15:40:08 gonna go find some eggs! 15:40:13 thanks, see some of you next week 15:40:17 bye! 15:40:20 #endmeeting