15:01:01 #startmeeting openstack search 15:01:02 Meeting started Thu Apr 6 15:01:01 2017 UTC and is due to finish in 60 minutes. The chair is sjmc7. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:07 The meeting name has been set to 'openstack_search' 15:01:37 o/ 15:01:38 morning all 15:01:41 o/ 15:01:45 o/ 15:01:45 o/ 15:02:32 we’ll start in a minute or two 15:03:02 o/ 15:03:17 probably going to be a short one this week, but we’ll see 15:03:24 #topic nova cells 15:03:56 The spec got approved on nova, though it looks like there’s still some differences of opinion - https://review.openstack.org/#/c/441692/ 15:04:35 The short version is that there’ll be a fallback path if SL isn’t enabled, but for now they want to move forward and find out any issues we’ll run into 15:05:24 Matt considered SL side to be the dependency of nova side, so maybe I will help on the versioned notification handler bo 15:05:26 Np 15:05:29 Bp 15:05:39 i put up a patch for that at https://review.openstack.org/#/c/453352/ 15:05:49 it’s WIP with some rough edges, but does work 15:06:10 Ah cool 15:06:32 The additional payloads are merging slowly:( 15:07:17 that’s ok. i did have some questions about the versioning 15:07:25 i’m not sure what to do about expected vs supported versions 15:08:20 with the microversion API we can request a specific version and know what we’re getting. with the versioned notifications it looks like we’ll just get a version but may not know ahead of time which one 15:08:49 i guess we’d need a handler per possible version which could get out of control pretty quickly 15:09:25 hmm 15:10:06 horizon has had the same problem with microversion APIs, that they have either had to create lots of code paths to support different potential API versions or peg to a known microversion 15:10:29 maybe we can have a handler per release? 15:10:32 as long as the notification version doesn’t change tens of times per release we’re probably ok 15:10:56 yeah, that would make sense. pick a version per release and support it 15:11:20 the other problem i had was that i was receiving both versioned and unversioned notifications because of the way the oslo messaging binding works 15:11:36 But this might means we have to do quick response at the end of each release 15:11:57 yes, it might. but hopefully nova is reasonably stable towards the end of releases 15:14:03 Did you configure the to send only versioned one? 15:14:15 no, i left the default (because that’s how many people will deploy) 15:14:34 so yeah, setting it to versioned only solves it, but it seems unreasonable to force that 15:14:35 Default sends both 15:14:59 yes 15:15:16 i was expecting only to receive them on the versioned_notifications topic, but i was getting both, so i’ll look at that too 15:15:51 Hmm strange 15:15:55 are they separated by notification exchanges? 15:16:30 Need to check the code... 15:16:47 mm… possibly not. i’ll take another look at it, it’s definitely possible i have something configured wrong 15:17:18 i’ll do some more work on that patch and get it to a point it’s working reasonably well, but it doesn’t look like there’s any significant barriers 15:17:42 Kevin_Zheng or anyone else - did you have anything else about the nova cells work? 15:18:15 No, I will help on review 15:20:04 ok 15:20:10 the only other topic i had was.. 15:20:16 #topic glance community images 15:20:41 rosmaita: we spoke about this at the end of ocata and in the end i think searchlight punted on it 15:20:51 but it looks like the nova work could also benefit from overridable default filters 15:20:59 yes, i saw your spec 15:21:02 so we might be able to do the ‘hide community images unless i ask for them' 15:21:29 it's probably a good idea, because community images offer the potential for a lot of spam 15:21:44 (if anyone ever uses them) 15:23:56 :) ok. well, once i (or someone) gets round to that feature for nova (where it sounds like it’s sort-of-mostly-essential) we can try applying it to glance 15:24:49 makes sense to me 15:25:22 ok. that was all i had for topics 15:25:25 #topic open discussion 15:25:57 if anyone’s got any burning questions, go for it, otherwise i’ll call it in a few minutes 15:31:56 ok, thanks folks. have a good weekend! 15:31:58 #endmeeting