15:00:58 #startmeeting openstack search 15:00:59 Meeting started Thu Jul 7 15:00:58 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:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:02 The meeting name has been set to 'openstack_search' 15:01:11 o/ 15:01:19 o/ 15:01:24 o/ 15:01:33 (am close to coffee emergency, though) 15:01:34 o/ 15:01:38 o/ 15:01:49 o/ 15:02:09 rosmaita: that phrase has become too graphic in my mind 15:02:28 lol 15:02:46 okay. agenda here: https://etherpad.openstack.org/p/search-team-meeting-agenda 15:02:47 o/ 15:03:08 #topic mid cycle hangout 15:03:19 sjmc7: i'm not sure i'm built for all these back-to-back meetings 15:03:26 http://doodle.com/poll/stxrx9wxq38itnk3ew9ym4rr/admin#table 15:03:37 isn 15:03:42 t hat all the management entails? 15:04:28 so, based on the doodle poll 15:05:05 19th or 20th look best. 15:05:22 i'd like to propose http://everytimezone.com/#2016-7-20,1560,cn3 15:05:32 unless there are any objections 15:05:45 that is one of two slots that has green for all voting participants 15:06:19 That sounds good to me. 15:06:47 is that july 21 in the usa? 15:06:54 (not sure i'm reading correctly) 15:06:55 oops 15:07:09 accidentally move the slider before copy pasting 15:07:15 http://everytimezone.com/#2016-7-20,120,cn3 15:07:32 ^ that should align to the doodle poll time 15:07:42 ok, that's better 15:07:49 I'm fine with the time 15:07:57 I was going off the doodle poll time :) 15:08:15 TravT_: what's the length of the meeting? 15:08:24 2 hours okay? 15:08:29 +1 15:09:14 ok for me 15:09:29 +1 15:09:44 https://etherpad.openstack.org/p/searchlight-newton-hangout 15:10:07 Proposed agenda there 15:10:13 add items 15:10:32 I'll put connection information there as well 15:11:11 #info searchlight newton hangout will be http://everytimezone.com/#2016-7-20,120,cn3 15:11:34 up next 15:11:38 #topic Mascot 15:12:02 i got an email 15:12:17 from the foundation saying that each project team can select a mascot 15:12:31 hahaha 15:12:40 the big fluffy kind? 15:12:41 animal/vegetable/mineral? 15:13:03 The idea is to create a family of logos for OpenStack projects that are unique, yet immediately identifiable as part of OpenStack. We’ll be using these logos to promote your project on the OpenStack website, at the Summit and in marketing materials. We’re asking project teams to choose a mascot to represent as their logo. Your team can select your own mascot, and then we’ll have an illustrator create the 15:13:03 logo for you (and we also plan to print some special collateral such as stickers for your team in Barcelona). 15:13:17 Your mascot can be anything from the natural world—an animal, fish, plant, or natural feature such as a mountain or waterfall. We ask that you don’t choose a mascot that another company or project in the ecosystem is already using. To facilitate this, we suggest your team choose and prioritize a few mascot candidates by July 27. 15:13:31 I asked: A question, since our project name is already an “object” (a searchlight), would a searchlight or a lighthouse like logo be a viable mascot? 15:13:40 +1 15:13:48 And the response was: - there are quite a few OpenStack project names that suggest specific human-made objects, and I imagine we’ll get a lot of questions on them (or requests for exceptions). I’d suggest that your team think of something from the natural world that might offer searchlight-type capabilities (I’m thinking of bioluminescent creatures, or creatures that are particularly good at finding things 15:13:48 , working in the dark, or using unique senses like a beluga). Another option might be to select a natural feature such as a land peninsula and strongly recommend to the illustrator that a lighthouse would work well on it! 15:14:08 -1 beluga 15:14:11 how aobut one of those deep-water fish that has its own flashlight? 15:14:28 the one that almost ate Nemo? 15:14:31 hahaha 15:14:47 who couldn't love this: http://www.fiboni.com/wp-content/images/anglerfish.jpg?a0f395 15:14:54 angler fish! 15:15:00 yeah, the illustrator will love drawing that! 15:15:06 we would need a disney-ized version 15:15:08 “more teeth please" 15:15:12 hahaha 15:15:31 we would have the coolest t-shirts, though 15:15:42 :) 15:15:53 "Searchlight Anglers" 15:15:56 and one day the best o’reilly book cover! 15:16:01 :) 15:16:16 rosmaita love that one 15:16:21 :) 15:17:29 other options could be something like a blood hound 15:17:44 or maybe a prison with inmates escaping and a searchlight on them 15:17:48 or a bat 15:18:13 i like the prison idea 15:18:13 https://s-media-cache-ak0.pinimg.com/originals/c0/ed/84/c0ed847982f56a3bc7a6dba7ee638383.jpg 15:18:41 i think that one's taken 15:19:07 bats use echolocation, although that's just polling, no notifications 15:19:54 google already has some sweet drawings for prisoners escaping 15:19:56 https://cdn.drawception.com/images/panels/2012/4-3/Eq8xPRqyZK-8.png 15:20:08 there's always http://www.firefly.org/images/pictures/firefly-pics2.jpg 15:20:10 (is kidding) 15:20:36 TravT_: that looks as good as the current glance logo 15:21:00 well, anyway, we'll have until july 27th 15:21:13 if you think of any ideas, please bring them to the next meeting or two 15:21:24 next topic 15:21:35 #topic cross region 15:21:39 sjmc7 ^ 15:21:52 hello! 15:22:17 at the summit we discussed cross-region search for a while in that sauna room 15:22:39 and decided not to do anything too complicated but add region_name to resource mappings to support client-side cross region search 15:22:55 it occurred as i was about to add it that it’s entirely redundant since the client already knows which region it’s searching 15:23:08 so i’m now inclined to not do anything until someone says they need it 15:24:08 otherwise it’s just another thing we have to support without a really clear use case. the one instance it would be useful is if a deployer set up elasticsearch to handle the aggregation, but i don’t see that happening in the near future while it’s still a very new project 15:24:44 it’s not technically hard to add region name, i just am reluctant to add things without a clear need 15:25:01 thoughts? 15:25:16 sjmc7, how do you query by region? 15:25:25 well, right now SL is deployed into a region 15:25:26 if the data is not region specific? 15:25:28 same as nova, or glance 15:25:38 so you already know the region you’re querying 15:25:48 right 15:25:50 ok 15:25:55 for reference, here is the spec that led to the discussion at the summit 15:25:56 http://specs.openstack.org/openstack/searchlight-specs/specs/newton/cross-region-search.html 15:26:34 Proposed change section and alternatives contain info 15:26:43 like i say, it’s not hard to add, but it’s information the client already has 15:27:18 are there configurations where you would combine region data into one ES? 15:27:36 there might be, but i would imagine that’s a way down the road 15:27:56 hmm, that is a good question though 15:28:02 well glance is often shared across regions 15:28:15 but that's a different problem 15:28:26 ok. then that might be a good use case 15:28:36 if for some reason, somebody setup multiple regions on the same control plane 15:28:54 with shared ES 15:28:59 so in that config you’d have keystone & glance shared but nova, neutron split by region? 15:29:41 yes 15:30:14 trying to remember if region value is populated in the service catalog in that case 15:30:35 yeah, it may be like keystone where it has multiple entries in the catalog but the same URL 15:31:18 wait, that sounds wrong. ok, i’ll look into whether that’d be doable as things are at the moment 15:31:35 this may be a rat-hole, but i think adding the region would be potentially useful long term 15:31:40 but we may not need to rush 15:31:54 ok. well, it’s not hard to do, so maybe make it optional 15:32:11 default it to true in devstack and CI so it’s tested 15:32:36 allows for smarter use of the client long term 15:32:54 not having to artificially add region value after the fact 15:33:17 yeah. ok, sold to the handsome chap at the back 15:33:24 \o/ 15:34:00 allright, 15:34:13 guess that's been covered 15:34:36 #topic Reviews needing attention (1 more +2) 15:34:36 * david-lyle is here to "speed" things up 15:34:57 There are several reviews out there which have a +2 15:35:13 so at least there has been some rigor applied 15:35:28 if we could get some more core eyes on them, it would be nice 15:35:37 First one: EASY! Index settings https://review.openstack.org/333958 15:35:56 that one really is fairly easy to try out. 15:37:15 The next one is definitely a little more intimidating, but it is high priority and has been banged on quite a bit. 15:37:21 High Priority! Reduce Nova API Calls https://review.openstack.org/317100 15:38:35 There are three more related ones, the aren't too hard, but are lower priority 15:38:46 https://review.openstack.org/333018 15:38:46 https://review.openstack.org/308582 15:38:46 https://review.openstack.org/333034 15:38:58 Okay, that's all for the call for reviews today 15:39:25 in f2f meetings today but can look when flying home tonight 15:39:35 cool, thanks, david-lyle 15:39:40 are you in hillsboro? 15:39:49 you’re such a jetsetter 15:39:52 yeah 15:40:12 #topic open discussion 15:40:16 that's all for the agenda 15:40:21 anything else on anybody's mind? 15:40:35 sjmc7, only the most glamorous destinations 15:41:09 i didn’t have anything, TravT_ 15:41:10 i guess I should mention that i'll be at the horizon mid cycle next week. 15:42:02 if there aren't any topics on the agenda by Wednesday next week, i can just cancel the meeting 15:42:29 if you think of any mascot ideas 15:42:32 add them here 15:42:32 https://etherpad.openstack.org/p/searchlight-mascot_suggesstions 15:42:44 ok. 15:42:47 thanks everybody 15:42:55 #endmeeting