15:00:58 #startmeeting openstack search 15:01:00 Meeting started Thu Oct 8 15:00:58 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:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:04 The meeting name has been set to 'openstack_search' 15:01:11 o/ 15:01:15 o/ 15:01:16 o/ 15:01:25 nikhil, so you'll be making it to this summit? 15:01:38 TravT: :) 15:02:05 that's great 15:02:06 o/ 15:02:19 Though I wonder if they should have kept Austin in Nov and Tokyo in May 15:02:36 i have a text from sjmc7 that his internet connection died. 15:02:42 he'll join when he can. 15:02:56 you mean weather wise 15:02:58 nikhil: that's what I thought about Atlanta and Paris as well 15:03:09 true! :0 15:03:10 :) 15:03:18 lakshmiS: yes 15:03:41 64F is not bad in tokyo 15:03:42 texas in may is going to be awesomeeeeee!!!!!!!!!! 15:03:54 Japan in Nov should be great because of the red leaves festival :) 15:03:58 better than texas in July I suspect 15:04:04 hi ativelkov 15:04:04 higher 90s, 100s even 15:04:20 hi TravT, sorry for interrupting :) 15:04:28 no worries, just killing time... 15:04:34 we're missing a few of our usual suspects 15:04:45 ativelkov: long time 15:05:02 lakshmiS: :) 15:05:08 ativelkov: we would like to touch base with you on artifacts v3 and indexing with searchlight 15:05:11 heard you have some meeting coming up next week on app catalog 15:05:42 TravT: sure, we have the integration with the searchlite in our mitaka backlog :) 15:05:48 :) 15:06:00 o/ 15:06:10 ativelkov: we could probably see if appcatalog needs searching :) 15:06:10 lakshmiS: yup, I was asked by the Openstack:Now editorial team to bring some Glance majors :) 15:06:52 ativelkov: we have only a couple sessions at the summit for searchlight, but we could also have an informal one to talk about it and artifacts 15:07:02 TravT: sure 15:07:33 TravT: I have some Murano-related topics as well :) 15:07:52 +1 15:08:09 so, let me bring up the session planning etherpad in just a sec. 15:08:19 #link https://etherpad.openstack.org/p/search-team-meeting-agenda 15:08:28 #topic RC1 released 15:08:48 Great job everybody! 15:09:08 i put up release notes: https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Search_.28Searchlight.29 15:09:08 yeaaaaah! 15:09:20 \o/ 15:09:46 it is pretty awesome to accomplish what we have in the amount of time we've done it. 15:10:05 really a great group of people 15:10:38 if you see anything missing from the release notes, please update or let me know and I will 15:10:55 we also have a stable/liberty branch 15:10:59 woohoo!!! 15:11:09 TravT: does that mean RC1 is rc-final for liberty? 15:11:15 probably. 15:11:33 there have been a couple bug fixes in the last few days and i found another, but really nothing critical 15:12:18 gotcha 15:12:29 we did do one fix direct on stable/liberty 15:12:30 https://review.openstack.org/#/c/231726/ 15:12:34 I was a bit confused on the timeline around rel notes 15:12:34 hey 15:12:39 now clear 15:12:44 hey sjmc7 15:13:10 since we decided to lower the release number at the last minute to help set measured expectations 15:13:23 allowing a little more wiggle room in mitaka 15:13:47 so, i guess nikhil that means we will have a new tag on stable/liberty for final 15:14:01 TravT: I think that's critical 15:14:07 yes 15:14:16 possibly early next week? 15:14:24 we had one on master https://review.openstack.org/#/c/230086/ 15:14:36 which i don't think we should backport 15:14:57 hmm 15:15:05 we don't keep a conf.sample .. 15:15:12 so, I am okay either way 15:15:33 oops, I read it in a wrong tab 15:15:36 nvm 15:15:41 * TravT was feeling confused 15:15:58 there is one other bug that if we got figured out we might consider for backport. 15:16:01 https://bugs.launchpad.net/searchlight/+bug/1503080 15:16:01 Launchpad bug 1503080 in OpenStack Search (Searchlight) "Facet doc count reports more docs than actual" [Undecided,New] 15:17:08 we've got to figure out a fix for it first :) 15:17:22 yeah 15:17:48 We do need a deadline for setting rc2 / final. 15:18:17 would kind of like it to be tomorrow, but Mon / Tues at the latest 15:18:27 I am leaving for japan Wednesday evening. 15:18:37 going to vacation for a bit before the summit 15:18:41 wow, that's a long trip! 15:18:54 going around japan other than tokyo? 15:19:14 tokyo, hakone, nara, kyoto, and one other place that i can't remember 15:19:40 wow. i guess you will speak japanese by the end of it like you did with french 15:19:44 lol 15:19:55 well maybe let's say a deadline of finding any serious bugs by tommorrow evening? 15:19:58 and doing the final on monday? 15:20:05 that sounds reasonable. 15:20:09 you'll also be sick of fish by then 15:20:16 sjmc7: https://review.openstack.org/#/c/232200/1 15:20:24 itisha put that up yesterday 15:20:29 yeah, testing that now 15:20:56 we could consider it as well... although not a serious bug. 15:21:52 it's a nice to have for deployment 15:22:14 seems pretty low risk 15:22:44 need to add some tests on it 15:23:02 if we can figure out one for config 15:23:32 manual testing for stuff increasing... 15:23:40 yes, we need to decrease that 15:23:53 maybe functional tests are best for config testing 15:24:10 yeah thats possible 15:24:28 or mock loads of stuff 15:24:45 lakshmiS: would you be able to leave a comment with pointer for itisha on how to add that kind of test? 15:24:51 sure 15:24:57 thx 15:25:36 ok, so we'll check in first thing Monday (last thing for lakshmiS) and then will likely push the tag 15:25:56 if sjmc7 figures out a fix for the doc_count, let's take a look at it. 15:26:03 no pressure? 15:26:14 :) 15:26:24 well, i'm just debating whether or not to remove showing it in the horizon plugin i've got going. 15:26:30 it is nice. 15:27:08 so, we do have another urgent agenda item. 15:27:18 #topic Mitaka session planning 15:27:31 #link https://etherpad.openstack.org/p/searchlight-mitaka-summit 15:27:45 We have a deadline of October 15th to enter our sessions into sched 15:27:59 so, we need to get these figured out in the next day or two 15:28:27 take a look at that etherpad: https://etherpad.openstack.org/p/searchlight-mitaka-summit 15:28:27 ok. i have some ideas that i've not put down yet. i will do so today 15:28:48 let's talk through some here. 15:29:31 We have 1 fishbowl and 1 workroom slot. 15:29:49 i was hoping to have some info for performance and scalability, but looks like that won't happen until after the summit 15:30:06 TravT: do we have priorities setup for searchlight or is there a plan? 15:30:21 rosmaita: that is one of the ideas I put down for a workroom slot. 15:30:30 yes, i saw that 15:30:32 my biggest concern is getting away from hitting the service APIs for updates 15:30:35 I am tying to think from a 3rd person perspective if things look clear 15:31:24 since just one slot, i think thinking about how to make cross-region searching happen would be a really good use of time 15:31:40 nikhil: i have an initial list of ideas for that and started to go through blueprints. 15:31:41 sjmc7: +1 to getting away from hitting the service APIs 15:31:50 yeah, HP is also interested in cross-region 15:31:52 was also thinking the fishbowl session might help us to set next priorities 15:32:24 TravT: gotcha 15:32:27 the other one i had was trying to provide some standardization on how string indexing is done 15:32:50 From what I perceive, for a new interested vendor I see searchlight will be focusing on performance, cross region scoping (may be HA). What does it mean for indexing other services and for testing? 15:32:53 because tokenized vs not tokenized is not very apparent until it goes wrong 15:33:02 in terms of other services, swift would be a big one 15:33:11 but i don't think there's any mechanism to do it 15:33:38 one takeway would be to hear from other teams on what would they like to be searched or pain points they have today which can also drive our priorities 15:33:55 what do you mean by the service APIs? API for openstack services or some sort of other API for each service that's being called as service API -- may be admin API or something? 15:34:16 nikhil - anything we have to do over HTTP on updates 15:34:26 it will severely limit update bandwidth 15:34:31 sjmc7: ++ 15:34:45 designate's notifications contain all the info we get from the api 15:34:46 I was strongly pro for this approach since the beginning 15:34:47 which is ideal 15:35:13 unfortunately, many other services don't provide what we need. one option is to limit ourselves to the notifications and try to improve them, which is my preferred option 15:35:24 anyway, i will add these to the etherpad 15:35:28 I guess that means we will be giving other projects a stick when notifications aren't good enough 15:35:33 Yes, I think everybody is pro the approach, and it means getting changes into other services so that the notifications in other services are generated with the same thing you'd get with a specific version of the API 15:35:51 haha, yeah. typing at the same time sjmc7 :) 15:35:57 for example, one of the blueprints i registered with us is to handle nova microversions. 15:36:29 because right now, we aren't specifying a version, meaning we are getting the minimum nova version 15:37:23 FYI: nova-server-versioning-extensions 15:37:26 if we don't use the API, we'll get whatever the notification gives us :) 15:38:06 which lowers the value of searchlight if the notification doesn't provide enough information 15:38:16 yep. which is why it needs discussion 15:38:40 maybe that should be a primary goal of the fishbowl session, if we can get people from other project into it 15:39:36 ok. i'll add it there 15:39:57 we can never rely on just API or notification. i guess both will be needed based on the plugin 15:40:00 that would play into the second idea i have there, i think 15:40:35 nikhil: I copied my initial list of priorities onto this etherpad: https://etherpad.openstack.org/p/searchlight-mitaka-priorities-brainstorming 15:40:48 anybody can add to it... this would be just ideas for priority themese 15:40:53 and we could finalize... 15:41:09 or we could do like nova and put a document into our repo with mitaka priorities 15:41:15 and we can all gerritt review it 15:42:16 ok, i'll just be quiet here for a bit and let people edit on the etherpad, comment, etc. 15:42:47 https://etherpad.openstack.org/p/searchlight-mitaka-summit 15:44:47 TravT: ah thanks... I was just saying, not necessarily asking for a review :) BUt it's a bonus!!! 15:45:10 TravT: I have a topic for open discussion if we have time 15:45:29 sure, let's give this another minute, i still see some editing happening on the etherpad. 15:45:43 and I have to submit these up before our next meeting. 15:50:26 sjmc7: how about we combine idea 2 & 3 for the fishbowl 15:50:55 sure 15:51:09 just leave there as is 15:52:01 So, we also will be in a horizon fishbowl it looks like 15:52:09 with zaqar 15:52:09 though i think therewe need to decide how we (SL) approach it; do we go with our hybrid approach until notifications are sufficient alone for a service (which reduces update bandwidth) or work with what the notifications have (which reduces what we can index) 15:52:47 maybe it could be configurable. 15:52:55 graceful degradation 15:53:06 that's a good discussion to have 15:53:11 we won't solve in the next 7 minutes 15:53:35 not with that attitude 15:53:42 :D 15:53:58 when notifications are less we dont have to worry much on calling API 15:54:11 We can continue this in the room, but I do want to give nikhil some time 15:54:17 yep, go for it 15:54:20 THanks TravT 15:54:22 #topic open discussion 15:54:42 SO, I am looking for a topic that an intern can possibly work on for 2 months full time 15:54:51 THey can potentially pair on a BP too 15:54:58 new plugin :) 15:55:02 +1 15:55:11 Currently, I am getting them into Glance 15:55:35 a new plugin'd be the obvious one though i'd hope that wouldn't be a 2 month effort 15:55:36 but as a trend would be okay to include them here and do people have ideas for their learnings? 15:56:12 A plugin integration is actually a good way to learn about how openstack interactions work, i think. 15:56:19 tests are one area where a lot could be still added 15:56:22 I was asking for some initial feedback. The outreachy program is the that's most active within openstack, but we can also look into GSoC 15:56:34 I see 15:56:39 sjmc7: remember a lot of learning time too 15:56:57 is this itisha or somebody else? 15:56:59 i'll hold off cracking the whip 15:57:01 so, I will take it as people think that in general interns are good addition and they can work on searchlight comfortably :) 15:57:18 i think so. 15:57:21 yes 15:57:24 +1 15:57:28 TravT: I am just scouting atm. Will ask the coordinators if there is more interest 15:57:36 kragniz was like mr extraodirnaire intern 15:57:44 * TravT can't spell 15:57:45 lol 15:57:50 they allow more than one prj per application so, I can help them with Glance and SL 15:58:04 kragniz: hello there 15:58:12 he's lurking! 15:58:25 nikhil, i think it'd be great. 15:58:26 I can come back with more feedback in following weeks once there is some interest 15:58:28 I always lurk! 15:58:31 awesome! 15:58:42 kragniz: hello 15:58:48 unless my lecture ends, like it just has 15:58:56 * kragniz runs away 15:59:02 bye kragniz 15:59:07 thanks TravT. I am hoping to add a topic related to SL to the OPW wiki and will start with the tests stuff as lakshmiS mentioned. 15:59:45 Data + Search if one catchy topic so I expect good interest but time will tell. 15:59:49 ok, so let's circle back on final release tag and session planning in the room tomorrow / Monday. 15:59:51 o/ 16:00:02 hi 16:00:14 search is actually quite interesting. 16:00:25 :) 16:00:28 i guess we better end this meeting so we stop confusing others. 16:00:32 #endmeeting