15:00:48 #startmeeting openstack search 15:00:52 Meeting started Thu Aug 20 15:00:48 2015 UTC and is due to finish in 60 minutes. The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:57 The meeting name has been set to 'openstack_search' 15:01:04 o/ 15:01:24 o/ 15:01:34 Let's give a couple mins. 15:01:35 o/ 15:01:37 o/ 15:01:41 o/ 15:02:00 I don't think sjmc7 will be here at least at the start. There is an HP meeting in seattle that he had to go to. 15:02:27 morning 15:02:27 and there he is 15:02:31 :) 15:02:35 sorry, bit under the weather 15:02:46 https://etherpad.openstack.org/p/search-team-meeting-agenda 15:02:56 Add anything you want as usual 15:03:15 #topic Testing 15:03:33 As mentioned last week, we put up a review for python 3 in the gate. 15:03:37 It went through. 15:03:50 that's all. 15:03:57 :) 15:04:01 Functional tests. 15:04:19 lakshmiS how are they coming? 15:04:27 you were going to put up an initial patch? 15:04:48 ready to go. will put up the patch before the weekend. 15:05:03 Great! 15:05:19 any discussion needed on them with the group here? 15:05:36 nothing specific i can think about 15:05:50 ok, well, i'm looking forward to seeing them. 15:05:57 even though i tried to cover the RBAC filters that rosmaita initially gave 15:06:30 there were some in that patch i had in glance a while back 15:06:35 if that's useful 15:06:45 sjmc7: yeah i ported them 15:07:09 great, thanks 15:07:43 #topic reviews process 15:08:08 so, we're only a couple weeks out in liberty 15:08:26 i'm still hopeful we can have a release. 15:08:54 but i also know that having time to do reviews is difficult for a number of people right now. 15:09:34 i've been trying to catch up on them. 15:09:47 and they are time consuming to fully test. 15:10:14 but wanted to open up some discussion on ideas for how to facilitate getting reviews down in timely manner. 15:10:49 and also what is / isn't okay process-wise 15:11:08 In the early phases of this project. 15:11:26 i know one thing we've tried to stick to is to have +2s from multiple companies, even though there are a majority of HP folks on the core list 15:12:14 if people are ok with approving changes with 2 +2s even if it's just HP folks just as the summit deadline approaches that might help, especially for bug fixes 15:12:43 I think for now that may be a good relaxation of the review guidelines 15:12:50 i agree 15:13:04 i keep hosing my devstack, which is slowing my reviews, so i am part of the problem here 15:13:14 we're still working on critical mass 15:13:17 same with me 15:13:39 I agree too, but would be good if someone can test them functionally. I know TravT is very particular about it and best to keep that practice 15:13:45 yeah, i've been testing them 15:13:54 it is time consuming btu esp given our tests it's necessary 15:14:06 yeah, i seem to be spending a large portion of my days just playing QA recently. 15:14:36 :) 15:15:05 we need downstream applications using searchlight to do that for us:) 15:15:13 lol 15:15:30 we've got people itching to use it :) 15:15:46 I'd still like to ensure that everybody has an opportunity to weigh in at least conceptually. 15:15:58 a +1 would be good to have 15:16:13 yes, just to indicate the idea seems right. 15:16:18 yeah - for features or bp implementations i'd definitely like additional input 15:17:16 but for pure bugfixes it seems less important 15:17:34 yes, and we have several high and critical's sitting out there right now with code proposed. 15:17:45 I also will consider the functional tests to be critical. 15:18:21 because i don't want to see any regressions. 15:19:35 any other input on this specifically? 15:20:48 lakshmiS, last week you had mentioned the idea of having an hour or so available each week for people to interact on specific reviews through end of liberty 15:21:05 that would be nice! 15:21:14 yes lets schedule it 15:21:55 how about Tuesday or Wednesdays at this same time? 15:22:09 in the searchlight room 15:22:35 i don'tmind sparing a couple hours tomorrow just on reviews if someone is available 15:23:16 nikhil_k, there is a question on the nova patch I have for you when we get to it later in this meeting. 15:23:18 tuesday would be better for me 15:23:27 wed looks better for me, otherwise 15:23:37 both are good with me 15:24:03 i am travelling for work mon, tue most likely 15:24:35 i can do either. 15:24:44 is wednesday out for you rosmaita 15:24:46 ? 15:25:39 either's ok with me, wednesday maybe a bit easier 15:26:19 I' fine with either 15:26:49 david-lyle: i'm still trying to figure out if i can psych myself up for your added early morning horizon meeting on wednesday. :( 15:26:57 :) 15:27:20 actaully, I may be online at 1500utc on tuesday but not 100% sure 15:27:43 If possible, let's shoot for Tuesday 15:27:58 I'll check in on Monday with everybody 15:28:37 just not 2000 or 2100 UTC on Tues those are taken with TC and X-Project 15:29:06 that is way too late for lakshmiS anyway 15:29:08 http://everytimezone.com/#2015-8-20,180,cn3 15:29:18 ok, just making sure 15:29:19 that's the time slot shooting for on Tuesday. 15:29:34 if you can't make it nikhil_k, we'll bump to wednesday 15:29:52 ok, on to but reviews 15:29:56 thanks TravT 15:30:01 #topic bugs 15:30:04 it says 8:30 PM local time for me which is same as now 15:30:29 so, this one: 15:30:30 Fix for Authentication not happening https://review.openstack.org/211047 15:30:43 TravT: i cann do wed, but have team mtg at 15:30 15:31:11 I kind of like tuesday better than wednesday 15:31:23 just so we have a day between that and this meeting 15:31:48 so, this one: Fix for Authentication not happening https://review.openstack.org/211047 15:32:01 even with allowing 2 +2s from same company, it needs another. 15:32:14 it is a critical bug 15:32:30 so, nikhil_k, david-lyle, sigmavirus24, rosmaita, if one of you could take a look 15:33:13 ack 15:33:29 note that i co-authored, so I can't +2 it. my +1 was only to indicate it was ready for reviews. 15:33:48 looking, can try out the patch after this 15:34:01 thatnks david 15:34:06 i am looking at that, but hosed my devstack 15:34:09 thanks david-lyle 15:34:25 i did test it, generated configs and docs looked good to me 15:35:08 there are a couple more critical highs. 15:35:17 Fix RBAC filters https://review.openstack.org/212563 15:35:26 I tested that one yesterday with images and the nova servers patch. 15:35:34 yeah, this was a good one 15:35:37 tried about 8 different queries on it. 15:35:45 i put those in a paste in my review comments. 15:36:18 laskhmiS, would be good to consider that with any of the RBAC functional tests you are doing 15:36:41 so maybe you could take a look lakshmiS? 15:36:47 we should provide guidance on writing these in the docs, or abstract some of it to the base class at some point. it's easy to screw up 15:36:49 ok i will check if its covered 15:37:16 Your sorting patch, sjmc7 Sorting https://review.openstack.org/#/c/206268/ 15:37:24 I will look at this one 15:37:30 yeah.. just needs reviews 15:37:39 it should be pretty straightforward 15:37:59 passthrough of the e-s DSL for sorting 15:38:19 ok. 15:38:32 On to BPs 15:38:36 you actually could do it already by passing it inside the 'query' parameter 15:38:43 but this makes it more explicit 15:39:36 #topic nova plugin 15:39:49 Nova instances plugin https://review.openstack.org/198852 15:39:57 i've been harassing sjmc7 on this one quite a bit 15:40:00 and it is very close 15:40:07 i do feel quite harassed 15:40:29 question for rosmaita and nikhil_k 15:40:47 currently the following fields are filtered if you aren't admin 15:40:57 OS-EXT-SRV-ATTR:host 15:41:08 OS-EXT-SRV-ATTR:hypervisor_hostname 15:41:13 are there others we should add? 15:41:27 there's a hostId too 15:41:30 Sorry, in the middle of a sad sad video call 15:41:32 which it occurs should probably be protected 15:41:48 sigmavirus24: need some kleenexes? 15:41:49 :) sigmavirus24. the best kind! 15:42:00 no 15:42:06 send the strongest of alcohol 15:42:12 lol 15:43:40 rosmaita: nikhil_k: if you could add a comment on that patch in this file about fields to filter for admin 15:43:41 https://review.openstack.org/#/c/198852/14/searchlight/elasticsearch/plugins/nova/servers.py 15:43:55 TravT: don't quite have them ready but can check 15:44:17 sure. line 30. 15:45:01 other than a few other nits on that patch and some ideas for future things, that patch worked quite nicely for me 15:45:11 so, maybe we can get nova support in by end of this week. 15:45:30 TravT: so, I am not sure about the extensions and their indexing 15:46:11 am aware that they were being proposed to be purged or moved to regular api but not sure if we can ever come up with a list of all the ext attrs that are admin only 15:46:44 they depend on which ext are enabled by the deployer and we will be playing cat and mouse 15:46:49 so, sorry some context: 15:46:54 nikhil_k: in some of my comments on that patch, i suggested that we add a plugin config for whitelisting / blacklisting fields. 15:47:12 OS-EXT-* are OS Extensions added to nova api 15:47:26 until we do that we could have a whitelist of extension fields in the code 15:47:39 so we don't accidentally scrape up any we shouldn't 15:47:47 that sounds good 15:48:33 here's a comment I put on the patch: 15:48:35 It really also occurs to me that when we do that the nova plugin should support having separate extension files for all these extension fields. The extensions enabled would all be invoked during serialize function and also would be called to add to the mapping. This way deployers could add their extension without modifying source just like they do for nova. BP needed. 15:48:54 yeah. maybe not a liberty timescale thing at this point 15:49:56 ah cool 15:50:13 nikhil_k, you mentioned having review time tomorrow. 15:50:23 yes 15:50:31 maybe you could do another pass on the nova patch. 15:50:42 sure 15:50:50 on my list now 15:50:51 hopefully sjmc7 will be able to address my current comments before tomorrow and i'll do another pass 15:51:03 ok. 15:51:12 yeah, will do 15:51:31 darn, evernote app broke on my m/c 15:51:49 ok, did want to mention that following our BP review last week I opened the client blueprint we discussed. 15:51:56 https://blueprints.launchpad.net/searchlight/+spec/initial-openstack-client-search-plugin 15:51:58 just FYI 15:52:15 #topic open discussion 15:52:30 i've actually got to run, meeting i have to attend in the office 15:52:54 ok. 15:53:02 anything anyone needs, i'll be in the SL channel in a biit 15:53:03 i think everybody is quite busy these days. 15:53:08 http://lists.openstack.org/pipermail/openstack-dev/2015-August/072082.html 15:53:21 is a thread about keystone and pagination 15:53:41 but the current stance by keystone on the v3 API makes it impossible to index 15:53:42 i saw that one :) 15:53:44 good reading! 15:54:02 oh interesting. 15:54:06 so, that's awesome 15:54:07 i didn't see it 15:54:21 this is not new, but progress is feeling unlikely 15:54:22 that is awesome. :( 15:54:43 promising 15:55:36 the other option is build based on other indexed data 15:56:36 david-lyle? 15:56:43 trying to figure out what you mean. 15:56:50 me too :P 15:57:14 ok, well, i'll read through that thread 15:57:15 no, you could go do a secondary request based on results from nova, etc 15:57:48 nova data will have project ids, you could request data on project ids returned with the data 15:58:06 but that's an incomplete index 15:58:14 so maybe worse :( 15:58:32 we could just run a scheduled job and periodically get all projects from keystone. 15:58:54 well no, you can't actually 15:59:00 yay 15:59:12 you'll get the first 500 or 1000 and an error saying there are more 15:59:18 but no way to index into them 15:59:47 will have to go to their db then:) 15:59:49 unless you dynamically build up a filtering scheme until you get below the MAX return # threshold 16:00:30 okay, we are out of time, but this was good to bring up 16:00:33 Thanks! 16:00:35 we can continue 16:00:41 on it in the future. 16:00:44 #endmeeting