15:01:34 #startmeeting openstack search 15:01:34 Meeting started Thu Jun 2 15:01:34 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:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:37 The meeting name has been set to 'openstack_search' 15:01:41 o/ 15:01:48 o/ 15:01:58 \o/ 15:01:58 o/ 15:02:03 o/ 15:02:03 o/ 15:02:13 how is everybody today? 15:02:53 sunny 15:02:56 Fine, thanks for joining us from Florida! 15:03:07 sure... i am technically on vacation right now 15:03:16 but couldn't get the kids moving this morning 15:03:22 so, figured i might as well join the fun here 15:03:25 anyway 15:03:28 https://etherpad.openstack.org/p/search-team-meeting-agenda 15:03:51 not much on the agenda list today 15:03:55 #topic newton-1 milestone 15:04:04 We have hit the newton 1 milestone. 15:04:19 i submitted the tag requests for searchlight ui and searchlight last night 15:04:28 Doug approved them through. 15:04:48 yeah, i got the release email spam 15:04:55 as we had previously discussed, we are targeting 1.0 this time. 15:05:05 seeing how this is actually our 4th release, seems about time 15:05:31 i didn't submit a release request for the client. 15:05:44 that is release independent anyway 15:05:58 i don't believe there are any huge changes needing to be released 15:06:02 nope 15:06:26 for searchlight UI, it is worth noting that it is not backwards compatible with mitaka horizon 15:06:34 but this is due to changes in upstream horizon 15:06:38 i think that’s true for most horizon plugins 15:06:50 yeah, i think so 15:06:59 * TravT can hear david-lyle groaning 15:07:34 okay, well, milestone 1 is mostly a non-event 15:07:39 just a marker in time. 15:07:53 but it is a good time to talk about where we are in the release 15:07:57 #topic open reviews 15:08:22 coming out of the summit 15:08:30 we had really established a couple of primary goals 15:08:36 1) production readiness 15:08:48 2) improved notifications (related to above) 15:09:04 3) supporting nova fully 15:09:20 Cool 15:09:42 In addition, we would like to bring in the pipeline architecture early in the cycle if it is coming in. 15:10:31 I think we have made good progress on 1. The zero downtime indexing has gone well. A few more BPs are open 15:10:48 The notifications have been improved or are in progress 15:11:02 ES 2.x seems to be fully supported now 15:11:04 yeah, though still some room to improve 15:11:22 yes, i think es2 is fully supported. we’ll try to move the CI jobs to it 15:11:30 Yeah, that'll be great 15:11:36 and then devstack, though that will be harder 15:11:53 cool, will upgrade my dev environment to use 2.x 15:12:03 Does Searchlight recommend any version of ES (1.* vs 2.)? 15:12:20 RickA-HP: 1.7 for mitaka 15:12:34 though we should be compatible with both 15:12:51 we haven’t used any 2.x-only features, nor relied on any 1.x ones that have been removed 15:13:23 The primary reason to recommend 2.x is that ES is trying to push people in that direction 15:13:46 We don't have a formal statement of ES support though 15:14:01 It wouldn't hurt to document it. 15:14:16 I'm wondering if I should upgrade my dev env to 2.*, or stay at 1.7 to help verify that 1.7 stays working. 15:14:26 I have both setup 15:14:35 my devstack is 1.7.something 15:14:40 yeah, i use both 15:14:59 Death by combinatorics! 15:15:03 and my local setup (non devstack) has es 2.x and 1.x. Just depends on which one I decide to turn on. 15:15:26 I think it would be good to push towards 2.x 15:15:38 maybe we can even get openstack to agree to a deprecation of 1.x 15:15:56 sjmc7 had sent out an email on that early in newton, with limited response 15:16:16 ceilometer team said “give it a go and see what breaks” :) 15:16:34 yeah, we should really push for that devstack change now 15:16:44 so that teams have time to address issues. 15:17:44 is anybody already signed up to do that? 15:18:23 i guess i can give it a go 15:18:50 ok, maybe it won't be too hard. just submit the change to the script. 15:19:52 we have a few specs to review 15:19:53 https://review.openstack.org/#/q/project:openstack/searchlight-specs+status:open 15:20:29 Kevin_Zheng: I added a comment on the server groups one this morning. 15:21:32 Yeah, thanks I just saw it 15:22:34 Will update tomorrow 15:22:50 sounds good 15:23:05 just in case you didn't see it before, here is a plugin authoring guide: http://docs.openstack.org/developer/searchlight/authoring-plugins.html 15:23:29 Ah, thanks 15:23:33 might be helpful to you 15:24:09 Yes looks really useful 15:24:21 Thanks a lot 15:24:30 thank sjmc7 for most of it. 15:24:44 he did a nice job on writing it up 15:24:55 aww, shucks 15:25:07 Really cool 15:25:20 lei-zh: looks like you just addressed feedback on the pipeline spec 15:25:44 i probably won't be able to look until next week (still on vacation). 15:25:53 but if others can please take a look as well 15:26:02 i’ll take another look 15:26:11 think it’s mostly done 15:26:23 yes, I konw it's a difficult one, comments and concerns are welcome 15:26:54 I think we are all still conceptually alligned 15:27:06 and the difficult part will be the code... ;) 15:28:01 sure, it requires lots of work : ) 15:29:14 let's plan on doing a formal BP review for priority, etc in a couple weeks. 15:29:25 see if there are things that need to be bumped out. 15:29:35 are there any BP's anybody wants to bring up now? 15:30:16 don’t think so 15:30:34 most of the high priority ones are either underway or for new plugins that folks are working on 15:31:11 ok 15:31:25 we’re waiting on upstream changes for some stuff 15:31:37 like some of the neutron ports, cinder backups 15:31:48 yes, anything we need to / can do to help those along? 15:32:41 is the ironic plugin also waiting for notifications to be implemented 15:32:51 i’m still not really sure of the etiquette around asking for changes in other projects 15:32:52 well, yes and no. 15:33:11 ironic "instances" all will be available via nova. 15:33:12 i guess the obvious answer is “submit patches” but a lot of the code is pretty opaque to just waltz into 15:33:46 but i'm wondering if we need to do something to detect the difference between ironic and vm instances and show as a different resource type 15:34:11 does nova know? 15:34:30 i don't know? 15:34:31 sorry, does nova make that apparently to a user 15:34:45 lei-zh: ironic is working on more notifications 15:34:47 https://bugs.launchpad.net/searchlight/+bug/1526408 15:34:47 Launchpad bug 1526408 in Ironic "[RFE] Add notification support to ironic" [Wishlist,In progress] - Assigned to Mario Villaplana (mario-villaplana-j) 15:35:05 and at the summit 3 folks from ironic came to our session and told us to comment on the patches 15:35:09 to make sure we get what we need 15:36:30 seems it's still under work 15:36:34 if you or anybody knows enough about ironic to comment on their notifications, it wouldn't hurt. 15:36:44 i think the same message we give to all the teams. 15:36:58 please give out all data you'd want to be indexed via notification 15:37:03 we don't want to do any callbacks 15:37:23 Sure 15:38:12 yeah, I'll try to find someone to have a look 15:38:34 lei-zh: thanks! 15:38:50 you are welcome :) 15:39:00 okay, well, is there anything else that people would like to discuss today? 15:40:03 nope 15:40:29 i assume some of our friends here would like to get to sleep tonight. 15:40:42 thanks everybody! 15:41:01 Thanks 15:41:07 thanks, bye 15:41:18 #endmeeting