Tuesday, 2015-11-17

ekarlsoTravT: anything I can help with ?00:00
TravTahh, thanks for looking at that. i didn't get a chance yet today00:00
TravTi'm trying read sjmc7's aggregation code...00:01
ekarlsowhat's that for ?00:01
ekarlso:p00:01
TravTfacets... basically displaying doc counts in UIs and such00:01
*** sigmavirus24 is now known as sigmavirus24_awa00:03
TravTekarlso: we've got a number of BP or bugs with nobody assigned.00:04
TravTthis one seems like one you probably would be able to fix quickly: https://bugs.launchpad.net/searchlight/+bug/146933600:05
openstackLaunchpad bug 1469336 in OpenStack Search (Searchlight) "Errors are returned as html" [Medium,New] - Assigned to Ian Cordasco (icordasc)00:05
TravTFYI, i've got to run for a few moments... brb00:06
*** itisha has quit IRC00:11
*** daddyjoseph97 has quit IRC00:20
*** yingjun has joined #openstack-searchlight00:36
*** yingjun has quit IRC01:45
*** yingjun has joined #openstack-searchlight01:45
*** yingjun has quit IRC01:50
*** yingjun has joined #openstack-searchlight02:00
*** bpokorny_ has joined #openstack-searchlight02:02
*** bpokorny has quit IRC02:06
*** bpokorny_ has quit IRC02:07
openstackgerritMerged openstack/searchlight: Feature/Bug workflow corrections  https://review.openstack.org/24593902:59
*** yingjun has quit IRC04:04
*** yingjun has joined #openstack-searchlight04:04
*** yingjun has quit IRC04:09
*** TravT_ has joined #openstack-searchlight04:52
*** sigmavirus24_awa has quit IRC05:00
*** TravT has quit IRC05:00
*** notmyname has quit IRC05:00
*** sigmavirus24_awa has joined #openstack-searchlight05:01
*** sigmavirus24_awa has quit IRC05:02
*** sigmavirus24_awa has joined #openstack-searchlight05:02
*** sigmavirus24_awa is now known as Guest8755305:02
*** notmyname has joined #openstack-searchlight05:03
openstackgerritMerged openstack/searchlight-specs: Setup Initial Spec Repo Contents  https://review.openstack.org/24521405:10
*** sballe has quit IRC05:25
*** sballe has joined #openstack-searchlight05:30
*** lakshmiS has joined #openstack-searchlight05:39
*** bpokorny has joined #openstack-searchlight05:43
*** yingjun has joined #openstack-searchlight06:09
*** bpokorny has quit IRC06:09
openstackgerritLi Yingjun proposed openstack/searchlight: Init searchlight client base  https://review.openstack.org/24566006:30
*** yingjun_ has joined #openstack-searchlight06:33
*** yingjun_ has quit IRC06:34
*** yingjun_ has joined #openstack-searchlight06:35
*** yingjun has quit IRC06:35
*** dhellmann has quit IRC07:01
*** dhellmann has joined #openstack-searchlight07:02
openstackgerrityuntongjin proposed openstack/searchlight-specs: This BP is implementing a notification-forwarding for SearchLight index  https://review.openstack.org/24622007:05
*** lakshmiS has quit IRC07:24
*** lakshmiS has joined #openstack-searchlight07:25
*** yingjun_ has quit IRC08:10
*** yingjun has joined #openstack-searchlight08:10
*** lakshmiS_ has joined #openstack-searchlight08:26
*** lakshmiS has quit IRC08:30
*** yingjun has quit IRC08:40
*** lakshmiS_ has quit IRC08:48
*** yingjun has joined #openstack-searchlight08:59
*** yingjun has quit IRC09:16
*** ekarlso has quit IRC09:22
*** openstackgerrit has quit IRC09:31
*** openstackgerrit has joined #openstack-searchlight09:32
*** gb21_ has quit IRC09:33
*** ekarlso has joined #openstack-searchlight09:37
*** ekarlso has quit IRC09:38
*** ekarlso has joined #openstack-searchlight09:38
*** GB21 has joined #openstack-searchlight09:45
*** ekarlso has quit IRC09:57
*** openstackgerrit has quit IRC10:31
*** openstackgerrit has joined #openstack-searchlight10:32
*** ekarlso has joined #openstack-searchlight10:36
*** ekarlso has quit IRC10:39
*** yingjun has joined #openstack-searchlight11:19
*** lakshmiS has joined #openstack-searchlight11:49
*** lakshmiS has quit IRC11:54
*** GB21 has quit IRC12:26
*** GB21 has joined #openstack-searchlight12:36
*** GB21 has quit IRC12:45
*** yingjun has quit IRC13:00
*** yingjun has joined #openstack-searchlight13:04
*** rosmaita_ is now known as rosmaita14:01
*** ekarlso has joined #openstack-searchlight14:01
*** yingjun has quit IRC14:11
*** yingjun has joined #openstack-searchlight14:11
*** yingjun has quit IRC14:15
*** nikhil_k is now known as nikhil14:39
*** ekarlso has quit IRC14:40
*** lakshmiS has joined #openstack-searchlight14:54
TravT_o/15:02
*** TravT_ is now known as TravT15:02
david-lyleo/15:02
sjmc7mornin15:02
lakshmiSo/15:02
TravTdavid-lyle: lakshmiS: sjmc7: rosmaita: nikhil: we were going to go through BP priorities this morning.  Still up for it?15:02
TravTi can practically feel your enthusiasm!  :P15:04
david-lylethat's why I'm here :)15:04
sjmc7my enthusiasm hasn’t had any coffee yet15:04
lakshmiS:)15:05
TravTsjmc7: i have begun the intake on that myself15:05
* TravT still looking to install an IV drip line15:05
TravTi thought maybe we should just touch base on bug priorities first.15:05
TravThttps://bugs.launchpad.net/searchlight15:05
TravTsjmc7 and I have been talking about plugin cleanups15:06
TravThe filed a related bug15:06
TravThttps://bugs.launchpad.net/searchlight/+bug/151502815:06
openstackLaunchpad bug 1515028 in OpenStack Search (Searchlight) "Separation between plugin and notification handler isn't clean" [Critical,In progress] - Assigned to Steve McLellan (sjmc7)15:06
TravTwhich I think is top priority15:06
TravTif we're going to make plugin improvements, i think it should be done sooner than later15:06
rosmaitao/15:06
sjmc7there’s a patch up for it15:06
sjmc7which is ready for feedback, but i’m expecting to have to do some more jiggling on it15:07
TravTi littered it with comments last night sjmc715:07
sjmc7splendid. i will jiggle away15:07
TravTrosmaita: o/15:08
TravTso, i guess take a look at the bug list first and see if there are any priority questions15:08
TravTone of them doesn't have a priority15:08
sjmc7we have bugs??!15:08
TravTsjmc7: shocking, right?15:09
rosmaitai agree that 1515028 is a priority, and like sjmc7's analysis15:09
TravTso this one doesn't have a priority.15:10
TravThttps://bugs.launchpad.net/searchlight/+bug/151501515:10
openstackLaunchpad bug 1515015 in OpenStack Search (Searchlight) "Rename default config file to searchlight.conf" [Undecided,In progress] - Assigned to Liyingjun (liyingjun)15:10
TravTi'm tempted to make it a high... just from the standpoint that things like that should change early in the cycle.15:10
sjmc7yeah.. it’s more of an annoyance than anything, but i agree it’d be better to change it earlier than later15:11
lakshmiSyeah makes sense.15:11
sjmc7i think there was a patch for that one too, which i didn’t get round to looking at yesterday15:11
lakshmiSbut lets check quickly if there is any naming convention for multiple configs15:11
TravTyeah, need to also discuss the relationship with this patch: https://bugs.launchpad.net/searchlight/+bug/149397515:12
openstackLaunchpad bug 1493975 in OpenStack Search (Searchlight) "Need separate config sections for api and listener" [Medium,In progress] - Assigned to Itisha Dewan (ishadewan07)15:12
TravTso should we still have separate config files or not?15:14
sjmc7i don’t think we need them right now15:14
lakshmiSi think if its just log entries separate sections are enough but depends on how much more we customize15:14
*** Guest87553 is now known as sigmavirus2415:15
sjmc7even then, it’s best to set log-dir15:15
TravTso then does this patch close that defect?15:16
TravThttps://review.openstack.org/#/c/232200/15:16
sjmc7right now, i don’t think it’s required at all15:17
*** akanksha_ has joined #openstack-searchlight15:17
sjmc7the usual way to do this is not to specify individual files15:17
sjmc7but to specify a directory15:17
sjmc7oslo.logging figures out the name15:17
*** itisha has joined #openstack-searchlight15:18
TravTwell, i think the guidance you left in itisha 's patchset and on the bug is a somewhat vague.15:19
TravTif i read the bug, it indicates log_dir15:20
sjmc7ok, will take another look15:20
TravTif i read the patch set, it seems that the whole bug should be superceded by a patch for separate config files15:20
TravTok, any other questions on priorities for bugs or do we agree with the current priorities on them?15:21
sjmc7nope, lgtm15:21
TravTok15:21
lakshmiSnot many bugs. that good15:21
TravTfeatures...15:21
TravThttps://blueprints.launchpad.net/searchlight15:21
TravTthe feature workflow went through, the base spec repo is set up now15:22
* david-lyle is very jealous of the bug #15:22
TravTdavid-lyle: lol15:22
TravTany of the blueprints with a priority are generally what I thought the priority should be15:23
sjmc7so many!15:23
TravTbut feel free to disagree / discuss15:23
sjmc7i filed https://blueprints.launchpad.net/searchlight/+spec/denormalize-nova-image-flavor15:24
sjmc7but i think it’s just me that’s obsessed by it15:24
lakshmiShttps://blueprints.launchpad.net/searchlight/+spec/discuss-notifications-with-service-teams this may needed to split to make it easier for someone to pickup15:25
TravTlakshmiS: yeah, it is pretty vague.15:26
sjmc7we kind of had the discussion, at least with the nova team, at the summit15:26
TravTi did go to the nova session at the summit to talk about it.15:26
sjmc7so maybe we can close it15:27
TravTand sjmc7 / briancline did go to the swift team meeting15:27
TravTand lakshmiS talked with ceilometer15:27
sjmc7let’s close it then15:27
TravTi think maybe we should just close15:27
sjmc7i think i roughly agree with the priorities there. there are some ‘undefined’ ones15:28
lakshmiSthis needs to prioritized - https://blueprints.launchpad.net/searchlight/+spec/index-perf-tests15:28
lakshmiSwhich will drive other priorities or more bugs15:29
lakshmiSmaybe this a duplicate of it https://blueprints.launchpad.net/searchlight/+spec/query-perf-tests15:30
TravTlakshmiS: do you mean you want the priority bumped higher?15:31
sjmc7my feeling is indexing performance is more of a concern than query performance15:32
lakshmiSyeah close one of them and bump it15:32
sjmc7i don’t think they’re duplicates though15:32
TravTwell, i think they are different.15:32
sjmc7different ends of the pipe15:32
TravTindexing is the initial indexing and notification indexing15:32
lakshmiSso query performance is about the parser?15:33
lakshmiSoh ok15:33
TravTlakshmiS: probably query perf is more about the searchlight process hop, but maybe also about how you configure things in a large scale env (multiple indexes, # shards, etc)15:34
TravTbut not sure15:34
TravTi think the indexing perf tests are probably a bigger deal.15:35
lakshmiSwhich i guess we are not there yet15:35
TravTwell, i bumped indexing perf test to medium.15:35
TravTshould it be higher?15:36
sjmc7i think high is ok15:36
sjmc7er, medium15:36
sjmc7that was freudian15:36
lakshmiSi think its important but we dont have a use case so its ok15:36
* nikhil sneaks in15:37
TravTnikhil: we're just talking about the perf tests15:37
lakshmiSright timing15:37
sjmc7sit at the front of the class, nikhil15:37
nikhilaha15:37
nikhilI used to15:38
TravT*nikhil sneaks out15:38
nikhilthen decided that kids aren't so cool there :P15:38
TravT;P15:38
nikhilare we discussing anything in particular?15:38
TravTpriorities on blueprints15:38
TravTi think we're now going to go through those with "undefined"15:39
nikhilTravT: hmm, may be I shouldn't have scrolled back up and read your sneaks out comment to actually do it #D15:39
TravTwe were just talking perf tests15:39
TravTwhich you still have assigned as owner15:39
nikhilI was curious about anything in particular for perf tests15:39
TravTwe still want them15:39
TravT:D15:40
nikhilok, and pythonic ?15:40
nikhilin gate?15:40
*** bpokorny has joined #openstack-searchlight15:40
nikhil(non-voting?)15:40
*** bpokorny has quit IRC15:40
TravTwell, i'd be quite happy to get the functional tests in gate and voting15:40
TravThttps://blueprints.launchpad.net/searchlight/+spec/zuul-functional-tests15:40
nikhil(plugin specific or congregated ?)15:40
*** bpokorny has joined #openstack-searchlight15:41
nikhilthat one seems rather straightforward15:42
TravTnikhil: do you want to own it?15:42
nikhilsure, I can do that today or tomorrow15:42
TravTassigned to you.15:43
TravTok... on to the undefineds15:43
TravThttps://blueprints.launchpad.net/searchlight/+spec/notification-forwarding15:43
TravTthe intel team interested in this already did a POC15:44
TravTwe just need to review the spec and ensure it goes in a direction that makes sense15:45
nikhilwow, nice interest in notifications! prolly first time I have seen15:45
sjmc7there’s a lot of interest :)15:45
nikhilTravT: should we copy over the contents to a spec?15:45
TravTnikhil, they did that last night.15:46
TravThttps://review.openstack.org/#/c/246220/15:46
nikhiloh, I didn't see the spec url in the BP.15:46
nikhillet me find it15:46
TravThere's where this makes a lot of sense to me15:46
TravT2 reasons.15:46
* david-lyle needs to step away15:47
TravT1) in solutions where searchlight is being used for a searchable cache, if you will, you wouldn't want to receive notifications until the cache is updated15:47
nikhilhuh15:48
TravT2) searchlight supplements the data, so you wouldn't want to repeat that work elsewhere for end user facing notifications.15:48
TravTnikhil: here's an example15:48
TravTlet's say horizon is hooked up to searchlight and providing list queries from searchlight15:49
TravTand they hook up horizon to receive updates from notifications15:49
TravTyou want to avoid a race condition15:49
TravTwhere a user gets a notice that say an instance is created15:49
TravTbut they go to the list instances page which is populated from searchlight and the instance doesn't show up.15:50
TravTideally that takes less than a second15:50
TravTbut, you'd not want to notify the UI of something that isn't visible in search results yet15:50
nikhilhmm, makes sense on the UI consistency.15:51
TravTanyway, i think since we have gotten a lot of interest in this and there are developers working on it, we could give it an initial priority of medium.  We do need to work through the spec though...15:52
TravTthoughts?15:52
nikhilI guess we are saying this is pluggable for horizon/dashboards and not necessarily the flow one expects from outbound notifications?15:52
nikhilI mean what if notifications are exposed to end users15:52
*** lakshmiS_ has joined #openstack-searchlight15:53
nikhildo we expect the operators to populate SL cache first in that case?15:53
TravTthere is another use case that the spec authors bring up.15:53
TravTthey want to leverage zaqar features for subscription, but they want the notifications to have all the data that searchlight has (which many notifications on the internal bus don't)15:54
TravTso they thought plugging searchlight in then having it forward along to zaqar would allow for this to be accomplished15:55
nikhilhmm15:55
TravTi spoke a bit about this with flavio at the summit and he seemed to think it was reasonable15:56
nikhilI guess I have a couple of pointers on that (may be I should comment on the spec too)15:56
*** lakshmiS has quit IRC15:56
TravTwell, we did just set up the spec repo for that. :P15:57
sjmc7the system works!@15:57
nikhil1. are we establishing a contract for the convergence on the internal bus, zaqar and SL notifications (what if someone has secure/sensitive information)15:57
TravTnikhil: i think that should be part of the notification forwarding spec.  a configurable filter.15:58
nikhil2. there are systems that have notification buses not so similar to what is described in the BP15:58
TravT2, i was thinking a driver like interface... but15:59
nikhilfor example, there could be internal service -> auditors -> subscriptions tools -> zaqar15:59
TravTlet's guide that on the spec15:59
nikhilyeah15:59
TravTas for priority, do we leave unprioritized or give it an initial priority?16:00
nikhils/could be/are existing/g16:00
lakshmiS_it could be high if horizon use case will be implemented for this release16:01
* TravT just looking at rest of list16:02
sjmc7we have a number of things i think are more important like adding resources and improving stability16:03
TravTI think i'd start it at medium16:03
TravTconditional on spec approval16:03
TravTwhich really means we have to provide feedback on the specs out there (i have one, steve has one, and this one016:04
nikhil:D16:04
TravTany objection to starting it at medium?16:04
TravTgoing once16:05
TravTgoing twice16:05
TravTdone16:05
sjmc7you have an alternate career as auctioneer16:05
TravTi'd prefer one as a lottery winner16:06
TravTi sense we are nearing overload for this meeting... but there are a few more to touch on16:07
TravTdefer to another time or get through the next couple?16:07
lakshmiS_i guess just few more16:08
TravThttps://blueprints.launchpad.net/searchlight/+spec/denormalize-nova-image-flavor16:08
TravTwhich has an inter-relationship with https://blueprints.launchpad.net/searchlight/+spec/nova-flavor-plugin16:08
sjmc7i don’t know how important that is (the first one)16:09
sjmc7it just annoys me16:09
TravTbasically, this says that we can include flavor information (more than just ID) when getting servers16:09
TravTand can search by more than just ID16:09
TravTdefinitely VERY nice to have16:09
sjmc7the problem is when they change16:09
TravTbut to date we just go in circles on how to handle it16:10
sjmc7although i would imagine flavors change so seldom we could take the hit16:10
sjmc7yeah. if it’s just me that it annoys, then we can keep this one on the backburner16:10
TravTit annoys me too... which is why you and I have had so many discussions on it.16:10
* nikhil wonders why people are in a bitter mood today. checks twitter, news ..16:10
* TravT wonders why nikhil wonders why people are in a bitter mood16:11
nikhilthere you go again16:11
lakshmiS_i think we should differ meeting to other time ;)16:11
* nikhil bbiab16:11
TravTi think perhaps nikhil wouldn't think we were in bitter mood if over video16:12
TravThard to see laughing16:12
nikhilguess what I managed to stumble upon at the same time as your comment TravT https://twitter.com/notmyname/status/66640286002895667216:13
TravTlol16:13
nikhilirc == open office16:13
lakshmiS_oh thats who notmyname is..16:14
TravTeverybody wave "hi!"16:14
TravT:D16:15
TravTso, back to the flavor bp16:15
TravTsjmc7: i do want to see this in16:15
TravTjust hard to say it is high16:15
TravTbut i'd be fine with medium16:15
*** GB21 has joined #openstack-searchlight16:15
TravTeverybody is right on cue today16:16
sjmc7more coffee!16:16
sjmc7yeah, it’s not crucial, it’s a nice to have16:16
TravTit is one of those things that really puts the polish on search giving you something you simply can't get with the regular APIs (I think)16:17
TravTok, so https://blueprints.launchpad.net/searchlight/+spec/index-management-api16:18
*** bpokorny_ has joined #openstack-searchlight16:19
*** bpokorny has quit IRC16:19
sjmc7mmmm… is this common?16:19
sjmc7a number of services have command line tools for initial setup kind of things16:19
TravTindex management api?16:19
TravTwell, here's what I'm thinking16:20
TravTactually, let me start with saying I would put this at low and not a mitaka iteam16:20
TravTitem16:20
sjmc7ok. i see the value, but i think it’s a pretty hefty chunk of work16:21
TravThow about I leave undefined, but target for next release16:21
TravT?16:21
lakshmiS_that makes more sense16:21
sjmc7i think we can certainly discuss it this cycle16:22
lakshmiS_and we can change it back if we get a strong use case from UI/users16:22
TravTOk.16:22
TravTok, the only other BP worth discussing today is: https://blueprints.launchpad.net/searchlight/+spec/keystone-projects-plugin16:23
TravTdavid-lyle: ^16:23
sjmc7i can’t see keystone ever sending notifications16:24
sjmc7which makes it hard to index projects16:24
david-lylesjmc7: yeah notifications will be hard16:24
david-lyleit would have to be a periodic resync16:24
TravTwe have same problem with nova flavors, i think.16:24
david-lyleif at all16:24
TravTand probably other entities.16:24
sjmc7periodic resync wouldn’t be hard to do; if that’s valuable we could certainly do it16:25
TravTyeah, so probably a BP on that concept should be registered16:25
TravTas dependent on https://blueprints.launchpad.net/searchlight/+spec/zero-downtime-reindexing16:25
nikhilwould we be indexing tokens too!? My guess, no.16:26
lakshmiS_that would be fun16:26
nikhilha16:26
TravTindexing tokens...16:26
david-lyleno16:26
sjmc7hahaha, no.16:26
david-lyleno tokens16:26
TravTof course we will!16:26
nikhilit could be valuable for bookkeeping admin only16:26
TravTjust say yes!16:27
nikhilbut that may not be quite complaint16:27
david-lyleno16:27
TravTdavid-lyle is no fun.16:27
nikhilI am just kidding with a serious face16:27
TravT;-P16:27
nikhilirc is fun! :D16:27
sjmc7i can imagine the conversation with our security guys16:27
TravTlol16:27
TravTwe could also forward the tokens out to zaqar16:27
* nikhil successfully lightens the mood even more evil :D16:27
sjmc7oo!16:28
david-lyleso with fernet, there are no tokens to index, so success?16:28
nikhilTravT: oh yeah :P16:28
sjmc7fernet is magic!16:28
TravTmaybe we could index the fernet keys and forward notifications out when they change16:28
david-lylewhere are we?16:29
* TravT looks behind him and sees the security police running towards him16:29
TravT#openstack-searchlight16:29
TravTumm, actually we are through the list16:30
TravTof setting initial priority16:30
TravTwe didn't really talk about what series everything should be targeted at16:30
TravTbut let's touch base on that later16:30
david-lyleserious note on the keystone projects plugin16:30
lakshmiS_yeah16:31
david-lyleit's blocked until that functionality actually exists in keystone16:31
david-lylein v316:31
TravTor until we do periodic re-sync16:31
david-lyleno, there's no pagination in keystone on projects16:31
david-lylecan't get a list yet16:31
david-lyleonly first API_RESULT_LIMIT16:32
david-lyleso ~50016:32
TravTi guess we could develop an algorithm to fish out all the results.16:32
david-lylethen you're dead in the water16:32
david-lyleno, we need the pagination of projects, then we could fish other items out16:32
sjmc7who has more than 500 projects?16:32
david-lylesjmc7: O_o16:32
lakshmiS_how about changing the limit in config for once16:33
david-lyleyou're public cloud is not fully dead yet16:33
david-lyle*your16:33
sjmc7it’s just sleeping!16:33
sjmc7it’s pinin’ for the fjords!16:33
david-lyleit's resting comfortably16:33
TravTok, i just added notes on that to BP16:33
TravTand changed implementation to "Blocked"16:33
david-lylethe breakthrough was keystone would be willing to consider pagination on projects16:34
david-lyleat the summit16:34
sjmc7that was around the same time they were talking about doing away with domain scoped tokens16:34
TravTso, what was the end result of both those conversations16:34
david-lylewell killing domain scoped tokens is a weekly waffle16:34
TravTthey both affect us16:34
david-lylehorizon will go forward with domain scoped token support16:35
*** GB21 has quit IRC16:35
david-lyleas it's part of the v3 API, it's not going away16:35
david-lyleeven though it will look different under the covers16:35
david-lylefor project pagination, our usecase was finally understood, and the possibility opened up16:36
david-lylebut would still need a spec and approval from keystone on adding pagination for projects16:36
TravTlikelihood for it to happen in Mitaka?16:36
david-lyledepends how active someone is doing the work16:36
TravTDo we need a spec in searchlight to deal with domains and HMT projects?16:37
david-lyleI'd sign up, but that would end in no real action16:37
david-lyleTravT: I don't think so16:37
*** GB21 has joined #openstack-searchlight16:37
david-lylenot sure what you'd add16:37
TravTme neither16:37
david-lyledomains won't have anything other than projects and users16:37
david-lylenothing from other services16:38
david-lylewell depending on the HMT result I guess16:38
david-lylewith HMT, I think project id's will still be enough16:39
TravTwell, that's good to know.16:39
david-lylenot sure we want to try and unwind the permissions nightmare of looking down the tree16:39
TravTat least nothing for mitaka16:39
david-lyleI don't think any service quite has that worked out yet16:39
david-lyleyeah maybe in N we revisit16:40
TravTok, then i think for today we can stop16:40
sjmc7whoa, that was a long session16:41
TravTyeah16:41
lakshmiS_later...16:41
TravTmaybe i'll just point our IRC meeting on thursday to this log.16:41
TravTprobably for thursday we'll just have open discussion on current spec reviews16:42
*** lakshmiS_ has quit IRC16:42
TravTallright, thanks guys16:42
*** yingjun has joined #openstack-searchlight17:06
*** yingjun has quit IRC17:10
*** GB21 has quit IRC17:24
*** bpokorny_ has quit IRC18:32
*** bpokorny has joined #openstack-searchlight18:52
*** bpokorny has quit IRC18:59
*** bpokorny has joined #openstack-searchlight19:01
*** yingjun has joined #openstack-searchlight19:08
*** yingjun has quit IRC19:13
*** bpokorny has quit IRC19:19
*** bpokorny has joined #openstack-searchlight19:19
*** bpokorny has quit IRC19:22
*** bpokorny has joined #openstack-searchlight19:22
*** ekarlso has joined #openstack-searchlight19:24
*** bpokorny has quit IRC19:28
*** bpokorny has joined #openstack-searchlight19:29
openstackgerritSteve McLellan proposed openstack/searchlight: Fix doc_count for nested fields  https://review.openstack.org/23604320:21
*** yingjun has joined #openstack-searchlight21:02
*** yingjun has quit IRC21:07
openstackgerritSteve McLellan proposed openstack/searchlight: Restructure index and notification classes  https://review.openstack.org/24598122:08
sjmc7i think i missed a conversation about having a python client for SL. if it’s in the searchlight repo, it won’t be possible to package it separately22:10
*** akanksha_ has quit IRC22:10
*** akanksha_ has joined #openstack-searchlight22:11
TravTsjmc7: i do agree that this should be a separate repo.  We'll have to create a new project like all the others22:29
david-lylewhy not openstackclient?22:36
david-lylestill a separate repo I guess to function as openstackclient plugin22:39
david-lylehttp://docs.openstack.org/developer/python-openstackclient/plugins.html22:39
TravTdavid-lyle: it is being proposed as a plugin to openstack client22:40
TravThttps://blueprints.launchpad.net/searchlight/+spec/openstack-client-search-initial-plugin22:40
TravTmaybe we need to ask the openstack sdk folks22:40
sjmc7it’ll be tough to use if it’s in the server code22:40
TravTyeah, might defeat the purpose22:41
TravTsjmc7: maybe you could do some more project config magic22:43
TravTand get a repo going for it22:43
sjmc7i do love me some infra22:43
TravTleave a comment on the patch...22:44
sjmc7ok. we’ll have to be prepared to do the maintenance on it22:44
TravTguess that goes with the territory.22:45
sjmc7yeah. i’ve been doing everythingh with bash aliases :)22:46
TravTi think we need to look at the commands though in the BP...22:46
TravTwould like to figure out how to make the commands easy22:47
TravTi saw in the glance room that after 11 months, glance now supports some limited updated_at and created_at comparison operators.22:48
TravTbut they are still nowhere near as powerful as ES native.22:49
TravTbbiab22:50
david-lyleTravT: I don't think it should be in the server code repo22:55
sjmc7no. i’ll get another repo created22:55
*** yingjun has joined #openstack-searchlight23:04
*** yingjun has quit IRC23:11
*** sigmavirus24 is now known as sigmavirus24_awa23:20
sjmc7TravT - do we have a stable-main group in gerrit? the ACLs need updating23:32
sjmc7err, stable-maint23:32
*** yingjun has joined #openstack-searchlight23:32
*** yingjun_ has joined #openstack-searchlight23:33
*** yingjun has quit IRC23:33
*** yingjun_ has quit IRC23:38
TravTsjmc7: no we don't23:56
sjmc7good, that simplifies things :)23:57
TravTat some point, we should have it for stable branch23:57
TravTbut i'm not sure we are there yet.23:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!