Tuesday, 2014-09-02

openstackgerritA change was merged to openstack/taskflow: Make version.py handle pbr not being installed  https://review.openstack.org/11819200:28
openstackgerritA change was merged to openstack/oslo.db: Use oslo.i18n  https://review.openstack.org/11725700:34
*** dims has joined #openstack-oslo00:47
*** yamahata has quit IRC00:55
*** ajo__ has quit IRC01:18
*** dims has quit IRC01:28
*** stevemar has joined #openstack-oslo01:53
*** yamahata has joined #openstack-oslo01:53
*** miqui has quit IRC01:57
*** alexpilotti has quit IRC01:57
*** amotoki has joined #openstack-oslo02:00
*** harlowja_at_home has joined #openstack-oslo02:09
*** harlowja_at_home has quit IRC02:14
*** takedakn has joined #openstack-oslo02:18
*** harlowja_at_home has joined #openstack-oslo02:46
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Remove the dependency on prettytable  https://review.openstack.org/11762902:49
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Add existing types to generated documentation  https://review.openstack.org/10693002:50
*** harlowja_at_home has quit IRC03:01
*** shakamunyi has joined #openstack-oslo03:15
*** shakamunyi has quit IRC03:20
*** harlowja_at_home has joined #openstack-oslo04:30
*** ildikov_ has quit IRC04:33
*** harlowja_at_home has quit IRC04:43
*** takedakn has quit IRC04:53
*** ildikov has joined #openstack-oslo05:25
openstackgerritOpenStack Proposal Bot proposed a change to openstack/oslo.i18n: Imported Translations from Transifex  https://review.openstack.org/11655306:05
openstackgerritOpenStack Proposal Bot proposed a change to openstack/oslo.db: Imported Translations from Transifex  https://review.openstack.org/11825806:05
*** k4n0 has joined #openstack-oslo06:06
*** flaper87|afk is now known as flaper8706:26
*** YorikSar_ has quit IRC06:28
*** ildikov has quit IRC06:54
*** openstackgerrit has quit IRC07:02
*** ildikov has joined #openstack-oslo07:04
*** stevemar has quit IRC07:29
*** YorikSar has joined #openstack-oslo07:38
YorikSardhellmann: Hi. I could add oslo.concurrency to bug 1357582 but I can't change status to triaged and importance level.07:39
YorikSardhellmann: https://bugs.launchpad.net/oslo.concurrency/+bug/135758207:39
*** flaper87 is now known as flaper87|afk07:43
*** flaper87|afk is now known as flaper8707:48
*** noelbk has quit IRC07:53
*** dims has joined #openstack-oslo07:56
*** dims has quit IRC08:00
*** morganfainberg is now known as morganfainberg_Z08:12
*** pblaho has joined #openstack-oslo08:20
*** jaosorior has joined #openstack-oslo08:25
*** noelbk has joined #openstack-oslo08:29
*** flaper87 is now known as flaper87|afk08:37
*** ildikov_ has joined #openstack-oslo08:44
*** ildikov has quit IRC08:47
*** flaper87|afk is now known as flaper8708:50
*** dtantsur|afk is now known as dtantsur08:57
*** i159 has joined #openstack-oslo09:19
*** praneshp has quit IRC09:28
*** pblaho is now known as pblaho|afk10:06
*** pcm_ has joined #openstack-oslo10:31
*** yamahata has quit IRC10:36
*** alexpilotti has joined #openstack-oslo10:42
*** pcm_ has quit IRC10:44
*** dims has joined #openstack-oslo10:46
*** pcm_ has joined #openstack-oslo10:47
*** dims has quit IRC10:50
*** pblaho|afk is now known as pblaho10:54
dtantsurHi folks! Yesterday I encountered SyntaxErrors in site-packages/sphinx/apidoc.py on Py33: http://logs.openstack.org/78/113978/4/check/gate-oslo-incubator-python33/b466718/console.html11:13
dtantsurIs it a known bug? Should I recheck on it?11:14
*** pblaho is now known as pblaho|afk11:18
*** ihrachyshka has joined #openstack-oslo11:19
*** amotoki has quit IRC11:22
*** ihrachyshka has quit IRC11:25
*** vigneshvar has joined #openstack-oslo11:25
vigneshvarhi guys, a quick question. I have subscribed to a queue using rpc_getserver method and start call, i tried to stop and then start again. But now messages are not consumed11:27
*** AJaeger has joined #openstack-oslo11:27
vigneshvarwhat could be the issue11:27
*** pblaho|afk is now known as pblaho11:30
*** dims has joined #openstack-oslo11:42
*** k4n0 has quit IRC11:46
*** kgiusti has joined #openstack-oslo11:55
*** jaosorior has quit IRC12:02
dhellmanndtantsur: I saw something about a bad sphinx wheel being published, so that may have caused your problem. If rechecking doesn't fix it, you should ask in #openstack-infra to see if they can help track down the bad package.12:04
*** dims has quit IRC12:08
*** dims has joined #openstack-oslo12:08
AJaegerdims, oslo.log is available now - but does not pass gating. There're two patches for it that fail due to python26 check failing12:15
dtantsurdhellmann, thanks, will try12:23
*** amrith is now known as _amrith_12:28
dimsAJaeger: got a url?12:35
*** jeckersb_gone is now known as jeckersb12:55
AJaegerdims, I see your patch already, thanks!12:57
AJaegerdims, https://review.openstack.org/117610 and https://review.openstack.org/11794112:57
AJaegerboth should pass IMHO12:57
dimsAJaeger: found it12:57
*** gordc has joined #openstack-oslo12:58
dimsAJaeger: not sure what i did will work, just trying something to see if it will12:58
AJaegerdims, let's wait ;) As long as you're on it and aware of it, I'm happy! :)12:59
AJaegerdims, thanks!12:59
dims:)12:59
*** pblaho is now known as pblaho|afk13:00
*** tongli has joined #openstack-oslo13:00
dimsAJaeger: looks like it worked - https://jenkins03.openstack.org/job/gate-oslo.log-python26/2/console13:01
AJaegerdims, that single character change is all? Wow!13:02
AJaegerdims, let'S find some reviewers and get it in ;)13:02
dimsweird :)13:02
dimsAJaeger: rebased the other 2 on top of this one to see if they fare better13:03
AJaegerdims,good idea - thanks!13:04
AJaegerhttps://jenkins03.openstack.org/job/gate-oslo.log-python26/3/console ;(13:04
*** ildikov_ has quit IRC13:04
dimsAJaeger: that global requirements did not fare well13:06
dimsthis seems to have passed - https://jenkins04.openstack.org/job/gate-oslo.log-python26/1/console13:06
AJaegerdims, but mine worked better ;)13:06
dimsy13:06
*** flaper87 is now known as flaper87|afk13:06
dimsk. i'll go chase other gremlins :)13:07
*** ildikov has joined #openstack-oslo13:07
AJaegerdims, thanks13:07
*** pblaho|afk is now known as pblaho13:10
*** Guest44661 is now known as hartsocks13:14
*** pblaho_ has joined #openstack-oslo13:15
*** pblaho has quit IRC13:16
*** jaosorior has joined #openstack-oslo13:17
*** jecarey_ has quit IRC13:21
*** pblaho_ has quit IRC13:22
*** zz_jgrimm is now known as jgrimm13:22
*** pblaho_ has joined #openstack-oslo13:22
*** bknudson has joined #openstack-oslo13:23
*** mriedem has joined #openstack-oslo13:35
viktorsdims: hi! Can you please review patch to incubator https://review.openstack.org/#/c/68963/ (Fix response_key parameter usage in BaseManager) ? Thanks!13:45
*** _amrith_ is now known as amrith13:49
dimsviktors: looks good13:54
viktorsdims: thank you!13:55
*** pblaho_ has quit IRC13:57
*** abhijeetm has joined #openstack-oslo13:58
*** zzzeek has joined #openstack-oslo13:59
*** stevemar has joined #openstack-oslo14:04
*** openstackgerrit has joined #openstack-oslo14:05
*** abhijeetm has quit IRC14:13
dhellmanndims, AJaeger : +2a on the testr fix for oslo.log14:28
dimsdhellmann: thanks!14:28
*** yamahata has joined #openstack-oslo14:31
*** vigneshvar has quit IRC14:37
*** ildikov_ has joined #openstack-oslo14:46
*** shakamunyi has joined #openstack-oslo14:47
*** jecarey has joined #openstack-oslo14:48
*** ildikov has quit IRC14:49
zzzeekhey dhellmann , does sep 4 feature freeze apply to what I’m trying to do with oslo.db testing15:02
*** mtanino has joined #openstack-oslo15:02
*** yamahata has quit IRC15:03
*** yamahata has joined #openstack-oslo15:03
*** shakamunyi has quit IRC15:07
*** yamahata has quit IRC15:11
*** shakamunyi has joined #openstack-oslo15:11
zhiyandhellmann: hi, do you have 2 mins? i have a interesting question on excutils.save_and_reraise_exception(), could you give me some input?15:14
*** markmcclain has joined #openstack-oslo15:15
dhellmannzzzeek: yes, oslo.db is in use so that work may need to be deferred to kilo :-/15:15
dhellmannzhiyan: what's up?15:15
zzzeekOK, not a prob15:15
*** markmcclain has quit IRC15:16
zhiyandhellmann: i used it in most places and works ok, but today i met an issue when i do it for urllib2.URLErro exception.15:16
dhellmannzzzeek: you can keep working on it, obviously, so we can land it as early as possible15:16
zhiyandhellmann: i got AttributeError: __exit__ issue15:17
zzzeekdhellmann: shoudld i move the blueprint in oslo-specs to kilo/ ?15:17
zhiyandhellmann: did you meet this as well? i'm interested in the cause, but no idea.15:17
dhellmannzzzeek: you can, but we have some other setup work to do in that repo so it might be less disruptive to go ahead and review it as it is for now15:18
zzzeekok15:18
dhellmannzhiyan: I haven't seen that. Can you post a traceback somewhere?15:18
*** markmcclain has joined #openstack-oslo15:18
zhiyandhellmann: http://paste.openstack.org/show/104790/15:18
zhiyandhellmann: btw, i'm using Python 2.7.615:19
dhellmannzhiyan: you need to call save_and_reraise_exception by adding the () even if you aren't passing any arguments15:20
dhellmannline 1315:20
*** viktors is now known as viktors|afk15:21
zhiyandhellmann: oh, my bad! hmm, i must need some sleeps. thanks!15:22
dhellmannzhiyan: :-)15:22
*** jecarey_ has joined #openstack-oslo15:23
*** Ajaeger1 has joined #openstack-oslo15:41
Ajaeger1dhellmann: thanks for the testr approval. Could you review https://review.openstack.org/117610, please? That gets the translation jobs working...15:42
dhellmannAjaeger1: looking15:43
dhellmannAjaeger1: +2a15:44
Ajaeger1dhellmann: thanks a lot!15:44
dhellmannAjaeger1: oslo.log work is likely to be lower priority this week, until after feature freeze15:44
Ajaeger1with those two patches in, oslo.log should be fine from a gate perspective...15:44
Ajaeger1dhellmann: I justed wanted the infra side working, I'm not planning on more patches ;)15:45
dhellmannAjaeger1: ok :-)15:45
*** shakamunyi has quit IRC15:46
*** takedakn has joined #openstack-oslo15:57
*** takedakn has quit IRC16:01
*** i159 has quit IRC16:03
dhellmannYorikSar: have you set up oslo.concurrency on pypi already?16:03
*** shakamunyi has joined #openstack-oslo16:04
*** morganfainberg_Z is now known as morganfainberg16:11
hartsocksdhellmann: ping16:11
dhellmannhartsocks: here16:11
hartsocksdhellmann: I just saw your note. I wasn't sure if you were aware I keep a presence in IRC.16:11
hartsocksdhellmann: The short of it is, I was moved teams just after the last OpenStack summit. I'm not active on that team right now. That might change soon.16:13
dhellmannhartsocks: the context isn't coming to mind, what note?16:13
hartsocksdhellmann: you asked about oslo.vmware and group memberships.16:13
dhellmannhartsocks: ah! that didn't go to just you, I used launchpad's "contact the maintainers" link16:13
dhellmannhartsocks: it has been handled, but thank you for following up16:13
hartsocksdhellmann: I'm basically, saying I'm not on that team's leadership anymore.16:14
hartsocksdhellmann: okay. Good.16:14
*** shakamunyi has quit IRC16:20
openstackgerritKen Giusti proposed a change to openstack/oslo.messaging: An initial implementation of an AMQP 1.0 based messaging driver  https://review.openstack.org/7581516:21
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo-incubator: Switch oslo-incubator to use oslo.utils  https://review.openstack.org/11464916:31
*** ildikov_ has quit IRC16:38
*** praneshp has joined #openstack-oslo16:51
amrithrussellb, would you please take a look at https://review.openstack.org/#/c/114664/. Thanks!17:00
*** takedakn has joined #openstack-oslo17:01
*** dtantsur is now known as dtantsur|afk17:01
amrithdhellmann, YorikSar ... but 1343604 has an OSSA alert tied to it. Commit https://review.openstack.org/#/c/116763/ is waiting for review on oslo.concurrency. Would you please help with a review if poss. Thanks!17:03
*** takedakn1 has joined #openstack-oslo17:04
*** harlowja has joined #openstack-oslo17:04
*** takedakn has quit IRC17:05
openstackgerritA change was merged to openstack/oslo.db: Add doc8 to tox environment docs  https://review.openstack.org/11400317:07
*** bnemec has quit IRC17:17
*** bnemec has joined #openstack-oslo17:18
*** praneshp_ has joined #openstack-oslo17:24
*** praneshp has quit IRC17:24
*** praneshp_ is now known as praneshp17:24
*** vigneshvar has joined #openstack-oslo17:26
*** mtanino has quit IRC17:26
*** praneshp_ has joined #openstack-oslo17:26
*** praneshp has quit IRC17:29
*** praneshp_ is now known as praneshp17:29
*** takedakn1 has quit IRC17:35
*** takedakn has joined #openstack-oslo17:35
harlowjadhellmann u might re+2ing https://review.openstack.org/#/c/106683/ ?17:48
harlowja*u mind17:48
harlowjaanyone know the author of python-memcached ?17:50
harlowjabe nice to have it for https://github.com/linsomniac/python-memcached/pull/52 (for dims and others... )17:50
dhellmannharlowja: +2a17:54
harlowjathx17:54
dhellmannharlowja: we should talk about FF and taskflow, too17:54
harlowjadhellmann on on https://review.openstack.org/#/c/106683/  +2a ?17:54
harlowja*only one on, ha17:54
harlowjasureeee17:55
dhellmannharlowja: mis-hit the mouse, 2nd time worked17:55
harlowjadamn mice17:55
harlowjaso dhellmann i'd like to get the 2-3 others on high priority @ https://etherpad.openstack.org/p/TaskFlow-0.417:55
harlowjathen have 0.417:55
harlowjathen feature freeze and such, and then 0.4.1 with other ones on there17:55
dhellmannis that likely to happen by the deadline?17:56
harlowjathis thursday right?17:56
dhellmannyes17:56
harlowjai think we can get 2 more reviews by this thursday17:56
harlowjai hope, ha17:56
harlowja2-317:56
harlowjabtw added tests for https://review.openstack.org/#/c/116544/17:57
dhellmannok, so that covers 0.4, and then do you have some bugs planned for 0.4.1?17:57
harlowjaa few ya,17:58
harlowjahttps://review.openstack.org/#/c/111543/ would be nice17:58
harlowjaand a few tiny other ones i think (and some other claenups)17:58
harlowjai'd say 0.4.1 would be nice to have the medium priority ones on that list17:58
dhellmannok, it would be good to have that etherpad list clarified down to the minimal set17:58
dhellmann0.4.1 should really only include bug fixes, right?17:59
harlowjayes, although shifting code around isn't really a bug or feature17:59
harlowjastuff like https://review.openstack.org/#/c/103245/ is just arrangement of code into better plae17:59
harlowja*place17:59
dhellmannright, so that also seems out of scope for a patch release17:59
harlowjakk18:00
harlowjalet me adjust that set then18:00
harlowjadocs and bugs then i think are ok for 0.4.1 ?18:00
dhellmannyeah, docs and bugs are good18:00
dhellmanndid you see the thread about milestone management?18:01
harlowjareading18:01
harlowjaseems fair i think18:02
dhellmannok, we'll probably plan on adopting that starting in kilo, then18:03
dhellmannalthough maybe earlier for some of the libs that don't have the long roadmap laid out like taskflow does18:03
*** Ajaeger1 has left #openstack-oslo18:04
harlowjalong roadmap u say :-P18:05
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Reject WBE messages if they can't be put in an ack state  https://review.openstack.org/11481418:06
dhellmannharlowja: well, you had a 0.5 series laid out :-)18:07
harlowjaah18:07
harlowjakk18:07
harlowjaguess that might be longer than others ;)18:07
dhellmannharlowja: yeah, most of the other libs haven't started thinking seriously about kilo yet18:10
*** harlowja has quit IRC18:12
*** harlowja has joined #openstack-oslo18:13
harlowjadhellmann k, updated https://etherpad.openstack.org/p/TaskFlow-0.418:19
harlowjalet me know if u think some of those not ok18:19
harlowjai personally like https://review.openstack.org/#/c/106216/18:20
harlowja:-P18:20
harlowjaremote calculatiion of the mandlebrot set ;)18:20
dhellmannharlowja: looking18:22
dhellmannharlowja: I'd like to get taskflow on the same cadence as the other libs, making kilo 0.5 and only actually releasing 0.4.1 if we have bugs to fix in 0.4.18:23
harlowjathat is fine with me18:23
dhellmannharlowja: ok, thanks, that will make release tracking a bit more predictable18:24
dhellmannharlowja: now, when do you think you'll be ready for a 1.0?18:24
harlowjathat seems to be the cadence anyway that is naturally occuring right now anyway, so might as well keep with it :-P18:24
dhellmannyep18:24
harlowjaso 1.0, hmmmm18:25
*** mtanino has joined #openstack-oslo18:25
dhellmanncan we talk about that as a goal for kilo, instead of calling it 0.5?18:25
harlowjawe could, although i start to wonder why (besides just making us all feel happy that we are using semantic versiioning and 1.0 is nice there)18:26
dhellmannyeah, the idea is to signal our intent that it is ready to be used in production (since it already is being used)18:27
harlowjawho really wants/desires that signal though ;)18:27
harlowjaits already a signal, person can just ask me18:28
harlowjalol18:28
dhellmannI hear a lot from consuming projects18:28
harlowjahave of the stuff in https://github.com/openstack/requirements/blob/master/global-requirements.txt isn't production ready then :-P18:28
dhellmannnot specifically about taskflow18:28
harlowja*half the stuff18:28
dhellmannyeah, well, most of that isn't being produced by openstack devs18:28
harlowjaanyways, let me think about it, it's probably possible, although i'm not sure it does much/adds much value (i've already been trying to make sure changes are X - 1 compat and such)18:30
harlowjait'd almost though let the project naturally evolve through its current rate and just let it evolve as is18:31
harlowjaseems less forced, more normal in a way18:31
dhellmanndo you have a roadmap to 1.0 then?18:31
harlowjai don't plan that far out, ha18:31
harlowja^ part of the evolution part (code to me evolves, ages if u will)18:32
harlowjalike a wine, ha18:32
dhellmannok, well, think about it. I'd really rather have everyone following the same system.18:33
harlowjau can't make a wine age quicker by just saying its aged, software sorta feels like that to me to :-P18:33
dhellmannwhat's https://review.openstack.org/#/c/109840/10/taskflow/engines/worker_based/proxy.py doing with kombu?18:33
harlowjado u want to know what that review is doign with kombu, or just in general?18:34
harlowjahttp://docs.openstack.org/developer/taskflow/workers.html might be useful18:35
harlowjataskflow not just run tasks locally18:35
harlowja*its what i call the WBE (not to confused with whooper)18:37
dhellmannthat code in general; I'll read the docs18:37
harlowjak, basically an engine can run things locally (useful for when this is useful) in threads or non-threads, then it can also connect that same stuff into remote workers18:38
harlowjasince an engine recieves a workflow, translates it into some format, then orchestrates/manages running it, this same thing can be done with remote processes as well18:39
harlowjajust manages things that aren't local (but may percieve to be local from a users point of view)18:39
harlowjaso from a taskflow user point of view its meant to be somewhat transparent (as transparent as possible)18:41
harlowjai was someday in the future/past going to use oslo.messaging, but that appears to be openstack centric and thus taskflow can't currently pull it in :-18:46
harlowja:-/18:46
*** flaper87|afk is now known as flaper8718:49
dhellmannharlowja: how about oslo.utils? https://review.openstack.org/#/c/116191/5/taskflow/utils/misc.py18:57
harlowjaonce https://github.com/openstack/oslo.utils/blob/master/requirements.txt#L4 is gone, yup18:57
harlowjai'll use that18:58
harlowjastill seems to suck in oslo.config18:58
harlowjais that planned to not get sucked in?18:58
dhellmannharlowja: I don't actually see us importing that anywhere18:58
dhellmannweird18:59
harlowjaah, then sure, i'll use oslo.utils18:59
harlowjaand oslo.serialization (which afaik also has the same problem)18:59
dhellmannI wonder if we have that in our cookiecutter template18:59
harlowjaah, maybe18:59
harlowjaya, from looking at oslo.utils not seeing it used19:00
dhellmannno, it may be coming from the exported requirements from the incubator?19:00
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo-incubator: fix small typo  https://review.openstack.org/11843719:00
openstackgerritDoug Hellmann proposed a change to openstack/oslo.utils: Remove unused dependency on oslo.config  https://review.openstack.org/11843819:01
dhellmannharlowja, dims : ^^19:01
harlowjacool19:01
dimsdhellmann: ah nice19:01
harlowjaseems good then, less things i don't have to worry about and can just use, phew19:02
*** lifeless has joined #openstack-oslo19:09
lifelessoh look another huge channel19:10
*** markmc has joined #openstack-oslo19:10
lifelessdhellmann: pbr-semver ping19:10
dhellmannlifeless: hey, I'm trying to sort out what we need to land by FF and what can wait. Where do things stand with the semver changes you're working on?19:11
dhellmannlifeless: I can't, for example, tell which changesets are associated with that blueprint19:11
lifelessok so19:11
harlowjalifeless more channels!19:11
harlowjawe need mooooreee channels19:11
lifelessall the helpful automation like tag-for-me can wait19:11
* dhellmann hadn't noticed we have so many lurkers in here until now19:12
*** jecarey has quit IRC19:12
lifelessdhellmann: https://review.openstack.org/#/c/114403/ and everything under it should be included asap IMO because that provides a cohesive transition19:12
lifelessdhellmann:  https://review.openstack.org/#/c/108270/18 failed because its not symmetrically gated with neutron19:13
lifelessdhellmann: devstack doesn't do 'setup.py install' just 'develop'19:13
lifelessdhellmann: I was asking around yesterday about opinions on the best way to make that symmetric19:13
dhellmannlifeless: yeah, I had a patch ready for infra for stuff like that but it lingered and sdague thought it was going to use too many resources19:14
*** dteselkin has quit IRC19:14
dhellmannlifeless: so do we need changes in neutron to fix the issue and let that patch land?19:14
lifelessso this is a repeating problem with neutron at least19:14
lifelessthey have a patch19:15
lifelessit was wending its way through gate 24h ago19:15
lifelessI asked about promoting it19:15
lifelessbut must have hit everyones lunch or something :/19:15
dhellmannoh, I saw a -1 from jenkins19:15
dhellmannor do you mean the neutron change?19:15
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo-incubator: Switch oslo-incubator to use oslo.utils  https://review.openstack.org/11464919:15
lifelessthe neutron change19:15
dhellmannhave a changeset id?I can ask kmestery and markmcclain to baby sit it19:16
lifelessit landed - 622b3cac8f1bab2c0348992e43929cd5dd8c13a219:16
lifelessI've rechecked the pbr change19:16
dhellmannok19:16
vigneshvarhi guys. I have an issue. i have used rpc.get_server method with a specific topic. I started it and i am able stop as well. How ever if i try to start again, it does not seem to work. Any clue ?19:16
lifelessnote the 'again' - this is the very identical change that neutron had to back out last time19:17
lifelessso really, running setup.py install somewhere on each neutron change shouldn't be a resource killer19:17
*** dteselkin has joined #openstack-oslo19:18
dhellmannvigneshvar: you probably want markmc, flaper87, or sileht to help with that. They're all in european time zones19:18
lifelesstripleo catches it, if we had the capacity to autorun all those jobs19:18
vigneshvardhellmann: Thanks19:18
dhellmannvigneshvar: we have a big deadline this week, so we're going to be focusing on code reviews and it may take a little time to get a response -- the -dev mailing list might be effective, too19:18
vigneshvardhellmann: sure i will follow it up with mailing list. thanks a ton19:19
dhellmannvigneshvar: any time!19:19
dhellmannlifeless: a simple job to run "pip instlal ." for each app seems fast and useful, but wouldn't the gate runs catch that anyway?19:23
lifelessdhellmann: they don't today19:26
lifelessdhellmann: because they use devstack which does pip develop .19:26
lifelessand thus doesn't run all the static file collection-copy-install code19:26
dhellmannah, right19:26
dhellmanndoes building the sdist catch it?19:27
lifelessI don't know19:27
* dhellmann is looking for the quickest job19:27
dhellmannok19:27
lifelessThere are two jobs today that I know of that catch it19:27
lifelessanything tripleo, which we would like to be running against everything19:27
dhellmannpbr has that job that verifies we can still install everything19:28
lifelessand check-requirements-integration-dsvm19:28
dhellmannthat's the one19:28
lifelesswhich we don't run against neutron etc changes19:28
dhellmannlifeless: building the sdist does not catch the error19:30
dimsdhellmann: did you have oslo.utils on your list as a fresh release? (fix for _import_*)19:33
lifelessdhellmann: you're testing with a older revision right? cause tip is fixed ;)19:33
dhellmanndims: I was going to hold off on releases until after the deadline thursday. do we need that one earlier?19:33
dhellmannlifeless: yes, I checked out the commit you sent, then HEAD~1 and tested both ways. sdist worked, install errored19:33
lifelesscool19:34
lifelessttx: ping19:34
dimsdhellmann: i think we should do that since _import_* caused a lot of headaches19:34
dhellmannok, are we ready for that?19:34
dimschecking19:34
dhellmannwe have 2 merging and the oslo.config dependency needs to merge I think19:35
dimsdhellmann: right19:36
dimsdhellmann: with that set, we should be good19:36
dhellmanndims: ok19:37
dhellmanndims: we should be careful about having anyone use utils until it is in the devstack gate19:37
dhellmanndims: https://review.openstack.org/#/c/117307/ has been approved but not merged yet19:38
dimsdhellmann: agreed19:38
dhellmanndims, bnemec : that doc I just shared with you has what I *think* we have left to do to call these libraries "done"19:42
dimsdhellmann: going through it19:44
* bnemec will look closer as soon as he finishes the file locking backport19:45
dhellmannquite a few holes, but I think we can finish for rc119:45
dhellmannand of course the list is based on the wiki instructions19:45
* dhellmann needs to go prep for the TC meeting19:45
openstackgerritamrith proposed a change to openstack/oslo-incubator: Mask passwords in exceptions and error messages  https://review.openstack.org/11845219:48
dimsdhellmann: when you get a chance - https://launchpad.net/oslo is missing oslo.log19:57
*** morganfainberg is now known as needs19:57
*** needs is now known as needscoffee19:57
bnemecWhy does pypi hate me?19:58
dhellmanndims: fixed20:04
dimsthanks!20:04
openstackgerritBen Nemec proposed a change to openstack/oslo-incubator: Use file locks by default again  https://review.openstack.org/11845720:05
bnemec^Push and pray since I can't get pypi to cooperate long enough to build a venv. >:-(20:06
*** kgiusti has left #openstack-oslo20:10
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Use and verify event and latch waited for values with timeouts  https://review.openstack.org/11846020:13
*** GheRivero_afk is now known as GheRivero20:27
*** amrith is now known as _amrith_20:34
jogoso I may have a oslo.db error20:50
jogohttp://logs.openstack.org/31/105031/14/gate/gate-tempest-dsvm-full/c05b927/logs/screen-n-cond.txt.gz?20:50
jogohttps://bugs.launchpad.net/nova/+bug/135313120:50
jogothere is a retry decorator on that function that does't seem to trigger20:50
jogomriedem: ^20:51
mriedemjogo: nova isn't using oslo.db yet20:51
mriedemthere is a review for it20:52
jogomriedem: sure, but oslo-incubator version of the code20:52
mriedemthe regex is a match: http://git.openstack.org/cgit/openstack/oslo-incubator/tree/openstack/common/db/sqlalchemy/session.py#n40620:54
mriedemnote the postgresql fix for the same isn't in there, but is in oslo.db20:54
mriedemthis is a mysql run though you linked me to20:54
*** needscoffee is now known as morganfainberg20:56
*** markmc has quit IRC21:02
jogomriedem: a more recent failure in mysql http://logs.openstack.org/79/95279/16/gate/gate-tempest-dsvm-full/d7e1280/logs/screen-n-cond.txt.gz?21:03
jogomriedem: does oslo.db fix this somehow?21:03
mriedemjogo: not that i'm aware of21:03
mriedemjogo: as noted in -nova the code looks correct, not sure why it's not handling the failure21:03
mriedemjogo: if this were pg i'd say it's obvious, because nova doesn't have the handling for pg, but that's not the case here21:04
jogoyeah21:04
jogoI am thinking the error being raised changed subtly?21:04
mriedemjogo: don't think so21:04
mriedemi plugged them into a regex tester and it's fine21:05
jogomriedem: not the regex21:05
jogobut the try except bock21:05
jogoblock21:05
jogozzzeek: ^21:06
mriedemjogo: seems fine21:08
mriedemthe db api calls are passing session as a kwarg to model_query which calls session.query which is wrapped http://git.openstack.org/cgit/openstack/nova/tree/nova/openstack/common/db/sqlalchemy/session.py#n70021:09
*** flaper87 is now known as flaper87|afk21:09
jogomriedem: we are catching a OperationalError in SQLA but the stacktrace starts in Mysqldb21:09
mriedemwell the stacktrace starts in the sqla driver which is mysqlconnector, and should be translated to sqla OperationalError21:12
mriedemwhich that wrapper should be catching21:12
jogomriedem: that is a few layers of should ;)21:13
ekarlsobtw, what's the pros / cons of mysqldb vs connnector +21:13
mriedemjogo: i'm wondering if self.bind.dialect.name is what we expect21:13
mriedemsorry this is mysqldb, not connector21:15
jogomriedem: good question21:15
jogomriedem: looks like it may be correct21:16
mriedemjogo: would be nice if this warned when the engine isn't handling deadlock failures:21:19
mriedemhttp://git.openstack.org/cgit/openstack/nova/tree/nova/openstack/common/db/sqlalchemy/session.py#n41821:19
mriedem"i'd like to help but you haven't told me how"21:20
jogomriedem: great idea21:20
jogoyou should add something to oslo.db21:21
jogomriedem: https://review.openstack.org/11847021:21
jogomriedem: a test patch to get some more logs21:21
*** takedakn1 has joined #openstack-oslo21:21
*** takedakn has quit IRC21:22
mriedemyeah i can add something to oslo.db21:22
jogomriedem: cool thanks21:24
jogomriedem: do you think its worth switching over to oslo.db for Juno?21:24
jogomriedem: I am torn on it21:24
jogoits risky but it makes backports and maint easier21:25
mriedemi haven't reviewed the change21:26
mriedemit does seem risky this late in the cycle21:26
mriedemi.e. not enough time for burn in21:26
jogomriedem: that is my thinking as well21:27
openstackgerritDoug Hellmann proposed a change to openstack/oslo-specs: Move the deferred logging specs to kilo  https://review.openstack.org/11847121:27
jogoif a oslo.db maint wants to compain for it I am all ears21:27
mriedemjogo: rpodolyaka was asking for reviews in -nova this morning21:29
zzzeekjogo: execption catching/rewriting is all different in oslo.db now21:29
zzzeektehre’s no more wrapper its done with a central event21:29
mriedemjogo: fwiw, we did merge a big oslo db sync right before feature freeze in icehouse21:30
jogozzzeek: so are you saying it should work better?21:30
jogomriedem: rpodolyaka and I didn't overlap this morning21:30
mriedemi'd be interested in knowing what other projects are already using oslo.db, for how long and if they've had any issues21:30
dhellmannjogo: I would advise planning to move to oslo.db by kilo-1 because the incubator code is going to be deleted soon. I'll leave it up to the nova team to decide whether that means doing it now, though.21:30
jogomriedem: ++21:30
zzzeekoslo.db’s current approach should guarantee all execptions intercepted, if that’s the issue21:30
zzzeekmriedem: said logic is brand new as of  a few weeks ago :)21:31
dhellmannmriedem: cinder designate glance heat ironic keystone neutron sahara tuskar21:31
dhellmannmriedem: according to their requirements.txt21:31
jogodhellmann: wow21:31
jogomriedem: so mabe we should land the oslo.db patch21:31
jogoI'll review it later today21:31
dhellmannjogo: yeah, oslo has stopped coming to nova first because you guys have a lot of other stuff going on, so this gives us a chance to work with smaller teams to resolve issues21:31
jogobeing there appears to already be good adoption and a few people to yell at when it breaks us ;)21:32
jogodhellmann: ++21:32
*** morganfainberg is now known as steve_notmorgan21:32
mriedemjogo: maybe, jaypipes was reviewing it before21:32
dhellmannjogo: we learned from oslo.messaging :-)21:32
mriedemjogo: i haven't reviewed it yet, and won't be able to in the next 10 min21:32
mriedemread: i'm busy for the next several hours,21:32
*** steve_notmorgan is now known as morganfainberg21:32
jogomriedem: neither well I but I its now at the top of my review list21:33
mriedem(and don't really want to review that tonight...)21:33
mriedemi'd be ok with it being a FFE in the ML too21:33
mriedemto get some attention on it, and would require 3 cores21:33
mriedemyou me and jaypipes would probably sponsor it21:33
mriedemactually it's not even tied to a blueprint21:34
*** _amrith_ is now known as amrith21:39
dhellmannharlowja: how much of oslo.messaging did you have to build into taskflow so that taskflow doesn't have to depend on oslo.messaging?21:40
harlowjadhellmann ah, good question21:40
dhellmannharlowja: https://review.openstack.org/#/c/114814/321:40
dhellmannharlowja: would it make sense to pull out the message bus driver stuff into a separate lib that taskflow can use and that can depend on oslo.messaging?21:41
jogomriedem: I would sponser a FFE too21:41
dhellmannharlowja: ditto for oslo.db in https://review.openstack.org/#/c/111543/21:42
harlowjadhellmann so u could consider https://github.com/openstack/taskflow/blob/master/taskflow/engines/worker_based/proxy.py to be part of oslo.messaging21:42
harlowjadhellmann anything that brings in oslo.config i won't touch it :)21:42
*** jgrimm is now known as zz_jgrimm21:42
harlowjajd__ tried and that caused lots of problems in tooz currently21:43
harlowja*well not lots, but problems21:43
harlowjai don't want apis that are half from one place, half from config...21:43
dhellmannharlowja: ok, we might have to have another discussion about whether taskflow is an oslo lib then, because I don't think it makes sense for us to be supporting 2 versions of all of these things just so you don't have to install oslo.config21:43
dhellmannperhaps we can work out the API issues in oslo.messaging so the config isn't required -- I thought we had most of that handled with the new url schemes anyway21:44
harlowjaor eliminate the usage of oslo.config :-P21:44
dhellmannyeah, that's not a realistic solution given our backwards compatibility requirements21:45
harlowjasure i know tooz tried to use oslo.config when it brought in oslo-incubator, stuff like http://paste.openstack.org/show/99963/ started occuring21:45
harlowjahaving a library that has an API that is magically touched at a distance by configuration options imho just doesn't feel right21:45
dhellmannso they have 2 modules defining the same option with different settings21:45
dhellmannthe user needs to configure the transport stuff. We don't want different option definitions in each app, so we put them in the common library.21:46
harlowjasure, thats great/nice for app usage21:48
dhellmannharlowja: seriously, put together some sort of description of what issues you'd have with oslo.messaging and oslo.db and whatever else so we can talk about how to address them. I had no idea you had duplicate implementations of all of this.21:48
dhellmannharlowja: look at the way we dealt with it in oslo.db, for example21:48
harlowjanot dupliacates neccasrily, they existed before the oslo.* stuff21:48
dhellmannyou wrote a message bus rpc thing before oslo.messaging?21:49
harlowjayes21:49
dhellmannhow old is taskflow then? because I thought it was newer than oslo.21:49
harlowja1.65 years21:49
harlowjanewer than oslo incubator21:50
harlowjabut not newer than the rest21:50
harlowjahttp://lists.openstack.org/pipermail/openstack-dev/2013-September/015088.html21:50
dhellmannok. well, now we have 2, and I don't like having 2 of things, so let's see what we can do about it21:50
ekarlsoyah, I remember that one looong way back : p21:51
harlowjasure i did create https://blueprints.launchpad.net/taskflow/+spec/use-oslo-db and https://blueprints.launchpad.net/taskflow/+spec/use-oslo-messaging but recently the discussion was that oslo.* libraries should only be used in apps from what i remember21:51
harlowjaand taskflow isn't an app21:52
harlowjaanyways21:52
dhellmannused within *openstack* not just apps, but we also assumed the rational wouldn't be used as a justification to support 2 implementations of those features21:53
harlowjaall for helping merge them, if we feel its a way to go21:55
harlowjajust gotta learn how to walk before u can run, and so-on21:55
*** alexpilotti has quit IRC21:57
dhellmannok, so let's put together a realistic plan for making the changes needed in all 3 libs (and any others I haven't spotted -- I see some incubated modules in there, too)21:59
harlowjadhellmann ya, the incubatored ones will have to be kicked on soon anyway22:03
harlowjaanyways, let see what i can writeuop22:05
dhellmannok, thanks22:05
*** bknudson has quit IRC22:05
harlowjasure22:06
*** dims has quit IRC22:07
*** dims has joined #openstack-oslo22:08
harlowjadhellmann will just write this up @ https://etherpad.openstack.org/p/taskflow-oslo-db-messaging (empty right now, ha)22:11
dhellmannharlowja: sounds good; we'll get the team to review it a bit and then you can turn it into a spec22:11
harlowjasure22:12
*** dims has quit IRC22:12
*** pcm_ has quit IRC22:13
*** stevemar has quit IRC22:21
*** jecarey_ has quit IRC22:21
*** jaosorior has quit IRC22:22
*** gordc has quit IRC22:28
*** pcm_ has joined #openstack-oslo22:44
*** pcm_ has quit IRC22:48
*** pcm_ has joined #openstack-oslo22:49
*** stevemar has joined #openstack-oslo22:54
*** zzzeek has quit IRC23:05
*** zzzeek has joined #openstack-oslo23:12
*** tongli has quit IRC23:16
*** tongli has joined #openstack-oslo23:16
*** praneshp has quit IRC23:31
*** stevemar has quit IRC23:35
*** oomichi has quit IRC23:35
*** markmcclain has quit IRC23:37
*** oomichi has joined #openstack-oslo23:45
*** zzzeek has quit IRC23:48
*** takedakn1 has quit IRC23:58
*** takedakn has joined #openstack-oslo23:58
*** praneshp has joined #openstack-oslo23:59

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