Friday, 2014-03-14

*** openstack has joined #openstack-oslo00:53
*** dims_ has joined #openstack-oslo00:53
*** bogdando has joined #openstack-oslo00:54
*** openstack has joined #openstack-oslo00:56
*** openstack has quit IRC00:57
*** openstack has joined #openstack-oslo00:59
*** rpodolyaka has joined #openstack-oslo00:59
*** hdd_ has joined #openstack-oslo01:02
*** rpodolyaka1 has joined #openstack-oslo01:07
*** rpodolyaka has quit IRC01:08
*** rpodolyaka1 has quit IRC01:14
*** openstack has joined #openstack-oslo01:15
*** openstack has joined #openstack-oslo01:19
*** openstack has quit IRC01:24
*** openstack has joined #openstack-oslo01:25
*** openstack has joined #openstack-oslo15:09
*** matrohon has joined #openstack-oslo15:09
*** banix has joined #openstack-oslo15:10
ihrachysmarkmcclain: I've checked cinder and nova porting patches to see how they solved the problem, and they didn't... because they don't create rpc connections in random places, instead relying on services to invoke proper methods [this can be my incorrect understanding though, I haven't checked their code for too long]15:11
markmcclainihrachys: we probably should clean up how we start RPC15:11
markmcclainwould it make sense to add something similar to init_db that arosen added to the plugins?15:12
dhellmannihrachys: that's why I wondered if the plugin was subclassed from something like MessageHandlingServer15:12
markmcclainalso for the unit tests we shouldn't be spawning RPC threads anyway15:12
dhellmannthere is setup_rpc(), there's just nothing cleaning it up when the plugin is "done"15:13
ihrachysmarkmcclain: yes, probably, though oslo.messaging does not have fake executor at the moment anyway15:13
markmcclainihrachys: here's what I'm thinking15:14
ihrachysmarkmcclain: whatis init_db? I failed to find it in source tree15:14
*** yamahata has quit IRC15:14
*** yamahata has joined #openstack-oslo15:14
markmcclainihrachys: sorry wrong method name.. he folded it into the base class' init15:15
*** rpodolyaka has joined #openstack-oslo15:15
markmcclainhttps://github.com/openstack/neutron/blob/master/neutron/db/db_base_plugin_v2.py#L22415:15
markmcclainihrachys: so right now we're in the process of revising/defining a new version of the plugin's class API15:16
markmcclainihrachys: might make sense to pause on your current work as we work out what the design plans15:17
markmcclainwe can incorporate the design changes needs to enable you to port to oslo.messaging15:18
ihrachysmarkmcclain: dhellmann: also I've noticed that tests run a lot longer with oslo.messaging, so now I wonder whether it may be the case of unused threads spawned in tests...15:18
markmcclainihrachys: I'm hoping we will be able to share a draft plan by the end of the month with community would that work?15:18
markmcclainihrachys: likely15:18
ihrachysmarkmcclain: dhellmann: and 'a lot' is like '2.5 times longer'15:19
markmcclainihrachys: ouch that's a painful delay15:19
ihrachys+ memory usage is a lot higher (rpc servers unstopped?)15:19
dhellmannihrachys: that seems possible, but we haven't seen that elsewhere so I wonder if it is related to not stopping them?15:19
markmcclainmy guess is the clean-up between tests is leaving lots of objects around15:20
markmcclainwe already had a few subtle leaks via cyclical obj relationships15:20
ihrachysactually, this is what took me here to discuss rpc connections in plugins :) I was in the middle of debugging slowliness issue when caught those greenlets in the logs.15:20
ihrachysdhellmann: that's exactly my convern - getting connections sitting there in memory15:21
ihrachysmarkmcclain: btw I've seen TestCases in the list of object types left after the run. why are they even left sitting there AFTER they are run?15:22
ihrachysmarkmcclain: yes, master also leaks, just not that much as with my patch15:22
markmcclainihrachys: the garbage collector is unable to reap them15:23
ihrachysin 2012, we had this patch applied to reduce memory usage https://review.openstack.org/#/c/16735/3/quantum/tests/unit/test_db_plugin.py15:23
ihrachysand frankly, in the bug linked, a person claimed that it was enough to have ~200 MB RES RAM to run tests15:23
markmcclainright that was only a bandaid to the larger problem15:23
ihrachysnow it uses like gigabytes of RAM...15:23
markmcclainyes that is problem that marun and others have been thinking about how to solve15:24
markmcclainihrachys: so are you ok pausing on your current work for now and we can revisit at the end of the month when we start talking about API framework changes?15:27
ihrachysmarkmcclain: without solving this rpc cleanup issue I can't proceed to get the patch in review phase anyway, so probably we'll live with it :)15:28
markmcclainihrachys: ok.. when the 1st design draft is published I'll ping you to get your feedback15:29
seagullsit probably would be best to collaborate to find a closer-to-optimal solution than beat our heads against the wall trying to hack our way through15:29
ihrachysthis oslo.messaging port looked quite easy at first sight when I started :) [I've checked cinder and glance and nova patches at that moment and it looked quite easy to achieve the same in neutron]15:29
ihrachysmarkmcclain: thanks!15:29
seagullsit's a very worthwhile effort nonetheless, ihrachys has uncovered/exposed lots of things to discuss and improve15:29
ihrachysdhellmann: but still, it would be probably great to see fake executor available. it's not nice to run threads in tests.15:30
dhellmannihrachys: if you can move the thread management out of the plugins, then the unit tests won't start threads15:31
* seagulls nods15:31
seagullsI've seen similar snafus in dealing with CORBA and other OOM systems. where folks put OOM initialization code in their servants15:33
seagullsit always ends in tears15:33
seagullswe wouldn't run into the same issues here, but there are issues.. obviously15:34
ihrachysdhellmann: moving rpc connections creation in separate function can be the way to go. but then something should call this separated method (and stop method too), and I think this is where we lack understanding how to achieve this15:34
dhellmannihrachys: why does the plugin need to create those connections at all? why isn't the plugin being called by something that creates the connections, receives the messages, and then needs the plugin to do the work?15:35
ihrachysdhellmann: surely, this is how it should look like - separate setup_rpc/cleanup_rpc method called from outside by some manager15:38
dhellmannihrachys: no, that's not what I mean  at all15:38
dhellmannihrachys: the plugin should not need to create or manage its own rpc connections15:38
dhellmannthe plugin shouldn't even need to know it is being fed data from rpc15:39
dhellmannsome common core piece should handle all of that15:39
seagulls+115:39
seagullswhere possible business logic implementation, should not know or implement anything regarding the specifics of how it is being called15:40
dhellmannseagulls: right15:41
seagullsit can then be used in any manner as seen fit without extra consideration15:41
seagullsit is more testable, easier to write, etc. etc. etc15:41
*** rpodolyaka has quit IRC15:42
ihrachysah, ok. plugins will just provide the list of endpoints, right?15:42
dhellmannihrachys: right15:42
*** hartsocks has quit IRC15:43
*** hartsocks has joined #openstack-oslo15:44
* markmcclain reads scrollback15:44
markmcclaindhellmann: so one pattern is some plugins use RPC to talk to proprietary agents, so we'll need to have a interface for a plugin to register callbacks15:45
*** drumkilla is now known as rustlebee15:47
seagullsmarkmcclain, are you referring to a call flow of RPC-Layer->Endpoint->proprietary-agent or something else?15:48
*** markmcclain has quit IRC15:50
openstackgerritAnastasia Karpinska proposed a change to openstack/taskflow: Move flow states to developers documentation  https://review.openstack.org/8035016:07
*** salv-mobile has quit IRC16:17
openstackgerritTerry Howe proposed a change to openstack/cliff: Add value only output formattter  https://review.openstack.org/8061416:19
*** rpodolyaka has joined #openstack-oslo16:25
*** openstackstatus has joined #openstack-oslo16:38
openstackgerritCyril Roelandt proposed a change to openstack/oslo-incubator: Python3: pass bytes as 'contents' to create_tempfiles()  https://review.openstack.org/8062716:46
*** rpodolyaka has quit IRC16:51
*** dims has joined #openstack-oslo16:54
*** matrohon has quit IRC16:55
*** saikrishna_ has joined #openstack-oslo16:56
*** rpodolyaka has joined #openstack-oslo16:58
*** dims has quit IRC17:00
*** markmcclain has joined #openstack-oslo17:00
*** markmcclain has quit IRC17:00
*** markmcclain has joined #openstack-oslo17:01
*** harlowja_away is now known as harlowja17:02
openstackgerritBrant Knudson proposed a change to openstack/oslo-incubator: Add connection trace for DB2  https://review.openstack.org/7016317:21
*** morganfainberg_Z is now known as morganfainberg17:21
beekneemechHmm, I think these Python 3 changes probably shouldn't go in during feature freeze.17:30
beekneemechIt isn't something we support now, so it's really a new feature, and it's going to add noise to any critical syncs to other projects.17:31
*** dshulyak has quit IRC17:34
*** mriedem has quit IRC17:37
*** mriedem has joined #openstack-oslo17:39
*** dims has joined #openstack-oslo17:40
*** rpodolyaka has quit IRC17:45
ekarlsois it possible to do a rpc.call() towards a host ?17:45
ekarlsoor is that only in .cast17:45
*** saikrishna_ has quit IRC17:47
*** rpodolyaka has joined #openstack-oslo17:48
dhellmannbeekneemech: +117:52
openstackgerritAnastasia Karpinska proposed a change to openstack/taskflow: Move flow states to developers documentation  https://review.openstack.org/8035018:17
*** hartsocks is now known as hartbot18:19
openstackgerritSolly Ross proposed a change to openstack/oslo-incubator: Report: Add basic processes section  https://review.openstack.org/7879318:34
openstackgerritSolly Ross proposed a change to openstack/oslo-incubator: Report: Propagate view_type through collections  https://review.openstack.org/7879218:34
openstackgerritSolly Ross proposed a change to openstack/oslo-incubator: Report: Support Sequences and Mappings as Data  https://review.openstack.org/7879118:34
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Move change state to after storage calls  https://review.openstack.org/8065718:36
*** seagulls is now known as seagulls_coffee18:38
*** rpodolyaka has quit IRC18:39
*** rpodolyaka has joined #openstack-oslo18:47
*** seagulls_coffee is now known as seagulls18:59
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Add graph property to all flow patterns  https://review.openstack.org/7253219:08
*** rpodolyaka has quit IRC19:14
*** rpodolyaka has joined #openstack-oslo19:17
*** rpodolyaka has quit IRC19:25
*** rpodolyaka has joined #openstack-oslo19:26
*** rpodolyaka has quit IRC19:47
*** Oslomann29 has joined #openstack-oslo19:48
*** rpodolyaka has joined #openstack-oslo19:49
*** yamahata has quit IRC20:07
*** jraim has joined #openstack-oslo20:09
*** rpodolyaka has quit IRC20:10
jraimdhellmann: question about oslo.logging if you have a sec20:11
dhellmannjraim: sure20:11
jraimwe had this PR put in20:11
jraimhttps://review.openstack.org/#/c/79011/20:11
jraimwhich is complaining about a problem that logging is causing in heat templates and we're trying to figure out the right way to fix it20:12
* dhellmann looks20:13
dhellmannso the barbican client is registering command line options at import time?20:13
*** Oslomann29 has left #openstack-oslo20:14
dhellmannoh, no, it imports oslo.log and we do that20:14
dhellmannok, here's my juno plan for oslo.log:20:14
dhellmannWe are starting to move logic from the ContextAdapter to ContextFormatter. When that is done, projects won't need to ask oslo.log for a log handler, since the formatter will be registered by the application and won't need to be attached to each handle.20:15
*** rpodolyaka has joined #openstack-oslo20:15
dhellmannAt that point, libraries can stop using oslo.log and just use python's logging module. Applications would need to use oslo.log to set up the formatter and handler, but they would only have to do that at the start of the process.20:16
jraimthat makes sense20:16
*** rpodolyaka has quit IRC20:16
dhellmannso I think removing oslo logging from the barbican client is the right approach20:16
jraimalright, we'll remove it for now and add it back in later if needed20:17
*** hartbot has left #openstack-oslo20:17
dhellmannjraim: ok20:17
jraimthanks for the advice20:17
dhellmannjraim: any time!20:17
*** rpodolyaka has joined #openstack-oslo20:18
*** rpodolyaka has quit IRC20:48
*** mriedem has left #openstack-oslo21:16
*** mriedem has quit IRC21:16
*** arnaud has joined #openstack-oslo21:20
*** openstackgerrit has quit IRC21:21
*** openstackgerrit has joined #openstack-oslo21:21
*** openstackgerrit has quit IRC21:32
*** openstackgerrit has joined #openstack-oslo21:32
*** dims has quit IRC21:34
openstackgerritZane Bitter proposed a change to openstack/oslo-incubator: Config generator: handle options in multiple groups  https://review.openstack.org/7973821:38
openstackgerritTerry Howe proposed a change to openstack/cliff: Add value only output formattter  https://review.openstack.org/8061421:42
*** zhiyan is now known as zhiyan_21:42
*** rpodolyaka has joined #openstack-oslo21:47
*** dims has joined #openstack-oslo21:53
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Adjust the exception hierachy  https://review.openstack.org/8037222:07
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Adjust the exception hierachy  https://review.openstack.org/8037222:08
* beekneemech -2's all the things22:12
beekneemechI wasn't sure what to do with the Python 3 test-only changes though.  There's technically an argument to be made that those don't fall afoul of the feature freeze restrictions since they aren't synced to other projects.22:12
beekneemechFor the moment I just left them alone.22:13
*** banix has quit IRC22:18
* beekneemech is fried and leaves for the weekend22:19
beekneemechSee y'all Monday :-)22:19
*** rpodolyaka has quit IRC22:26
*** ihrachys has quit IRC22:26
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Adjust logging levels and usage to follow standards  https://review.openstack.org/8049722:48
*** rpodolyaka has joined #openstack-oslo22:49
*** flaper87 is now known as flaper87|afk23:27
*** rpodolyaka has quit IRC23:32
*** openstackstatus has quit IRC23:36
*** openstackgerrit has quit IRC23:39
*** arnaud has quit IRC23:43
*** lbragstad has quit IRC23:46
*** seagulls has quit IRC23:46
*** bogdando has quit IRC23:46
*** sergmelikyan has quit IRC23:46
*** harlowja has quit IRC23:46
*** bknudson has quit IRC23:46
*** jd__ has quit IRC23:46
*** zhiyan_ has quit IRC23:46
*** dhellmann has quit IRC23:46
*** clarkb has quit IRC23:46
*** wingwj has quit IRC23:46
*** beav has quit IRC23:46
*** viktors_ has quit IRC23:46
*** yamahata_ has quit IRC23:46
*** flaper87|afk has quit IRC23:46
*** jeblair has quit IRC23:46
*** dteselkin has quit IRC23:46
*** SergeyLukjanov has quit IRC23:46
*** ruhe has quit IRC23:46
*** gilliard has quit IRC23:46
*** sileht has quit IRC23:46
*** jraim has quit IRC23:46
*** GheRivero has quit IRC23:46
*** openstack has joined #openstack-oslo23:46
*** rpodolyaka1 has joined #openstack-oslo23:47
*** openstackstatus has joined #openstack-oslo23:47

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