Friday, 2014-03-21

*** markmcclain has joined #openstack-oslo00:21
*** rpodolyaka1 has joined #openstack-oslo00:23
*** markmcclain1 has joined #openstack-oslo00:24
*** markmcclain has quit IRC00:26
*** rpodolyaka1 has quit IRC00:27
*** banix has quit IRC00:28
*** gcb has joined #openstack-oslo01:02
*** harlowja_at_home has quit IRC01:19
*** markmcclain1 has quit IRC01:19
*** rpodolyaka1 has joined #openstack-oslo01:23
*** rpodolyaka1 has quit IRC01:28
*** banix has joined #openstack-oslo01:31
openstackgerritChangBo Guo(gcb) proposed a change to openstack/oslo.messaging: Refactor AMQP message broker selection  https://review.openstack.org/8118301:44
openstackgerritChangBo Guo(gcb) proposed a change to openstack/oslo.messaging: Select AMQP message broker at random  https://review.openstack.org/8196201:56
*** mriedem has quit IRC02:00
*** mriedem has joined #openstack-oslo02:13
*** rpodolyaka1 has joined #openstack-oslo02:24
*** rpodolyaka1 has quit IRC02:28
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Add a timeout object that can be interrupted  https://review.openstack.org/8197102:51
*** mriedem has left #openstack-oslo03:09
*** mriedem has quit IRC03:10
*** rpodolyaka1 has joined #openstack-oslo03:25
*** rpodolyaka1 has quit IRC03:29
*** banix has quit IRC03:33
*** gcb has quit IRC03:37
*** gcb has joined #openstack-oslo03:41
*** zhiyan_ is now known as zhiyan03:50
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Add a timeout object that can be interrupted  https://review.openstack.org/8197104:04
*** rpodolyaka1 has joined #openstack-oslo04:26
*** rpodolyaka1 has quit IRC04:30
*** gcb_ has joined #openstack-oslo04:32
*** gcb has quit IRC04:34
*** gcb_ has quit IRC04:35
*** gcb_ has joined #openstack-oslo04:38
*** morganfainberg is now known as morganfainberg_Z04:39
*** morganfainberg_Z is now known as morganfainberg04:44
*** arnaud has joined #openstack-oslo04:53
*** arnaud__ has quit IRC04:53
openstackgerritYuriy Taraday proposed a change to openstack/oslo.rootwrap: Add an option to run rootwrap as a daemon  https://review.openstack.org/8179805:01
*** rpodolyaka1 has joined #openstack-oslo05:25
*** arnaud has quit IRC05:25
*** arnaud has joined #openstack-oslo05:26
*** rpodolyaka1 has quit IRC05:30
*** rpodolyaka1 has joined #openstack-oslo05:31
*** norman has joined #openstack-oslo06:36
*** norman has quit IRC06:36
*** norman has joined #openstack-oslo06:37
*** rpodolyaka1 has quit IRC06:46
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: Iteration over links in flow interface  https://review.openstack.org/8094207:11
*** arnaud has quit IRC07:40
*** norman has quit IRC08:06
*** flaper87|afk is now known as flaper8708:07
*** rpodolyaka1 has joined #openstack-oslo08:14
*** I159_ has joined #openstack-oslo08:17
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: Drop obsolete test_unordered_flow  https://review.openstack.org/8202408:18
*** rpodolyaka1 has quit IRC08:18
*** gcb_ has quit IRC08:52
*** ihrachys is now known as ihrachys|wfh|tax08:55
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: Drop indexing operator from linear flow  https://review.openstack.org/8203409:12
*** gcb has joined #openstack-oslo09:14
openstackgerritChangBo Guo(gcb) proposed a change to openstack/oslo-incubator: Add module integrity check in update.py  https://review.openstack.org/7690109:25
*** morganfainberg is now known as morganfainberg_Z09:48
*** rpodolyaka1 has joined #openstack-oslo10:15
*** rpodolyaka1 has quit IRC10:19
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: Linear flow: mark links and rework unit tests  https://review.openstack.org/8205010:33
*** rpodolyaka1 has joined #openstack-oslo11:16
*** rpodolyaka1 has quit IRC11:20
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: Unit tests for unordered flow  https://review.openstack.org/8207211:29
*** banix has joined #openstack-oslo12:15
*** rpodolyaka1 has joined #openstack-oslo12:16
*** rpodolyaka1 has quit IRC12:20
*** mriedem has joined #openstack-oslo12:23
openstackgerritYuriy Taraday proposed a change to openstack/oslo.rootwrap: Add an option to run rootwrap as a daemon  https://review.openstack.org/8179812:38
*** russellb is now known as rustlebee12:40
*** dims has quit IRC12:41
*** dims has joined #openstack-oslo12:48
*** ihrachys|wfh|tax is now known as ihrachys|wfh12:52
*** banix has quit IRC13:00
*** rpodolyaka1 has joined #openstack-oslo13:17
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: Rework graph flow unit tests  https://review.openstack.org/8208613:18
*** rpodolyaka1 has quit IRC13:20
*** bknudson has joined #openstack-oslo13:25
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: (WIP) Flattening improvements  https://review.openstack.org/8209113:29
*** hartsocks is now known as hartbot13:31
*** markmcclain has joined #openstack-oslo13:59
*** banix has joined #openstack-oslo14:01
*** markmcclain1 has joined #openstack-oslo14:02
*** markmcclain has quit IRC14:03
*** markmcclain1 has quit IRC14:07
*** markmcclain has joined #openstack-oslo14:10
ihrachys|wfhgcb: ping re random choice of broker in amqp14:12
*** rpodolyaka1 has joined #openstack-oslo14:18
*** rpodolyaka1 has quit IRC14:22
*** markmcclain has quit IRC14:25
*** dhellmann_ is now known as dhellmann14:33
dhellmannbnemec: +2a on https://review.openstack.org/#/c/78628/ (I was off yesterday)14:40
bnemecdhellmann: Thanks!14:41
*** bnemec is now known as beekneemech14:41
ihrachys|wfhdhellmann: have you seen that test_executor failure?14:42
dhellmannihrachys|wfh: I did see your message. Looking at the test report doesn't tell me much. Are we seeing that failure on other patches?14:43
ihrachys|wfhdhellmann: not that I aware of it14:44
ihrachys|wfhdhellmann: I've seen this once only in your review.14:44
ihrachys|wfhdhellmann: but it looks that assumptions made in this unit test are not correct (having only single greenthread to switch to on .sleep(0))14:45
dhellmannihrachys|wfh: is there some way for me to get to the patch in gerrit from the link you posted to the test results?14:45
ihrachys|wfhdhellmann: https://review.openstack.org/#/c/77273/14:45
ihrachys|wfhit's your patch :)14:45
ihrachys|wfhI just base my work on this14:45
dhellmannihrachys|wfh: you might be right about the bad test assumptions14:46
ihrachys|wfhdhellmann: ...but since it's not reproducible, it's hard to be sure14:49
dhellmannit looks like cinder is giving up on oslo.messaging for this cycle? https://review.openstack.org/#/c/81870/14:49
ihrachys|wfh:(14:50
*** zhiyan is now known as zhiyan_14:52
ihrachys|wfhdhellmann: it's not clear where this unexpected greenthread came from though.14:53
dhellmannihrachys|wfh: could you open a bug with the details you have? I have another issue I'm tracking atm, but we should start collecting data and rechecks for this14:55
ihrachys|wfhdhellmann: ok14:57
ihrachys|wfhdhellmann: ha! there's one https://bugs.launchpad.net/oslo.messaging/+bug/128270614:59
openstackgerritMonty Taylor proposed a change to openstack/oslo.rootwrap: Don't use system pip things in tox  https://review.openstack.org/8211714:59
openstackgerritDoug Hellmann proposed a change to openstack/oslo.rootwrap: Don't use system pip things in tox  https://review.openstack.org/8211715:03
ihrachys|wfhdhellmann: is there a way to wait for all greenthreads to complete? if so, we could do it prior to running the test...15:03
dhellmannihrachys|wfh: I don't think we want tests blocking like that. What is the test trying to verify? That exactly one thread is created, or that one more than used to be there is created? Or that a thread is used? Can we rewrite the test to check that condition in a different way?15:04
openstackgerritMonty Taylor proposed a change to openstack/oslo.rootwrap: Don't use system pip things in tox  https://review.openstack.org/8211715:06
ihrachys|wfhdhellmann: i think we try to check that greenthread is actually scheduled to spawn, and it completed.15:06
dhellmannihrachys|wfh: that seems like something we could do with a mock, no?15:09
ihrachys|wfhdhellmann: seems yes; ok, I'll try the approach now.15:12
dhellmannihrachys|wfh: thanks!15:12
*** rpodolyaka1 has joined #openstack-oslo15:18
*** rpodolyaka1 has quit IRC15:20
*** hartbot has quit IRC15:48
*** hartsocks has joined #openstack-oslo15:51
*** hartsocks has quit IRC15:53
*** hartsocks has joined #openstack-oslo15:53
*** arnaud__ has joined #openstack-oslo15:57
*** arnaud__ has quit IRC16:04
*** arnaud has joined #openstack-oslo16:04
*** bogdando has quit IRC16:07
*** markmcclain has joined #openstack-oslo16:10
*** gcb has quit IRC16:11
*** markmcclain has quit IRC16:15
*** rpodolyaka1 has joined #openstack-oslo16:19
*** rpodolyaka1 has quit IRC16:23
*** gcb has joined #openstack-oslo16:24
bknudsonis there a no-op rpc_backend?16:32
*** anteaya is now known as cyan16:36
openstackgerritYuriy Taraday proposed a change to openstack/oslo.rootwrap: Add an option to run rootwrap as a daemon  https://review.openstack.org/8179816:36
*** cyan is now known as Guest2006416:36
*** Guest20064 is now known as anteaya-who-was-16:37
*** anteaya-who-was- is now known as anteaya16:37
dhellmannbknudson: there's a fake driver in oslo.messaging, if that's what you mean16:53
bknudsondhellmann: that might be what I'm looking for. I'll give it a try16:56
*** I159_ has quit IRC17:00
ihrachys|wfhdhellmann: on second thought, it does not look like mocking eventlet is enough. The executor test requires that scheduled thread is actually run, and all eventlet mechanics is done (like calling .__exit__). So it's not just about capturing arguments of eventlet.spawn()17:01
ttxdhellmann: would you agree with my comment on https://review.openstack.org/#/c/72093/ ? Just making sure i'm not crazy before uploading a "fix" for it17:02
dhellmannttx: looking17:02
ttxtrying to get it all in for depfreeze17:05
ttxbut Dirk is a bit slow on patch updates right now17:05
dhellmannttx: yes, you're right, that's the wrong expression17:16
ttxok pushing fix then17:18
openstackgerritThierry Carrez proposed a change to openstack/oslo.rootwrap: Avoid matching ip -s netns exec in IpFilter  https://review.openstack.org/7209317:18
ttxthat one would have introduced a rather subtle flaw in that filter17:19
*** rpodolyaka1 has joined #openstack-oslo17:19
ttxdhellmann: feel free to +2/APRV it later in the day if tests pass -- i'm about to call it a week17:20
dhellmannttx: I'll keep an eye on it; have a good weekend!17:20
ttxWill tag oslo.rootwrap on Monday if hell didn't freeze over the weekend17:20
* dhellmann crosses his fingers for a heat-wave17:20
ttxWe had 75°F yesterday.17:21
ttx(France, not Florida)17:21
dhellmannjust a few degrees warmer than here17:23
ttxand now I see you were not speaking literally17:24
*** rpodolyaka1 has quit IRC17:24
*** dshulyak has quit IRC17:25
beekneemechdhellmann: Do you have any thoughts on https://review.openstack.org/#/c/81412/117:42
beekneemechI'm not really sure what the current best practices for oslo.config are.17:43
* beekneemech should probably change that17:43
*** jroll is now known as jimmyjohns17:45
openstackgerritIhar Hrachyshka proposed a change to openstack/oslo.messaging: Fixed inconsistent EventletContextManagerSpawnTest failures  https://review.openstack.org/8215118:01
ihrachys|wfhdhellmann: I've applied a bit different approach fixing the executor test failure: https://review.openstack.org/#/c/82151/18:07
openstackgerritIhar Hrachyshka proposed a change to openstack/oslo.messaging: Fixed inconsistent EventletContextManagerSpawnTest failures  https://review.openstack.org/8215118:09
*** morganfainberg_Z is now known as morganfainberg18:11
*** rpodolyaka1 has joined #openstack-oslo18:20
*** rpodolyaka1 has quit IRC18:24
*** beav has joined #openstack-oslo18:26
dhellmannbeekneemech: looking18:27
dhellmannbeekneemech: it seems like those options should be registered in one group (not the default) and that the memorycache module should "own" the name of that group, not keystone client -- do you know why keystoneclient is registering them itself?18:29
beekneemechdhellmann: No idea.  Maybe we should deprecate the keystoneclient one?18:31
dhellmannbeekneemech: I suspect that's part of why morganfainberg has been involved in the cache work in oslo18:31
bknudsonkeystone does caching of results... keystoneclient caches tokens and revocation list18:36
bknudsonauth_token middleware does caching of tokens and results18:37
bknudsontokens and revocation list18:37
dhellmannbknudson: the question is why the middlware registers a separate config option for that caching; is it not using the oslo module?18:44
bknudsondhellmann: memcached_servers option?18:47
dhellmannbknudson: yes, see https://review.openstack.org/#/c/81412/1 and https://launchpad.net/bugs/126214818:48
dhellmannbknudson: I'm trying to understand the background, so I can understand the proposed fix and whether it's good long-term18:48
*** boris-42 is now known as boris-the-blade-18:49
*** boris-the-blade- is now known as boris-the-blade18:50
bknudsondhellmann: doesn't look like python-keystoneclient needs it to me, since memorycache does the same thing.18:50
dhellmannbknudson: is this just a matter of a module moving into oslo, and not yet being removed from its original location?18:50
bknudsonall that auth_token does with it is pass it on to memorycache.get_client(memcache_servers)... so if it wasn't set in auth_token then it'll use the oslo config18:50
dhellmannwe wouldn't want the middleware to depend on that config option being registered by another module, but we don't want it registered twice with different settings either18:51
dhellmannaha, interesting18:51
dhellmannbknudson: could you leave that comment on the review?18:51
*** rpodolyaka1 has joined #openstack-oslo19:08
*** hartsocks has left #openstack-oslo19:30
morganfainbergdhellmann, correct this is why i am trying to work on that.19:42
*** rpodolyaka1 has quit IRC19:42
morganfainbergdhellmann, almost have all your comments on my patchset for oslo.cache addressed, but there has been enough restructure i need to test it19:42
morganfainberga lot before pushing up changes.19:42
dhellmannmorganfainberg: ok, can you provide any guidance on how to fix https://bugs.launchpad.net/nova/+bug/1262148 in the short term without major changes like moving options around into different groups?19:43
morganfainbergdhellmann, looking now19:44
dhellmannmorganfainberg: see https://review.openstack.org/#/c/81412/ too19:44
morganfainbergdhellmann, oooh. icky19:45
dhellmannmorganfainberg: yeah, we probably shouldn't have libraries registering options in the default group19:45
morganfainbergdhellmann, ++ i tossed a summit session proposal up on that :P19:46
dhellmannnice19:46
morganfainbergdhellmann, i think all oslo.* options should be namespaced incubator or library19:46
morganfainbergdhellmann, the [DEFAULT] group probably should only be used for the application itself and even then... limited19:47
dhellmannright19:47
morganfainbergeven if the summit session is rejected, i plan on cornering people in the dev lounge about fixing this in juno19:47
dhellmannalthough I don't know if we wan an "oslo.messaging" section or just "messaging" or whatever -- but each lib should pick a namespace and the incubator modules should be using them, too19:47
morganfainbergor working on fixing it (more appropriately)19:47
dhellmannwe should talk about adding that to the list of graduation steps for oslo libs19:48
morganfainbergdhellmann, i would like to see an [oslo.<namespace>] magic in oslo.config19:48
morganfainbergnot sure how easy that would be due to the way config_parser works19:48
dhellmannwhy do we need magic?19:48
morganfainbergiirc . is special in config parser19:48
dhellmannoh, just for the dot19:48
morganfainbergyeah19:49
dhellmannwell, why do we need the "oslo." part?19:49
morganfainbergwe don't but it means no one would conflict with the common lib namespace19:49
dhellmanntrue19:49
dhellmanncould just use oslo_ as a prefix19:49
morganfainbergif someone has mongo db stuff and wants to call their section [database] they would have zero impact to oslo.db19:50
morganfainbergdhellmann, true. a good alternative19:50
morganfainbergdhellmann, and probably requires no magic :)19:50
dhellmannI'm not sure we need a prefix, but I would rather pick one that doesn't need magic :-)19:50
dhellmannhehe19:50
morganfainbergdhellmann, i would advocate a prefix is just to clearly delineate where the options are defined and leaving the rest of the namespace wide open19:51
morganfainberg[messaging] for example could be used in a lot of cases19:51
morganfainbergi'm 100% for making namespaced options required for graduation from incubation19:51
morganfainbergeven w/o a prefix :)19:52
dhellmannok, I could be convinced on the prefix part I think, although it means changes to existing libs19:52
morganfainbergdhellmann, the deprecated option stuff is pretty good last i looked. but it is shuffling a lot of code19:52
dhellmannyeah19:53
morganfainbergi think the "correct" approach is make all new libs conform, and slate fixes for current ones as we can manage it19:53
dhellmannmakes sense19:53
morganfainbergand encourage new incubated code to pre-emptively namespace19:53
morganfainberg"don't just dump that option in default please"19:54
morganfainbergok back on topic. looking at the bug / reviews and trying to see what we can do19:54
*** rpodolyaka1 has joined #openstack-oslo19:58
*** rpodolyaka1 has quit IRC20:07
*** rpodolyaka1 has joined #openstack-oslo20:10
*** rpodolyaka1 has quit IRC20:14
morganfainbergdhellmann, i think the only real answer here is to either make auth_token check two locations (not register the deprecated option location) or fix the group in the incubated code.20:17
morganfainbergdhellmann, looking over all the various options and testing some thing, i don't see a good way to unwind this.20:18
morganfainbergdhellmann, likely the least resitance will be to make auth_token say "is [auth_token] memcache_servers == default ? if so, check [DEFAULT] then fallback. but it's ugly20:19
dhellmannmorganfainberg: would there ever be a need to configure that option with 2 different values?20:20
morganfainbergdhellmann, this also implies we should have a way to see if a value is the default from the CONF object itself.20:20
morganfainbergdhellmann, hm. actually yes i could see that being desired, multiple memcache farms20:20
dhellmannI don't know if that's possible, and if it is I'm not sure that's a good way to detect an "unset" value20:20
morganfainbergdhellmann, this is the exact case why we need to namespace the options :P hm...20:21
*** openstackgerrit has quit IRC20:22
dhellmannmorganfainberg: what about bknudson's comment on https://review.openstack.org/#/c/81412/1/openstack/common/memorycache.py ?20:23
*** openstackgerrit has joined #openstack-oslo20:23
*** harlowja_still_a has joined #openstack-oslo20:23
morganfainbergif keystoneclient imported memory_cache just to ensure the option is registered would we have the same issue?20:23
bknudsonI can imagine you'd want a different memcache for auth_token vs whatever else might use memcache20:23
morganfainbergbknudson, ++20:24
morganfainbergbknudson, when did we deprecate the old option?20:24
dhellmannright, and that's part of what the new cache stuff is trying to support, right?20:24
* morganfainberg goes and checks20:24
morganfainbergdhellmann, exactly20:24
morganfainbergdhellmann, it's the whole reason to use a layer like dogpile w/ named cache regions20:24
bknudsonthe auth_token options are in [keystone_authtoken]20:24
dhellmannwere we supporting that before with this older cache code?20:24
morganfainbergdhellmann, don't think so20:25
bknudsonor you could specify them in your api-paste.ini20:25
morganfainbergbknudson, i think the conflict comes from the deprecated name part in our option20:25
morganfainbergbknudson, otherwise this has little impact20:25
bknudsonthat's memcache_servers20:25
morganfainbergbknudson, yeah20:26
bknudsonCONF.register_opts(opts, group='keystone_authtoken')20:26
bknudsondeprecated_name='memcache_servers'20:27
morganfainbergwait a second.20:27
bknudsonthe bug 1262148 seems strange... it says auth_token defines memcached_servers in default and not in keystone_authtoken20:30
morganfainbergbknudson, ok this is rooted from a bug in the generator code20:30
morganfainbergbknudson, nothing to do with either us or the incubated code20:30
morganfainbergwe're just symptoms here20:30
morganfainberghttps://review.openstack.org/#/c/79738/2/openstack/common/config/generator.py20:30
morganfainbergaparantly identical options don't appear in separate groups20:31
morganfainberghttps://bugs.launchpad.net/oslo/+bug/128858620:31
morganfainbergbut our option is actually largely different because helptext is different20:31
bknudsonit would be interesting to see the result of fixing that bug on the other bug20:31
morganfainbergthis seems like faulty code20:34
morganfainbergwhy does an option need a group?20:35
morganfainbergit's to help smush out multiple definitions in the same group...but there are cases where we don't want a group on an option20:36
morganfainbergthe generator assumes all options must be in a group it looks like.20:36
*** rpodolyaka1 has joined #openstack-oslo20:38
*** rpodolyaka1 has quit IRC20:44
*** banix has quit IRC20:50
*** rpodolyaka1 has joined #openstack-oslo21:40
*** rpodolyaka1 has quit IRC21:45
*** bknudson has quit IRC22:09
*** dhellmann is now known as dhellmann_22:21
*** harlowja_still_a has quit IRC22:33
openstackgerritJenkins proposed a change to openstack/oslo-incubator: Updated from global requirements  https://review.openstack.org/8223622:33
*** rpodolyaka1 has joined #openstack-oslo22:41
*** rpodolyaka1 has quit IRC22:47
*** dims has quit IRC22:59
*** dims has joined #openstack-oslo23:14
*** mriedem has left #openstack-oslo23:22
*** mriedem has quit IRC23:22
*** rpodolyaka1 has joined #openstack-oslo23:44
*** rpodolyaka1 has quit IRC23:48
*** yamahata has quit IRC23:55
*** yamahata has joined #openstack-oslo23:55

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