15:00:57 #startmeeting openstack search 15:00:58 Meeting started Thu Jun 18 15:00:57 2015 UTC and is due to finish in 60 minutes. The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:02 The meeting name has been set to 'openstack_search' 15:01:08 #topic agenda and roll call 15:01:11 mornin 15:01:14 o/ 15:01:16 o/ 15:01:18 o/ 15:01:25 g'morning/afternoon/evening 15:01:40 o/ 15:01:50 #link https://etherpad.openstack.org/p/search-team-meeting-agenda 15:02:34 so the repo is set up in gerrit now 15:02:42 Thanks guys. I wanted to discuss the possibility of mid-cycle meeting co-located with Glance. 15:02:51 thats a great way to start!! 15:02:59 we still need to add people to the group so we can approve patches 15:03:02 #topic We've operational gerrit workflow 15:03:17 kragniz: who's the admin? 15:03:24 openstack-ci? 15:03:25 nikhil_k: no one yet 15:03:35 huh? 15:03:37 #link https://review.openstack.org/#/admin/groups/964,members 15:03:48 doh 15:03:57 someone must have to be there to create it? 15:04:14 apparently not 15:04:15 we need to talk to -infra to get someone added, then they add other people 15:04:24 kragniz: you wanna own it? 15:04:29 sure 15:04:40 #action kragniz : talk to -infra to get someone added to 15:04:47 there was a list of potential cores somewhere in the post-summit conversation 15:04:47 #info Group searchlight-core 15:05:02 you should make the co-PTLs admins 15:05:14 as well 15:05:22 yup 15:05:31 there's also searchlight-release 15:05:54 nevermind, mixing lp and gerit 15:06:08 usually, all drivers are admins 15:06:18 here cores==drivers 15:06:27 right, just got my tools crossed 15:06:41 after we have that done, we need to fix the gate, which is currenly failing 15:06:52 agreed 15:07:19 unless anyone desperately wants to, i can take a look at that 15:07:20 sjmc7: do you want to look at that? 15:07:22 heh 15:07:39 i'm hoping it's something simple in our tox file 15:07:42 #action sjmc7 , kragniz to look at the failing gate 15:07:52 sjmc7: I think it's the same failure I was seeing on that last patch of yours on github 15:08:18 looked like it was much earlier in the process when i took a quick look yesterday but i'll dive in later 15:08:46 this is the failure 15:08:48 #link http://logs.openstack.org/32/192532/1/check/gate-searchlight-python27/1020cb4/testr_results.html.gz 15:09:13 ok. yeah, will take a look today 15:09:17 looks like mismatch , members is missing in actual 15:09:43 pep8 was failing too i noticed 15:10:00 ah, on the newer one 15:10:10 yep. i'll dig around later today 15:10:27 Thanks 15:10:34 #topic BP walkthrough 15:10:47 #info BPs registered: https://blueprints.launchpad.net/searchlight 15:10:52 Thanks everyone for doing that. 15:11:07 that was the easy part :) 15:11:15 #action: nikhil_k to add performance test related BP 15:11:24 I guess we can mark this BP as implemented now? https://blueprints.launchpad.net/searchlight/+spec/separate-from-glance 15:11:26 Any other missing? 15:11:48 i think those were all the ones we discussed 15:12:09 nice! 15:12:20 lakshmiS: yup, I think so 15:12:22 lakshmiS: makes sense. may be the init gerrit link can be posted there? 15:12:27 kragniz: ^ 15:12:41 sure! 15:13:07 #link https://review.openstack.org/#/admin/projects/openstack/searchlight 15:13:24 oops, there not here 15:14:26 done and maked as implemented 15:15:08 kragniz: thx 15:15:41 yay! 15:15:58 some more details added 15:16:11 * sigmavirus24 got distracted, sorry 15:16:23 sigmavirus24: you missed all the fun! 15:17:15 sigmavirus24: check your inbox for all the blueprints assigned to you ;) 15:17:20 * sigmavirus24 read the scrollback 15:17:22 lakshmiS: lol 15:17:23 :) 15:17:29 lakshmiS: https://blueprints.launchpad.net/searchlight shows none 15:17:32 so I'm winning 15:17:45 wait for it ... 15:17:45 all unassigned go to sigmavirus24 :P 15:18:14 * sigmavirus24 is disappointed in launchpad. No way to subscribe to new blueprints it seems 15:18:19 kragniz: I guess we can create one in glance for #link https://blueprints.launchpad.net/searchlight/+spec/remove-from-glance 15:18:33 Should we mark it as started now? 15:19:01 has any one volunteered to do it? 15:19:12 can you mark a BP as being for more than one project 15:19:15 I see kragniz assigned 15:19:19 sjmc7: I sort of did 15:19:27 not very attached to it, though 15:19:27 good man! 15:19:56 kragniz: thats the point. remove all the attachments from glance 15:19:58 kragniz: umm, I can help out the spec+BP 15:20:30 #action nikhil_k : create a glance spec and BP for port-out of CIS code 15:20:48 kragniz: i can help with it, since i added most of it in glance ;) 15:20:54 I will link the spec to this BP too 15:21:11 lakshmiS: great 15:21:42 kragniz: you can't 15:21:50 #info https://blueprints.launchpad.net/searchlight/+spec/glance-image-api-plugin 15:21:56 (mark it as affecting more than one project) 15:22:11 sigmavirus24: :( 15:22:29 sjmc7: I guess this work would go in Glance mostly 15:22:38 ? 15:22:43 nikhil_k no 15:22:57 what we proposed for liberty was keeping it all in searchlight 15:23:15 because otherwise we have precisely the same problems we had for kilo that we have little control over the pace we can make changes 15:23:29 and because if plugins are spread around everywhere, making changes to the base code is hard 15:23:35 nikhil_k: did you mean that this is about glance images or where the code lives? 15:23:35 hmm, I thought that was just for tests 15:23:51 lakshmiS: I meant the plugin. 15:24:00 (code) 15:24:04 we can discuss it but i think development will be VERY hard if we immediately try to push plugin code out to other projects 15:24:31 yeah, we discussed this a while ago 15:24:36 nikhil_k: yeah we need to talk about it. 15:25:37 Looks like we should create a breakdown of the implementation of this BP 15:25:50 the code's already there 15:25:56 in the searchlight repo 15:25:58 nikhil_k: the initial idea is to keep glance and nova plugin in searchlight to start with the initial codebase 15:26:09 I think putting this in Glance wouldn't hurt for Liberty and that can be an example for other project in next releases 15:26:27 it makes deployment, testing etc MUCH harder from the get go 15:26:34 nikhil_k: I agree but that should be a seperate BP 15:26:40 cool 15:27:08 so, this is very searchlight centric for now. We can leave other projects scope out. 15:27:14 yeah, i'm good with a separate BP. that is the direction we want to take, but i'd like to get those initial plugins done first 15:27:40 I think that may slow down adoption but we need to focus on getting it to work intiially. 15:27:49 exactly! 15:28:09 * nikhil_k quickly changes his TODOs 15:28:12 yeah, that's my thought 15:28:31 but i agree with using glance as the intial example of where we want to go, just not right now 15:29:17 but in the long run its easy to maintain the glance plugin code in glance(especially for RBAC changes) 15:29:48 yeah 15:30:04 I think we may do oslo.versionedobjects this cycle then 15:30:13 given there is b/w 15:30:42 that complicates stuff a bit for indexing but we will see 15:31:17 yeah will have to maintain multiple index mappings 15:31:46 agree and think the rythm should work 15:32:08 for deployments we need to follow https://blueprints.launchpad.net/searchlight/+spec/devstack-plugin , right? but no one assigned yet 15:32:52 i thought eklarso was interested 15:32:56 someone was keen to do devstack integeration 15:32:58 wko: ekarlso seem to be volunteers 15:32:59 ah, yeah, that's right 15:33:08 #link https://etherpad.openstack.org/p/liberty-searchlight-brainstorming 15:33:22 wko did the intial devstack patch 15:33:41 wayne i think? 15:33:43 yeah 15:34:27 can we assign someone to that ? 15:34:34 lets assign to wko to start with 15:34:54 given it would be great to have it working earlier in the cycle 15:35:06 fyi, Liberty-1 is next week 15:35:14 volunteer for what ? :D 15:35:23 ekarlso: https://blueprints.launchpad.net/searchlight/+spec/devstack-plugin 15:36:38 lakshmiS: sjmc7 we have to just port the code proposed against glance for this https://blueprints.launchpad.net/searchlight/+spec/set-up-functional-tests ? 15:37:14 nikhil_k yep 15:37:14 nikhil_k: oh, who wrote that ? 15:37:17 i can probably do that 15:37:33 #link https://review.openstack.org/#/c/157209/ 15:38:03 sjmc7: I can help you with it if you want me to 15:38:10 #action sjmc7 to port out functional tests proposed against glance to propose against searchlight 15:38:15 we're talking about different things i think 15:38:22 i'm not doing the devstack stuff :) 15:38:25 sjmc7: the functional tests part ;) 15:38:30 :) 15:38:47 ok. i'll port the review over; it will likely need some work 15:39:12 ekarlso: I can ask wayne to get in touch with you on the devstack patch. Are you interested working on it? 15:39:19 lakshmiS: ofc 15:39:26 sjmc7: judging from the looks of it you need to add base scaffolding to get it to work 15:39:31 aye 15:40:16 yeah, glance spins up servers for functional tests 15:40:36 I wonder if that's a correct terminology for such tests more so for searchlight 15:40:47 any preference to calling them integration tests? 15:40:57 nikhil_k: uh I think for that you could just cheat and post out notifications to the MQ where the listeners are... 15:41:01 they are functional, i think, not integration 15:41:05 integration would be tempest 15:41:24 or am I talking about smth diff ;P 15:41:34 ah, probably are .. 15:41:36 nvm me :) 15:41:46 the existing tests were primarily to test RBAC, not notification processing 15:41:50 tempest tests for integration are being ported out 15:42:16 given we would be testing plugins for different projects, I am in more dilemma about the name 15:42:24 tests in glance are confusing as they are 15:42:40 we were going to port out functional tests to tempest as they are more integration like 15:42:55 so that's a bad name currently there 15:43:04 ah, ok 15:43:13 ummm.. in that case, i might not be the best person to do it 15:43:23 I thought other projects were moving their functional tests out of tempest now? 15:43:48 sjmc7: I or some one would need to follow up on what's the speed of porting out tempest tests under projects 15:44:04 in that case we can get rid of functional and just keep integration 15:44:37 s/under/to go under projects umbrella/g 15:44:42 ok.. i'm confused. should i hold off moving that un-merged glance review into searchlight? 15:44:57 sjmc7: yeah, may be we can pick it up next week 15:45:02 kragniz: moving tests out of tempest itself and in project tree under folders aclled "functionaltests" or alike using the tempest-lib 15:45:07 personally i think it's useful having tests that can be run outside the context of devstack that actually exercise elasticsearch 15:45:16 kragniz: so each proj has independent functionaltests 15:45:53 sjmc7: yeah, it would be a very painful job to maintain them and they are very expensive on the CI/CD 15:46:05 yeah == I agree 15:46:15 but that's the tradeoff 15:46:22 ok. so - hold off for now? 15:46:28 yes, please 15:46:45 #action: nikhil_k check tempest-lib adoption speed 15:47:20 nikhil_k: I'l help you out if you want to .. 15:47:20 I just wanted to discuss the preference for the mid-cycle location and dates 15:47:38 ekarlso: awesome, that would be super helpful. ping out offline.. 15:47:43 you* 15:47:49 #topic Mid cycle 15:47:57 #info Horizon is officially the week of July 21 in Fort Collins 15:48:13 We are discussing multiple possiblities for Glance atm 15:48:28 but some memebers are suggesting July 28th 15:48:55 it would be easy for me to go to the horizon one; i can probably get clearance to travel somewhere else but won't be able to do two weeks 15:49:13 I am ok with any date. I will attend remote due to travel budget problems 15:49:13 ah 15:49:57 the 21st was the only way Horizon could get critical mass 15:50:31 yeah, thanks for helping get feedback and decision david-lyle :-) 15:51:03 midcycle scheduling is not fun, for the record :) 15:51:09 :) 15:51:21 anyone else? 15:51:41 is the preference that SL be part of glance's? i guess that makes more sense given the personnel 15:51:52 krykowski : would you be joining us? 15:52:39 sjmc7: My thought was that Travis et.al would be at the Horizon so, may be we can do discussion there and at Glance's too given people can travel 15:53:15 I still think a virtual midcycle might make sense for Searchlight 15:53:19 If Glance happens in bburg, there would be decent number of people interested in getting involved and providing feedback 15:53:38 bburg? 15:53:50 david-lyle: sure. I was thinking more along the lines of -- a few active folks show up 15:54:01 oops, bburg == Blacksburg, VA 15:54:14 nikhil_k: sure, either way 15:54:15 sigmavirus24: do you think if we set location to that you may get to travel? 15:54:24 my apologies for not recognizing the acronym for that seething metropolis! 15:54:44 sjmc7: :) 15:54:53 david-lyle: but I agree, the entire team would need a virtual mid-cycle 15:55:06 nikhil_k: so tl;dr I'm a secondary caregiver and travel is just not going to work for a while now + the sprint planning shenanigans on my team mean I probably won't be able to even take a vacation until August 15:55:24 i'm ok planning for a virtual one 15:55:32 sjmc7: heh. habit fail :-) 15:55:36 if virtual then I can attend :P 15:55:46 and i'm similar - other work commitments are starting to crunch for the next 2 months 15:56:28 sigmavirus24: gotcha 15:56:59 Thanks for the feedback ! 15:57:06 let's see what glance decides, and then make a decision 15:57:30 I guess Glance team just needs to decide how many can show up if non-colocated event happens 15:57:44 yeah. it sounds like not many here can travel in any case 15:58:01 I am a bit worried about people not getting budget approved in that case 15:58:23 may be we will cancle and keep things virtual this cycle 15:58:57 I'd be good with that 15:59:00 sounds like virtual this time! 15:59:06 okey dokey 15:59:09 distributed team! 15:59:35 Thanks all. 15:59:58 thanks for running it 16:00:07 :) 16:00:09 #endmeeting