Monday, 2014-08-18

*** mriedem has quit IRC00:06
*** oomichi has joined #openstack-oslo00:47
*** harlowja is now known as harlowja_away00:58
*** shakayumi is now known as shakamunyi00:59
*** arnaud__ has joined #openstack-oslo01:20
*** morganfainberg is now known as morganfainberg_Z01:35
*** arnaud has quit IRC01:46
*** arnaud__ has quit IRC01:46
*** shakayumi has joined #openstack-oslo01:46
*** shakamunyi has quit IRC01:49
*** morganfainberg_Z is now known as morganfainberg02:37
openstackgerritlifeless proposed a change to openstack-dev/pbr: Raise an error if preversion versions are too low  https://review.openstack.org/10826902:47
openstackgerritlifeless proposed a change to openstack-dev/pbr: Look for and process sem-ver pseudo headers in git  https://review.openstack.org/10827002:47
openstackgerritlifeless proposed a change to openstack-dev/pbr: Refactor oneline changelog walking.  https://review.openstack.org/10827102:47
openstackgerritlifeless proposed a change to openstack-dev/pbr: Only consider tags that look like versions.  https://review.openstack.org/11440302:47
*** stevemar has joined #openstack-oslo03:14
*** flashgordon is now known as jogo03:19
*** amotoki_ has joined #openstack-oslo03:51
*** amotoki_ has quit IRC03:52
*** Krast has joined #openstack-oslo03:56
*** stevemar has quit IRC04:44
*** amotoki_ has joined #openstack-oslo05:12
*** SridharG has joined #openstack-oslo05:27
*** SridharG has quit IRC05:33
openstackgerritOpenStack Proposal Bot proposed a change to openstack/oslo.vmware: Imported Translations from Transifex  https://review.openstack.org/11473206:08
*** SridharG has joined #openstack-oslo06:39
*** AAzza_afk is now known as AAzza06:54
*** noelbk has joined #openstack-oslo06:54
*** ildikov has joined #openstack-oslo07:22
*** mrda is now known as mrda-away07:25
*** ihrachyshka has joined #openstack-oslo07:29
*** ihrachyshka_ has joined #openstack-oslo07:30
*** ihrachyshka has quit IRC07:34
*** viktors has joined #openstack-oslo07:39
*** AAzza is now known as AAzza_afk07:56
*** linkid has joined #openstack-oslo08:27
*** alexpilotti has joined #openstack-oslo08:55
*** pblaho has joined #openstack-oslo09:41
*** pblaho is now known as pblaho|afk09:59
*** pcm_ has joined #openstack-oslo10:04
*** pcm__ has joined #openstack-oslo10:07
*** pcm_ has quit IRC10:10
*** yamahata has joined #openstack-oslo10:16
*** yamahata has quit IRC10:21
*** pblaho|afk is now known as pblaho10:47
openstackgerritA change was merged to openstack/oslo.vmware: Add support for the DatastoreURL object  https://review.openstack.org/11471010:55
*** sheeprine has quit IRC11:16
*** pblaho_ has joined #openstack-oslo11:16
*** pblaho has quit IRC11:20
*** sheeprine has joined #openstack-oslo11:29
*** sheeprine has joined #openstack-oslo11:29
*** Alexei_987 has joined #openstack-oslo11:44
*** gordc has joined #openstack-oslo12:08
*** pblaho_ is now known as pblaho|afk12:25
*** amotoki_ has quit IRC12:31
*** pblaho|afk is now known as pblaho_12:37
*** AAzza_afk is now known as AAzza12:38
*** pblaho_ is now known as pblaho12:46
*** bknudson1 has quit IRC13:08
*** jeckersb_gone is now known as jeckersb13:13
*** pblaho_ has joined #openstack-oslo13:28
*** jecarey has joined #openstack-oslo13:29
*** pblaho has quit IRC13:31
*** dims has joined #openstack-oslo13:34
*** markmc has joined #openstack-oslo13:40
*** miqui has joined #openstack-oslo13:45
*** yamahata has joined #openstack-oslo13:45
*** jeckersb is now known as jeckersb_gone13:51
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: port ds_util from nova to oslo.vmware  https://review.openstack.org/11455113:53
*** jeckersb_gone is now known as jeckersb13:56
*** ildikov has quit IRC14:00
*** Krast_ has joined #openstack-oslo14:04
*** yamahata_ has joined #openstack-oslo14:04
*** miqui_ has joined #openstack-oslo14:04
*** zzzeek has joined #openstack-oslo14:06
*** hyakuhei_ has joined #openstack-oslo14:06
*** miqui has quit IRC14:11
*** markmc has quit IRC14:11
*** viktors has quit IRC14:11
*** Krast has quit IRC14:11
*** hyakuhei has quit IRC14:11
*** yamahata__ has quit IRC14:11
*** pblaho__ has joined #openstack-oslo14:12
*** pblaho__ is now known as pblaho14:12
*** yamahata has quit IRC14:13
*** yamahata has joined #openstack-oslo14:14
*** beekneemech is now known as bnemec14:15
*** pblaho_ has quit IRC14:16
*** oomichi has quit IRC14:16
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely  https://review.openstack.org/11017014:17
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Use testr instance provisioning to lazily create databases  https://review.openstack.org/11048614:17
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Add transactional test support to provisioning  https://review.openstack.org/11315314:17
*** mriedem has joined #openstack-oslo14:17
*** viktors has joined #openstack-oslo14:18
*** markmc has joined #openstack-oslo14:18
zzzeekhey viktors !14:19
viktorszzzeek: hi!14:19
zzzeekhow was vaca14:19
*** SridharG has quit IRC14:20
viktorszzzeek: vacation is always nice! :)14:20
zzzeekso ill be coming on to core review to help out14:20
*** miqui_ is now known as miqui14:21
zzzeekbut until then I have a whole line of +2’s I need :) https://review.openstack.org/#/q/owner:%22Michael+Bayer%22+status:open,n,z14:21
*** jecarey has quit IRC14:22
*** jecarey has joined #openstack-oslo14:22
viktorszzzeek: I hope to look at oslo.db's patches tomorrow with the fresh head - today is my first working day )14:22
viktorsbtw, dhellmann, should we wait for someone's vote, before we will add zzzeek to the core team?14:23
zzzeekviktors: OK.14:23
viktorszzzeek: by the way, I have a question about patch https://review.openstack.org/#/c/110486/14:26
zzzeekyup14:27
*** jecarey has quit IRC14:27
viktorszzzeek: I think, that this is a bad idea - to depends on testr (or some another test runner)14:27
viktorszzzeek: have you tried to use something like this - https://docs.python.org/2/library/atexit.html ?14:28
zzzeekviktors: OK well there is also another change that will be to use scenarios, and for that we have to use testscenarios which is also part of the testr world14:28
zzzeekviktors: atexit is very unpredictable in my experience14:28
zzzeekviktors: all test systems support some form of “dispose after all tests” idea - so to support other runners, we can implement for those as well14:29
zzzeekviktors: here’s how SQLAlchemy does it for both nose and py.test: https://bitbucket.org/zzzeek/sqlalchemy/src/530d3f07e0c1e70e0f9b80d3b5986253e06dcaf2/lib/sqlalchemy/testing/plugin/?at=master14:30
* viktors looking14:30
zzzeekviktors: maybe there’s a way to make tox do it ?   we are comfortable depending on tox right ?14:31
viktorszzzeek: well, sure we can do it via tox, but I'm not really sure about it14:32
zzzeekviktors: also what was proposed was that tests run via shell scripts14:32
zzzeekviktors: which i dont really like.  it means we have to add a shell script to all projects and change how they all run tests14:32
*** yamahata has quit IRC14:32
zzzeekviktors: to me it seems like a failure of the test runners14:33
viktorszzzeek: my idea is - we should be able to run any test using any test runner14:33
viktorsinside or outside of the virtual environment14:34
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: port ds_util from nova to oslo.vmware  https://review.openstack.org/11455114:34
zzzeekviktors: there has to be a test collector of some kind in order to run tests14:34
zzzeekviktors: even if you use straight unittest, you need to call unittest.main()14:34
viktorszzzeek: thats true14:35
zzzeekviktors: so you need to solve the collection issue, and IMHO the setup/teardown bording that is part of that same issue14:36
zzzeekviktors: so IMHO the approach we use for resource setup/teardown should be integreated with the collector being used.14:36
zzzeekviktors: keep in mind the patch here in no way prevents tests from being run with any runner14:37
zzzeekviktors: I usually run with py.test, works great14:37
zzzeekviktors: this *only* applies to parallel test runs, which we only support with testr right now14:37
viktorszzzeek: yes, I agree that testr is default test runner, so we should use it's features.14:39
viktorszzzeek: I just want to be sure, that if I'll want to set pdb in a single test, I'll be able to do it without a lot of magic :)14:40
viktorsfor example14:40
zzzeekviktors: nothing is changing in that regard14:40
zzzeekviktors: using pdb with testrunner is already a pile of crap, nothing is changing there, I use py.test if im pdbing14:41
viktorszzzeek: ok, I should check it locally14:41
zzzeekviktors: all of these patches only alter the mechanics of when the “anonymous” database is created/dropped14:42
*** tsekiyama has joined #openstack-oslo14:42
zzzeekto be more efficient14:42
viktorszzzeek: ok14:43
* viktors forgot about everything during vacation :)14:44
viktorszzzeek: one more thing - have you some experience with db query retrying?14:46
zzzeekyup14:46
*** markmcclain has joined #openstack-oslo14:49
viktorszzzeek: can you provide some info about it? We just made a similar feature some time ago, but I'm not sure, that it in use14:50
zzzeekviktors: query retrying can become complex if we are talking about a connection that was dropped14:50
zzzeekviktors: because the transaction is gone14:50
zzzeekviktors: so I prefer to look at it as “transaction retrying"14:50
zzzeekviktors: and in the context of openstack and its web API methods, i think the simplest way to “retry” is just run the whoel web API method again in case of a dropped connection14:51
*** rustlebee is now known as russellb14:52
*** bknudson has joined #openstack-oslo14:54
viktorszzzeek: yes, we did it in a same way :)15:00
*** gpocente1 is now known as gpocentek15:07
*** gpocentek has quit IRC15:07
*** gpocentek has joined #openstack-oslo15:07
zzzeekviktors: there is a “retry the whole transcation” system I wrote, though i dont know that openstack needs it.  you can see that here: https://bitbucket.org/zzzeek/sqlalchemy/issue/3104/transaction-replay-extension15:10
*** jecarey has joined #openstack-oslo15:10
*** stevemar has joined #openstack-oslo15:11
*** ihrachyshka_ has quit IRC15:12
openstackgerritJulien Danjou proposed a change to openstack/oslo.concurrency: lockutils: catch BusyError when locking with timeout  https://review.openstack.org/11499315:13
viktorszzzeek: well, we made it in a similar way - https://github.com/openstack/oslo.db/blob/master/oslo/db/api.py#L62-L12015:14
zzzeekyes that patch is appropriate for wrapping an API method15:14
openstackgerritJulien Danjou proposed a change to openstack/oslo.messaging: Port to Python 3  https://review.openstack.org/10800715:14
zzzeekthe “transaciton replay” thing is actually much more elaborate and risky, it is recording all statements and replaying selected ones15:15
zzzeekviktors: and its 100% transparent too … :)15:15
zzzeekviktors: wrote it for a client.   its nuts15:15
viktorszzzeek: :)15:16
openstackgerritJulien Danjou proposed a change to openstack/oslo.messaging: Import notifier middleware from oslo-incubator  https://review.openstack.org/10574615:18
openstackgerritJulien Danjou proposed a change to openstack/oslo.messaging: Import oslo-incubator context module  https://review.openstack.org/10574515:18
openstackgerritJulien Danjou proposed a change to openstack/oslo.messaging: Import oslo-incubator/middleware/base  https://review.openstack.org/10574415:18
*** alexpilotti has quit IRC15:20
*** markmcclain has quit IRC15:35
*** ildikov has joined #openstack-oslo15:45
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: port ds_util from nova to oslo.vmware  https://review.openstack.org/11455115:48
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: port ds_util from nova to oslo.vmware  https://review.openstack.org/11455115:56
*** bnemec has quit IRC15:57
amrithhello oslo-core ... would you please review https://review.openstack.org/#/c/113407/, https://review.openstack.org/#/c/114656/, https://review.openstack.org/#/c/114659/, https://review.openstack.org/#/c/114664/15:59
*** AAzza is now known as AAzza_afk16:11
openstackgerritBogdan Dobrelya proposed a change to openstack/oslo.messaging: Should not send replies for cast messages  https://review.openstack.org/11501016:14
dhellmannamrith: several of those failed their last jenkins run16:15
dhellmannamrith: and you need https://review.openstack.org/#/c/114614/ on that list :-)16:17
openstackgerritBogdan Dobrelya proposed a change to openstack/oslo.messaging: Should not send replies for cast messages  https://review.openstack.org/11501016:18
*** viktors is now known as viktors|afk16:23
YorikSardhellmann: They're failing because of https://review.openstack.org/11464716:29
dhellmannYorikSar: ah, ok16:30
YorikSardhellmann: I wonder if it's ok if I approve it or should I wait for someone else?..16:30
dhellmannYorikSar: +2a16:32
YorikSardhellmann: Great :)16:33
*** praneshp has joined #openstack-oslo16:33
dimsdhellmann: i need a oslo.utils release with mask_password to jump start the olso/nova integration (which also means updating global reqs)16:34
YorikSardhellmann: But for the future - is it ok to not wait for second core to approve such changes?16:34
dhellmanndims: can we merge the mask_password fix first?16:36
dimsdhellmann:  yep16:36
dhellmannYorikSar: we tend to look at it case-by-case; it's better to ask for reviews here16:36
dims"with mask_password" :)16:36
dhellmanndims: there were 2 patches, right? add the function and enhance its security?16:36
dimsdigging up one sec. yes, there were 216:37
dimsjust one left - https://review.openstack.org/#/c/114614/16:38
dimsany nova cores around? (116414 has dhellmann's +2 already)16:39
dimsoops oslo cores :)16:39
dhellmann:-)16:40
dhellmanntime for lunch, bbiab16:40
dimsyou can see where my brain is wired to ask for reviews :)16:40
*** zzzeek has quit IRC16:42
*** harlowja_away is now known as harlowja16:45
*** zzzeek has joined #openstack-oslo16:50
*** ildikov has quit IRC16:53
*** bnemec has joined #openstack-oslo17:04
*** markmcclain has joined #openstack-oslo17:18
*** markmcclain has quit IRC17:18
*** markmcclain has joined #openstack-oslo17:19
*** Alexei_987 has quit IRC17:33
*** harlowja is now known as harlowja_away17:46
*** SridharG has joined #openstack-oslo17:49
*** bnemec has quit IRC17:53
*** bnemec has joined #openstack-oslo17:56
*** alexpilotti has joined #openstack-oslo18:02
*** zzzeek has quit IRC18:03
*** zzzeek has joined #openstack-oslo18:05
*** arnaud has joined #openstack-oslo18:19
*** harlowja_away is now known as harlowja18:26
*** SridharG has quit IRC18:28
*** Alexei_987 has joined #openstack-oslo18:34
morganfainbergso are we maintaining the incubator for a given release (e.g. stable/XXX) with the expectation that projects will sync on the stable tree?18:38
morganfainbergfor their matching stable tree that is?18:38
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: port ds_util from nova to oslo.vmware  https://review.openstack.org/11455118:39
dhellmannmorganfainberg: yes, in case we find critical bugs in pieces that are still in the incubator18:40
morganfainbergdhellmann, cool.18:41
morganfainbergdhellmann, just checking :)18:41
dimsdhellmann: need some stevedore help...getting this exception - http://paste.openstack.org/show/96964/18:42
dimswhen i enable lines 167-171 in https://review.openstack.org/#/c/114551/6/oslo/vmware/selector.py,unified18:43
dimsplease take a look and let me know. brb18:43
dhellmanndims: it looks like the "policy" variable being passed in from the test is None18:43
dhellmanndims: that needs to be a name of a valid plugin from the 'selector.drivers' namespace18:44
dhellmanndims: I'm not sure that's a very good namespace, fwiw, it doesn't say anything about openstack or oslo or vmware in the name18:44
dimsah duh. thanks! i had set the default value to largest and forgot :)18:44
*** pblaho has quit IRC18:44
dimsdhellmann: y, just toying with it i had it with oslo.vmware earlier18:44
dhellmanndims: ah18:45
dimswhew! thanks18:45
dhellmanndims: https://pypi.python.org/pypi/entry_point_inspector18:45
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: port ds_util from nova to oslo.vmware  https://review.openstack.org/11455118:47
*** mrda-away is now known as mrda18:56
*** jecarey has quit IRC19:04
*** noelbk has quit IRC19:07
*** arnaud has quit IRC19:09
*** ildikov has joined #openstack-oslo19:16
dimsdhellmann: thanks19:26
*** pblaho has joined #openstack-oslo19:28
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: port ds_util from nova to oslo.vmware  https://review.openstack.org/11455119:30
*** jecarey has joined #openstack-oslo19:39
openstackgerritA change was merged to openstack/oslo.db: Handle DB2 SmallInteger type for change_deleted_column_type_to_boolean  https://review.openstack.org/11203019:42
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: VMWare: Support for pluggable Datastore selection  https://review.openstack.org/11455119:43
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: VMWare: Support for pluggable Datastore selection  https://review.openstack.org/11455119:44
*** kgiusti has joined #openstack-oslo19:47
*** shakayumi has quit IRC19:53
dimsbnemec: ping19:55
*** tsekiyam_ has joined #openstack-oslo19:55
*** gpocente1 has joined #openstack-oslo19:57
*** AAzza_afk is now known as AAzza19:58
*** kgiusti has quit IRC19:58
*** tsekiyama has quit IRC19:58
*** viktors|afk has quit IRC19:58
*** mriedem has quit IRC19:58
*** gpocentek has quit IRC19:58
*** mriedem has joined #openstack-oslo19:59
*** viktors has joined #openstack-oslo19:59
*** kgiusti has joined #openstack-oslo19:59
*** pblaho has quit IRC20:00
*** pcm__ has quit IRC20:01
*** pcm_ has joined #openstack-oslo20:02
*** noelbk has joined #openstack-oslo20:04
dimsdhellmann: we'll need a version of oslo.i18n with the test fixtures for use with oslo.serialization (https://review.openstack.org/#/c/113347/ is stuck because of that)20:15
*** linkid has left #openstack-oslo20:17
openstackgerritA change was merged to openstack-dev/oslo-cookiecutter: Add common fixes for docs generation to template  https://review.openstack.org/11466720:25
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo-incubator: Fix MemcachedKeyCharacterError when keys have spaces  https://review.openstack.org/11353720:28
dhellmannmarkmc, flaper87|afk, jd__, dims, bnemec : can you take a look at the osprofiler spec? it seems to have a lot of support outside of oslo, but I'd like some feedback from inside, too: https://review.openstack.org/#/c/105096/20:34
jd__I suggest a mail so I don't forget because it's late here20:35
dhellmanndims: so we just need to cut a release?20:35
dhellmannjd__: sure20:35
jd__thanks :)20:35
dimsdhellmann: yes please20:35
dhellmanndims: ok20:36
dimsjd__: can you please look at https://review.openstack.org/#/c/114614/ - need that to get oslo.utils into nova etc20:36
*** kevinbenton has joined #openstack-oslo20:40
*** jeckersb is now known as jeckersb_gone20:40
kevinbentondhellmann: ping regarding a neuron CLI fix i’m working on. markmcclain sent me your way20:41
kevinbentondhellmann: (sorry if you got that twice, first contacted you in infra)20:41
dimsdhellmann: review #? (curious)20:42
dhellmannhi, kevinbenton20:43
dhellmanndims: I'm not sure what you mean?20:43
dimsoops kevinbenton: review #? :)20:44
dhellmanndims: heh, ok, me, too :-)20:44
dims:)20:44
kevinbentondhellmann: hi, we ran into an issue where the —timeout parameter was used by both the top-level neutron command and one of the subcommands. argparse would always eatup the timeout parameter for the top-level command20:44
kevinbentonhttps://review.openstack.org/#/c/114005/20:44
kevinbentondhellmann, dims: ^^20:44
kevinbentonso that fixes it, but at the cost of not being able to specify any params to the top-level neutron command after the subcommand20:45
dhellmannkevinbenton: so the app value and the subcommand value use the same option name but mean different things?20:45
kevinbentondhellmann: yes, load balancer creating a watcher with the timeout param is referring to the object20:45
kevinbentondhellmann: top-level timeout is just for the command timeout20:45
dhellmannkevinbenton: frankly, I would change one of the option names to avoid confusion on the part of the user20:46
dhellmannkevinbenton: if the subcommand option isn't being honored now, then nothing can be relying on it and it's safe to change that one to something else (--watcher-timeout ?)20:46
kevinbentondhellmann: actually the top-level one just merged and broke the subcommand20:47
kevinbentondhellmann: so i’ll rename the top-level one20:47
dhellmannkevinbenton: ah, well, if you haven't released, then I'd roll that back20:47
kevinbentondhellmann: we also revealed a hole in the unit tests :-)20:47
dhellmannkevinbenton: sounds like it20:48
kevinbentondhellmann: do you think this patch is still worth looking into or should we even support duplication of option names?20:48
dhellmannkevinbenton: duplicating option names feels like a bad idea, since the user then has to be careful about how they order their command line20:49
kevinbentondhellmann: ok20:51
kevinbentondhellmann: thanks for your help20:51
dhellmannkevinbenton: sure thing20:51
*** kgiusti has left #openstack-oslo20:53
*** AAzza is now known as AAzza_afk20:54
*** arnaud has joined #openstack-oslo20:55
*** miqui has quit IRC20:55
Alexei_987dhellmann: Hi could you please revisit this spec when you'll have time? https://review.openstack.org/#/c/105796/20:57
*** ihrachyshka has joined #openstack-oslo21:02
*** bknudson has quit IRC21:03
bnemecdims: Sorry, missed your ping somehow.21:03
bnemecdhellmann: Will try to take a look asap.21:03
*** arnaud has quit IRC21:03
dhellmannbnemec: thanks21:04
*** ihrachyshka has quit IRC21:04
*** yamahata has joined #openstack-oslo21:04
*** ihrachyshka has joined #openstack-oslo21:04
dimsbnemec: need help with https://review.openstack.org/#/c/114614/21:05
bnemecdims: Okay, will try to hit that one too :-)21:06
dimsthanks bnemec21:06
dhellmannAlexei_987: I think I'm still not getting the point of that proposal. The point of the executor is to hold the loop and manage receiving messages and calling the dispatcher. If you move that to the server, then you've got information about the execution model (threading or not) in the server and in the executor, since the eventlet stuff is left behind.21:08
Alexei_987dhellmann: please see my comment regarding different drivers.. they usually contain their own main loop21:08
Alexei_987dhellmann: server uses it's own thread to receive messages21:09
dhellmannAlexei_987: and so they could provide their own executor, no?21:09
Alexei_987dhellmann: it's not how it happens in practice21:09
Alexei_987dhellmann: now we have a bridge between 2 loops21:09
Alexei_987dhellmann: we have it in 0MQ driver and proposed AMQP1.0 driver21:10
dhellmannAlexei_987: is that by design, or is that an artifact of us not having updated all of the drivers fully when we moved to the new public API for oslo.messaging?21:10
Alexei_987dhellmann: from my POV it's an artifact of legacy design21:10
Alexei_987dhellmann: in any case main loop in executor doesn't prevent us from using eventlet21:10
dhellmannAlexei_987: so rather than throwing out the new design, why not update the drivers?21:10
*** gordc has quit IRC21:11
Alexei_987main loop in server*21:11
Alexei_987dhellmann: update drivers to provide their own executor?21:11
dhellmannAlexei_987: we *want* the choice to use eventlet to be explicit, that's why we put it in a separate plugin layer21:11
Alexei_987dhellmann: it still remains the same21:11
Alexei_987dhellmann: we can use blocking executor or eventlet executor21:12
dhellmannAlexei_987: what remains the same?21:12
Alexei_987dhellmann: choice21:12
dhellmannAlexei_987: if it's the same, what's the point?21:12
Alexei_987dhellmann: main loop is moved to server...21:12
dhellmannAlexei_987: As I said, I think I'm missing something about the motivation for this change.21:12
Alexei_987dhellmann: this allows us to remove bridge between 2 loops21:12
Alexei_987dhellmann: and implement driver in a more efficient way21:12
dhellmannAlexei_987: why not remove that and leave the loop in the executor?21:13
Alexei_987dhellmann: + it simplifies executor cause it doesn't have to care about connections and poolinng21:13
Alexei_987dhellmann: to remove the bridge without moving loop 2 server we'll need driver to provide their own executors21:13
dhellmannAlexei_987: that layer does become simple if you move all of the work it's doing into another layer, but that doesn't seem like a good reason to move it21:13
dhellmannAlexei_987: if the driver has to provide its own server or its own executor, what's the difference?21:14
Alexei_987dhellmann: now we have 2 executors - blocking + eventlet21:14
Alexei_987driver will have to implement both21:14
dhellmannno21:14
Alexei_987why not?21:14
dhellmannbecause deciding whether to use threads or eventlet or block is the job of the executor21:15
*** markmc has quit IRC21:15
Alexei_987dhellmann: yes and we say that driver will provide it's own executor21:15
dhellmannthe driver shouldn't worry about that21:15
Alexei_987exactly21:15
dhellmannAlexei_987: well, they don't care about it now, do they?21:15
Alexei_987dhellmann: cause of the bridge between 2 main loops21:15
*** dims has quit IRC21:15
dhellmannok21:15
Alexei_987I move receiving messages to server and dispatching messages stays in executor21:16
Alexei_987cause driver knows how to receive messages21:16
Alexei_987and executor knows about how to dispatch them21:16
Alexei_987and right now executor does both things21:16
dhellmannyou really need to be convincing the maintainers of the library, not me. I may just be asking dumb questions. I would like to hear what they say, and what haypo says about how this would affect the plans to get rid of eventlet and use asyncio in python 3.21:16
Alexei_987IMHO this will help a lot21:17
Alexei_987cause it makes executors simpler21:17
Alexei_987(by moving receiving logic to driver21:17
Alexei_987dhellmann: I'm explaining this cause I have -1 on spec so I'm trying to answer questions you've had21:18
dhellmannAlexei_987: maybe you can add some of this to the spec, then, and get them to take a look. It's not solely up to me, and I asked questions that it seems like you can answer without waiting.21:18
dhellmannAlexei_987: it's likely I'm just not seeing something because I'm not an expert on this particular library21:19
Alexei_987dhellmann: I'm not sure what is the best way to attract attention to this spec21:20
dhellmannAlexei_987: I would start by answering the existing questions in the text of the spec, which will give you a new draft without a -1. Then you can ask some of the contributors to oslo.messaging to look at the updated draft.21:22
Alexei_987dhellmann: I think that right now It maybe more usefull to focus on functional + performance tests21:22
Alexei_987dhellmann: what do you think?21:22
dhellmanntests not related to this spec?21:22
Alexei_987dhellmann: no.. however it would be easier to land such patches21:23
Alexei_987dhellmann: cause functional tests will make sure that nothing is broken21:23
Alexei_987and performance test will display positive impact of changes21:23
Alexei_987dhellmann: should I also put comments and discussions in spec text?21:25
dhellmannAlexei_987: Well, there was some sort of thought put into the existing design that you want to change, so I would like to see that addressed when you give reasons for changing it. Maybe the design is bad, but maybe it meets requirements you're not seeing. So before you spend a lot of time working on code or tests, I would like to make sure there is some amount of agreement about the new approach being OK.21:26
Alexei_987dhellmann: well tests will be for existing design21:26
*** dims has joined #openstack-oslo21:26
dhellmannAlexei_987: that's why we go through the spec process21:26
Alexei_987dhellmann: so it's definitely worth spending some time on such things21:26
dhellmannAlexei_987: if you want to write tests, that's fine, I just don't think it's a way to prove your new approach is better21:26
Alexei_987dhellmann: well if my approach will allow to implement driver that is working much faster with the same functionality it's not enough?21:27
Alexei_987dhellmann: I don't think that current design is intended to be terribly slow on purpose21:28
dhellmannAlexei_987: no, of course not, but it was intended to have different layers responsible for different parts of the operation21:28
dhellmannAlexei_987: I need to go.21:28
Alexei_987dhellmann: ok thanks for your time21:28
openstackgerritA change was merged to openstack/oslo.concurrency: Fix docs generation  https://review.openstack.org/11464721:42
*** dims has quit IRC21:43
*** dims has joined #openstack-oslo21:43
*** dims has quit IRC21:48
* bnemec hopes we never have a bug in mask_password.21:58
bnemecThe number of regexes has gotten so large that tracking down which one is causing a problem would be a nightmare. :-)21:58
Alexei_987bnemec: why not adding some kind of subclass for private data?21:59
Alexei_987bnemec: polymorphism would be able to handle it all22:00
bnemecAlexei_987: They're already private.  I just suspect we've got some overlap in them and I doubt anyone actually understands what each one is doing anymore.22:01
Alexei_987bnemec: I mean that password would be some special type and it would not be printed22:01
*** stevemar2 has joined #openstack-oslo22:02
bnemecAlexei_987: We don't have control over that.  This is for masking passwords out of arbitrary strings.22:02
*** zzzeek_ has joined #openstack-oslo22:03
*** pcm_ has quit IRC22:04
bnemecIt might be interesting to see if we could convince the other projects to use a special object for password strings though.22:04
bnemecNot 100% sure it would work in a way they'd like.22:04
Alexei_987bnemec: It would be quite logical for auth_tokens for example22:05
*** dims has joined #openstack-oslo22:07
*** ihrachyshka has quit IRC22:08
*** dims_ has joined #openstack-oslo22:08
*** stevemar2 has quit IRC22:09
*** toabctl_ has joined #openstack-oslo22:10
*** krotscheck_ has joined #openstack-oslo22:10
*** sheeprine has quit IRC22:11
*** toabctl has quit IRC22:11
*** zzzeek has quit IRC22:11
*** stevemar has quit IRC22:11
*** krotscheck has quit IRC22:11
*** sheeprine has joined #openstack-oslo22:11
*** sheeprine has quit IRC22:11
*** sheeprine has joined #openstack-oslo22:11
*** zzzeek_ is now known as zzzeek22:11
*** toabctl_ is now known as toabctl22:11
*** krotscheck_ is now known as krotscheck22:11
*** dims has quit IRC22:12
amrithdhellmann, yt?22:30
*** jecarey has quit IRC22:37
openstackgerritamrith proposed a change to openstack/oslo.concurrency: Mask passwords in exceptions and error messages  https://review.openstack.org/11465622:38
amrithdhellmann, https://review.openstack.org/#/c/114656/ is ready for you to re-review. Thx22:39
*** dims_ has quit IRC22:42
*** arnaud has joined #openstack-oslo22:43
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: VMWare: Support for pluggable Datastore selection  https://review.openstack.org/11455122:44
openstackgerritAlexei Kornienko proposed a change to openstack/oslo.messaging: Moved all tests to unit folder.  https://review.openstack.org/11513622:45
openstackgerritAlexei Kornienko proposed a change to openstack/oslo.messaging: Added functional test for RPC  https://review.openstack.org/11513722:45
*** ajo has quit IRC22:47
*** arnaud__ has joined #openstack-oslo22:48
*** ajo has joined #openstack-oslo22:49
*** mriedem has left #openstack-oslo22:50
*** alexpilotti has quit IRC22:50
*** zzzeek has quit IRC22:53
*** zzzeek has joined #openstack-oslo22:53
*** zzzeek has quit IRC22:53
*** yamahata has quit IRC23:20
*** alexpilotti has joined #openstack-oslo23:26
*** bknudson has joined #openstack-oslo23:32
openstackgerritA change was merged to openstack/oslo.messaging: Sync jsonutils from oslo-incubator  https://review.openstack.org/11445423:54

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