Thursday, 2015-10-08

*** openstackgerrit has quit IRC00:01
*** openstackgerrit has joined #openstack-searchlight00:02
*** itisha has quit IRC02:51
*** nikhil has quit IRC04:32
*** nikhil has joined #openstack-searchlight04:32
*** GB21 has joined #openstack-searchlight05:02
*** GB21 has quit IRC05:35
*** GB21 has joined #openstack-searchlight05:50
*** GB21 has quit IRC06:21
*** nikhil has quit IRC06:56
*** nikhil has joined #openstack-searchlight06:56
*** akanksha_ has quit IRC08:38
*** GB21 has joined #openstack-searchlight10:09
*** GB21 has quit IRC11:57
*** GB21 has joined #openstack-searchlight12:36
*** sigmavirus24_awa is now known as sigmavirus2413:50
*** lakshmiS has joined #openstack-searchlight14:05
*** lakshmiS_ has joined #openstack-searchlight14:27
*** lakshmiS has quit IRC14:31
*** lakshmiS_ has quit IRC14:57
*** lakshmiS has joined #openstack-searchlight14:58
TravTCourtesy Searchlight meeting reminder in #openstack-meeting-4: lakshmiS, mclaren, nikhil_k, rosmaita, sigmavirus24, TravT, krykowski, david-lyle, wokuma, kragniz, sjmc7, ekarlso, abhijeetm, itisha15:00
nikhilthanks!15:01
*** david-ly_ has joined #openstack-searchlight15:22
*** david-lyle has quit IRC15:23
*** david-ly_ is now known as david-lyle15:24
nikhilTravT: hi, is it okay to term searchlight as "official" openstack project? I'm a bit uncertain on that terminology atm..16:11
TravTyes, it is an official project.16:12
nikhilsjmc7: lakshmiS anyone ^ ?16:12
nikhilthanks!16:12
TravTwas voted in by the TC16:12
nikhilTravT: I always get confused when they change some details16:14
TravTyeah, it is a project, and then they have all these tags16:14
nikhil:)16:15
*** lakshmiS has quit IRC17:23
*** itisha has joined #openstack-searchlight18:00
itishahey guys, I don't think I completely got what sjmc7 was trying to say on the review https://review.openstack.org/23220019:43
sjmc7hi itisha. i checked out the patch, but it doesn't seem to have any effect - that code doesn't get executed at all when i start the api19:44
sjmc7i may have something configured wrong19:44
nikhilsjmc7: weird, I thought the configs were static content19:45
nikhilthat you generate using tox -e genconfig (like oslo command)19:45
sjmc7i think that generates an example config file?19:45
nikhilsjmc7: yes, tox generates an example config file and I have a notion that operators will use that as a reference for creating their own19:49
sjmc7ok19:49
sjmc7but the codebase doesn't support the options19:49
nikhilsjmc7: in fact, in glance we keep the same in tree to support such cases. But enforcing dynamic creation is better consistency wise19:49
nikhilsjmc7: I see19:49
nikhilitisha: are you getting it?19:50
sjmc7most projects no longer keep it in tree because it gets out of date19:50
nikhilI don't want to move ahead of you and ask questions taht you don't get, itisha.19:50
nikhilsjmc7: true19:50
itishai'm not sure i get what you mean by keeping it in tree?19:50
sjmc7glance has a sample config file checked in to git19:51
itishaoh ok....19:51
*** akanksha_ has joined #openstack-searchlight19:52
itishaok, i think i'm on the same page till now19:52
nikhilitisha: do you know what to do next?19:57
nikhilitisha: if not, check the code and see which options are actually being used and which aren't. You will then need to modify some of the groups of these options so that code uses them. questions?20:00
itishanikhil: if we create separate config files for api and listener as sjmc7 suggested, that would mean there would be no default at all right (ie no common configs)?20:01
nikhilitisha: sorry, I need to go to a meeting. bbiab20:02
sjmc7itisha no - it would mean there'd be a common config file, plus role-specific ones20:03
sjmc7so searchlight-api.conf and searchlight.conf20:03
itishaoh ok....20:03
sjmc7i'm only suggesting that because i know oslo.config supports chaining config files like that, and i don't know if it supports overriding options in the way you're trying to do it20:03
TravThmmm...20:05
TravTitisha, would you be comfortable asking the oslo folks?20:05
TravT#openstack-oslo20:05
itishaTravT, umm, ok, i can check with them....20:06
TravTmaybe just say: we have two services that currently use the same config file. we want to, however, have some settings separated by service such as the log file.  what is the best way to do that.  can we do that within the same config file or do we need role specific files?20:08
itishaok, cool, i'll check with them20:09
TravTtry calling out these irc names20:13
TravTdims bknudson20:13
TravTif there isn't a response on irc, then it may take a mailing list question20:14
itishaTravT: hmm, ok, i've used the irc names, i'll wait for a while, and if there is no response, i'll then ask it on the mailing list20:19
TravTsure...20:19
TravTthis is kind of a crazy time (end of release and summit coming up), so people are often kind of scrambling20:20
itishaohh, alright, totally understandable :)20:20
sjmc7borland left me in the lurch a bit, i am not a happy bunny20:20
sjmc7nikhil - does glance override log_file ? it has multiple components20:28
sjmc7how does glance-reg and glance-api separate them?20:28
nikhilsjmc7: they have separate file for both services20:28
sjmc7totally separate?20:28
nikhilyes20:29
sjmc7or share a common file?20:29
sjmc7i think nova does shared + specific ones20:29
nikhilas they are often installed on diff nodes20:29
sjmc7although.. i can't find evidence of that. did i make it up?20:29
sjmc7that's disappointing20:30
nikhilhttps://github.com/openstack/glance/blob/master/etc/glance-registry.conf20:31
nikhilhttps://github.com/openstack/glance/blob/master/etc/glance-api.conf20:32
nikhilsjmc7: are you talking about something else?20:32
sjmc7yeah.. hmm. maybe log_dir is the recommended way to do this?20:32
sjmc7yeah, i thought i'd seen chained config files20:32
sjmc7but now i think i'm going mad20:32
nikhil:)20:37
sjmc7perhaps log_dir is the right way to solve this particular issue20:37
* nikhil back20:49
nikhilitisha: let me know if you get stuck somewhere20:50
nikhilitisha: I'm just back from a meeting but have to send a few emails now.. so send me a ping20:50
itishanikhil: ok, sure, i'll do that20:52
*** ig0r_ has joined #openstack-searchlight20:58
*** ig0r_ has quit IRC21:03
*** ig0r_ has joined #openstack-searchlight21:04
*** GB21 has quit IRC21:10
*** ig0r_ has quit IRC21:10
sjmc7itisha, TravT - the workaround for this i think is to specify log_dir rather than log_file21:38
sjmc7i think it still makes sense to add [api] and [listener] sections, but they don't have to try to override the oslo logging stuff21:38
sjmc7looking at other services, it's quite common to have config for various components all in the same file21:39
TravTsjmc7: sounds like good info.  what code changes are needed?21:41
sjmc7none21:43
sjmc7log_dir is olso.config's answer to this21:43
*** sigmavirus24 is now known as sigmavirus24_awa21:43
sjmc7it uses the name of whatever's running __main__ to set the filename21:43
sjmc7documentation change only21:43
sjmc7then i think making the config alteration can wait until we have a definite need for it (e.g. an option that cannot be common)21:44
sjmc7so this is my bad, that BP was somewhat of a red herring21:45
TravTon an unrelated note, i just figured out how to handle delay on events for text query typing.21:45
sjmc7ah, splendid21:46

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