Tuesday, 2014-07-29

openstackgerritA change was merged to openstack/pycadf: Updated from global requirements  https://review.openstack.org/10657200:00
*** dims_ has quit IRC00:03
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Implement a dialect-level function dispatch system  https://review.openstack.org/10943600:16
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017000:16
zzzeekthat’s a big one00:21
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017000:24
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017000:31
*** zzzeek has quit IRC00:41
*** nacim has quit IRC01:17
*** jecarey has joined #openstack-oslo01:25
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Allow endpoints to be fetched from factories  https://review.openstack.org/11018101:52
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Allow endpoints to be fetched from factories  https://review.openstack.org/11018102:00
*** yamahata has quit IRC02:16
*** penguinRaider__ has quit IRC02:49
*** praneshp has joined #openstack-oslo02:51
*** penguinRaider__ has joined #openstack-oslo02:52
*** praneshp_ has joined #openstack-oslo02:54
*** praneshp has quit IRC02:56
*** praneshp_ is now known as praneshp02:56
*** harlowja is now known as harlowja_away03:07
*** harlowja_away is now known as harlowja03:08
*** jecarey has quit IRC03:32
*** amotoki has joined #openstack-oslo03:55
*** SridharG has joined #openstack-oslo04:15
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Allow endpoints to be fetched from factories  https://review.openstack.org/11018104:25
*** HenryG is now known as HenryG_afk04:45
*** morganfainberg is now known as morganfainberg_Z04:59
*** harlowja is now known as harlowja_away05:26
*** ildikov has quit IRC05:34
*** jaosorior has joined #openstack-oslo05:42
*** jraim has quit IRC06:00
*** zhiyan has quit IRC06:00
*** harlowja_at_home has joined #openstack-oslo06:00
*** jraim__ has joined #openstack-oslo06:05
*** zhiyan has joined #openstack-oslo06:05
*** zhiyan has quit IRC06:23
*** jraim__ has quit IRC06:24
*** noelbk has quit IRC06:25
*** zhiyan has joined #openstack-oslo06:28
*** jraim__ has joined #openstack-oslo06:28
*** ildikov has joined #openstack-oslo06:33
*** viktors|afk has quit IRC06:36
*** harlowja_at_home has quit IRC06:38
*** pblaho has joined #openstack-oslo06:42
*** SridharG has quit IRC06:56
*** SridharG has joined #openstack-oslo07:00
*** SridharG has quit IRC07:06
*** flaper87|afk is now known as flaper8707:26
*** ihrachyshka has joined #openstack-oslo07:46
gusurgh.  mysqlconnector doesn't accept execute("sql stmt1; sql stmt 2"), and the sqlalchemy docs are unclear on whether that should be allowed or not :/07:49
*** ihrachyshka has quit IRC07:50
*** ihrachyshka has joined #openstack-oslo07:50
guszzzeek: ^  is this a user error, or should dialects/mysqlconnector.py be fixed to use cursor.execute(multi=True)?07:51
*** nacim has joined #openstack-oslo08:02
openstackgerritChristian Berendt proposed a change to openstack/oslo-incubator: Remove usage of readlines()  https://review.openstack.org/11022808:02
*** i159 has joined #openstack-oslo08:03
*** praneshp has quit IRC08:22
openstackgerritIlya Pekelny proposed a change to openstack/oslo.db: oslo.db.exceptions module documentation  https://review.openstack.org/9343508:27
haypowin 308:32
openstackgerritRoman Podoliaka proposed a change to openstack/oslo.db: Implement a dialect-level function dispatch system  https://review.openstack.org/10943608:42
*** Alexei_987 has joined #openstack-oslo08:50
openstackgerritTim Kelsey proposed a change to openstack/oslo.messaging: Adds message security plugins  https://review.openstack.org/10980608:56
*** ajo has joined #openstack-oslo08:58
openstackgerritA change was merged to openstack/oslo.db: oslo.db.api module documentation  https://review.openstack.org/9343409:16
openstackgerritA change was merged to openstack/oslo.db: Updated from global requirements  https://review.openstack.org/11010509:20
openstackgerritTim Kelsey proposed a change to openstack/oslo.messaging: Adds message security plugins  https://review.openstack.org/10980609:28
openstackgerritA change was merged to openstack/oslo.db: Specify raise_on_warnings=False for mysqlconnector  https://review.openstack.org/10722109:35
*** Alexei_987 has quit IRC09:37
openstackgerritOleksii Chuprykov proposed a change to openstack/oslo.db: Add create_database_permission_exist function  https://review.openstack.org/10925909:49
*** alexpilotti has joined #openstack-oslo10:19
*** Alexei_987 has joined #openstack-oslo10:27
openstackgerritA change was merged to openstack/oslo-incubator: Updated from global requirements  https://review.openstack.org/11010410:29
*** pcm_ has joined #openstack-oslo10:36
*** pcm__ has joined #openstack-oslo10:37
*** pcm_ has quit IRC10:41
*** HenryG_afk is now known as HenryG10:53
*** pblaho has quit IRC11:06
*** pcm__ has quit IRC11:14
*** pcm_ has joined #openstack-oslo11:15
ihrachyshkaI wonder whether there are plans for a new oslo.db version11:21
*** GheRiver1 is now known as GheRivero11:32
*** nacim has quit IRC11:35
*** pblaho has joined #openstack-oslo11:36
*** nacim has joined #openstack-oslo11:37
*** SridharG has joined #openstack-oslo11:49
*** SridharG has quit IRC12:03
*** nacim has quit IRC12:23
*** nacim has joined #openstack-oslo12:26
*** ihrachyshka_ has joined #openstack-oslo12:30
*** ihrachyshka_ has quit IRC12:31
*** ihrachyshka_ has joined #openstack-oslo12:32
*** ihrachyshka has quit IRC12:32
*** gordc has joined #openstack-oslo12:41
*** ihrachyshka__ has joined #openstack-oslo12:56
*** lbragstad has joined #openstack-oslo12:57
*** ihrachyshka_ has quit IRC12:59
*** pblaho_ has joined #openstack-oslo13:03
*** pblaho has quit IRC13:03
*** dims has joined #openstack-oslo13:31
*** bknudson has joined #openstack-oslo13:41
*** jokke__ is now known as jokke_13:53
*** lbragsta_ has joined #openstack-oslo13:56
*** lbragsta_ has quit IRC13:57
*** lbragsta_ has joined #openstack-oslo13:58
*** lbragstad has quit IRC13:58
openstackgerritJulien Danjou proposed a change to openstack/oslo-incubator: network_utils: make tests portable  https://review.openstack.org/11029314:04
openstackgerritJulien Danjou proposed a change to openstack/oslo-incubator: log: make tests portable  https://review.openstack.org/11029714:07
*** pblaho_ has quit IRC14:09
openstackgerritJulien Danjou proposed a change to openstack/oslo-incubator: network_utils: make tests portable  https://review.openstack.org/11029314:15
*** dhellmann has quit IRC14:17
*** dhellmann has joined #openstack-oslo14:20
*** ildikov has quit IRC14:22
*** ihrachyshka__ is now known as ihrachyshka14:24
ihrachyshkai159: am I right that you're somehow involved in oslo.db?14:24
*** ajo has quit IRC14:24
i159ihrachyshka: Hi. Yes I'am. I'm a member of Mirantis oslo.db team.14:26
ihrachyshkagood, great. so I have a question to an expert then :)14:26
ihrachyshkaI'm working on mysqldb -> mysqlconnector switch14:26
ihrachyshkasome of projects require changes here and there in migration rules14:27
*** ajo has joined #openstack-oslo14:27
ihrachyshkanow I'm struggling with glance14:27
ihrachyshkaand it fails with (InterfaceError) Use multi=True when executing multiple statements when a glance migration rule is attempted14:27
ihrachyshkathe rule is not a python script, but a SQL file14:27
ihrachyshkasee: https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/migrate_repo/versions/006_mysql_upgrade.sql14:28
ihrachyshkamy question is 1) WTF (other projects don't have those)14:28
ihrachyshka2) what to do with it? it fails inside /usr/lib/python2.7/site-packages/migrate/versioning/script/sql.py, where the contents of the file is executed on cursor14:29
ihrachyshkaI guess we could modify that migrate library to pass multi=True, but 1) it does not belong to openstack 2) I don't know whether this multi=True thing is portable14:29
ihrachyshkai159: ^^14:30
*** dims has quit IRC14:31
*** amotoki has quit IRC14:34
gordcdhellmann: was wondering, is there something special that needs to be done to get oslo.config/messaging>=1.4.0.0a3 to work? i get distributions not found errors when i run unit tests14:36
i159ihrachyshka: I think your problem is glance-migrate specific. multi=True is multi databases mode, I think so. I never had a deal with multi=True mode, so I'm sorry, I can't help you. You can ping rpodolyaka or zzzeek, they are muuuuch more experienced than me and it is possible that they can help you.14:39
ihrachyshkamulti=True is for 'allow multiple statements being executed in one go'14:40
ihrachyshkarpodolyaka1: ^^14:40
ihrachyshkai159: thanks anyway :)14:40
ihrachyshkayeah, I also think it's glance specific. we don't generally execute pre-crafted mysql scripts14:41
rpodolyaka1ihrachyshka: hmm, interesting14:43
rpodolyaka1ihrachyshka: I think, multi database mode is a red herring, but what we have here is that we pass a few SQL statements to cursor.execute() call14:44
rpodolyaka1ihrachyshka: somehow, it raises a warning with mysqlconnector DB API driver14:44
rpodolyaka1InterfaceError: (InterfaceError) Use multi=True when executing multiple statements 'select 1; select 2;' {}14:45
rpodolyaka1In [7]: eng.execute('select 1; select 2;')14:45
ihrachyshkait comes from really old times: https://github.com/openstack/glance/commit/a2c9a1eb5ce3b5abd650811ad9c97d5aa307af8a14:45
rpodolyaka1ihrachyshka: ^^14:45
ihrachyshkarpodolyaka1: is it connector issue?14:46
rpodolyaka1In [11]: eng = sa.create_engine('mysql://root:devel@localhost/devel')14:46
rpodolyaka1In [12]: eng.execute('select 1; select 2;')14:46
rpodolyaka1Out[12]: <sqlalchemy.engine.result.ResultProxy at 0x7f7cc8c593d0>14:46
rpodolyaka1this is with mysql-python14:46
rpodolyaka1ihrachyshka: I'm not sure, it's a bug, it might also be a feature :P14:47
rpodolyaka1ihrachyshka: I'd ask on mysqlconnector irc channel, if they have one :)14:47
ihrachyshkalooks like a feature, they have a special handling for this in their code :)14:47
ihrachyshkathey don't, that's a problem :)14:48
ihrachyshkathough I can reach the author thru email14:48
ihrachyshkaI'll probably go that route14:48
*** tsufiev has quit IRC14:55
dhellmanngordc: you might need a newer version of tox/virtualenv/pip -- let me know if you're still having issues14:58
dhellmannrpodolyaka1, ihrachyshka : is that flag for multiple SQL statements in one call vs. multiple databases?14:59
gordcdhellmann: hmm. ok, i'll give that a try14:59
rpodolyaka1dhellmann: for multiple SQL statements14:59
dhellmanngordc: which versions do you have installed?15:00
ihrachyshkadhellmann: yes15:00
dhellmannrpodolyaka1: interesting. seems like something we should support.15:00
gordctox==1.6.1, pip==1.5.615:00
ihrachyshkadhellmann: yeah, otherwise we need to modify projects like in https://review.openstack.org/#/c/110271/15:00
rpodolyaka1dhellmann: it seems this is mysqlconnector DB API driver specific, as we haven't seen this issue so far (we've been testing mysql-python/psycopg2/pysqlite drivers)15:01
*** tsufiev_ has joined #openstack-oslo15:01
*** morganfainberg_Z is now known as morganfainberg15:01
gordcdhellmann: venv==1.10.115:02
dhellmannrpodolyaka1: so those other connectors don't accept this option, or the default is different?15:02
ihrachyshkarpodolyaka1: well, we could make our library more smart and handling that case for us, passing multi=True when needed (?)15:02
ihrachyshkadhellmann: I guess the former, but need to check15:02
dhellmanngordc: I'm on 1.11.2 in at least one project, so maybe that's it then15:03
dhellmannihrachyshka: ok15:03
gordcdhellmann: ok, i'll try updating venv15:04
*** tsufiev_ has quit IRC15:05
*** tsufiev_ has joined #openstack-oslo15:06
gordcdhellmann: yep, that fixed it. thanks!15:06
dhellmann\o/15:06
*** tsufiev_ has quit IRC15:07
*** jecarey has joined #openstack-oslo15:07
ihrachyshkadhellmann: yeah, doesn't look like mysql-python has it: https://github.com/arnaudsj/mysql-python/blob/master/MySQLdb/cursors.py15:07
dhellmannihrachyshka: so we need our own connector compatibility layer?15:08
ihrachyshkadhellmann: maybe, I don't know whether it would be easier to fix that case by case though, as in the patch I've posted above15:08
dhellmanngordc: did you write a spec for the oslo.middleware graduation?15:08
*** tsufiev has joined #openstack-oslo15:09
ihrachyshkadhellmann: I've sent an email to the author of connector to see how he feels about that15:10
*** lbragsta_ is now known as lbragstad15:10
dhellmannihrachyshka: I think we'll be better off if we can make oslo.db adapt to the projects as they are now, without having to change them15:11
ihrachyshkadhellmann: for that specific issue, we already have some relevant hack inside migrate library for sqlite: https://github.com/stackforge/sqlalchemy-migrate/blob/master/migrate/versioning/script/sql.py#L3715:11
gordcdhellmann: i want to say yes, but i can't find any... should i write one up? and i guess another for notifiermiddleware?15:11
dhellmanngordc: yes, please -- I just approved the wrong bp, realized my mistake, went to look for the spec for the other to use the tool to do it (instead of doing it all by hand again), and didn't find one15:12
gordcdhellmann: ok. will do a quick write up15:13
dhellmanngordc: I'll go ahead and target the bp, but if you could get a spec put together this week that would let me approve it before my next sync with ttx15:13
gordcdhellmann: will do15:13
dhellmanngordc: thanks!15:13
jd__gordc: did you port/integrate the notifier middleware in oslo.middleware?15:14
jd__I think it was missing in your original porting15:14
jd__s/porting/run of graduate.sh/15:14
*** nacim has quit IRC15:14
ihrachyshkadhellmann: is that migrate library handled by oslo?15:14
gordcjd__: no. i believe in original discussion with dhellmann we wanted to keep notifier middleware separate so we didn't have to bring in oslo.messaging into middleware lib15:15
jd__haha15:15
jd__and dhellmann just commented that we may not want to put the notifier middleware in oslo.messaging either15:15
jd__so WAT?15:16
dhellmannihrachyshka: no, sqlalchemy-migrate isn't owned by oslo15:16
gordcjd__: yeah, we're going to have it as a lib by itself15:16
ihrachyshkadhellmann: but still, it's under stackforge (?)15:16
jd__I don't really like that idea15:16
jd__like we already have largely enough repository/packages15:17
jd__:/15:17
dhellmannjd__, gordc : yeah, the dependencies there were tricky, but we've been merging some of the other libs I thought we needed to keep together. If you can work out how to have them all in one place, that's fine, just write it up. :-)15:17
dhellmann^keep together^keep apart15:17
dhellmannI didn't want oslo.messaging to require webob, and I wasn't sure about the middleware library requiring oslo.messaging. :-/15:17
gordcjd__, dhellmann, is the webob package big? i would think it'd be best to move the notifier middleware into which lib that brings in smaller dependency15:19
dhellmanngordc: I would have to look at the dependency list, but you might be right.15:20
jd__gordc: I'd say webob is lighter than oslo.messaging actually, wdyt dhellmann?15:30
openstackgerritIlya Pekelny proposed a change to openstack/oslo.db: oslo.db.exceptions module documentation  https://review.openstack.org/9343515:31
gordcjd__: yeah, that's what i think as well... if that's the case, i'm ok to with your initial patch for moving notifiermiddleware to oslo.messaging if everyone else is cool with it.15:32
jd__the one I abandoned? /me cries15:33
*** zzzeek has joined #openstack-oslo15:38
dhellmannjd__: so oslo.messaging would depend on webob for that notifier? That might be OK. Are there any other dependencies?15:42
jd__dhellmann: no15:43
dhellmannjd__: ?15:44
jd__dhellmann: sorry, yes and no15:44
jd__cf the patches :)15:44
jd__https://review.openstack.org/#/q/status:open+project:openstack/oslo.messaging+branch:master+topic:bp/graduate-notifier-middleware,n,z15:44
openstackgerritJulien Danjou proposed a change to openstack/oslo.messaging: Import notifier middleware from oslo-incubator  https://review.openstack.org/10574615:44
openstackgerritJulien Danjou proposed a change to openstack/oslo.messaging: Import oslo-incubator context module  https://review.openstack.org/10574515:44
openstackgerritJulien Danjou proposed a change to openstack/oslo.messaging: Import oslo-incubator/middleware/base  https://review.openstack.org/10574415:44
*** ihrachyshka has quit IRC15:46
openstackgerritIlya Pekelny proposed a change to openstack/oslo.db: Utility function for robust schema drop  https://review.openstack.org/10641915:47
dhellmannjd__: ok, I'll leave it up to you and gordc to work out the right home and write up the spec for it. I don't expect to have time to review any of that until next week (I'm out for the next 3 days)15:47
jd__I don't want to write specs, I've already wrote the patches15:48
*** HenryG_ has joined #openstack-oslo15:48
jd__I say screw that bureaucracy15:48
jd__I'm starting #openstack-rebel15:48
i159zzzeek: Hi. Have you seen my pull request to sa?15:50
zzzeeki159: have I ever !15:51
i159zzzeek: is it ok?15:51
dhellmannjd__: you can write it once, or every time someone asks why we have the dependencies set up that way :-/15:51
zzzeeki159: i added lots of comments15:51
zzzeeki159: b.c. i know you like code reviews! :)15:52
* zzzeek loves code review15:52
*** HenryG has quit IRC15:52
* dhellmann has adopted the mantra "write it down"15:52
*** HenryG_ is now known as HenryG_afk15:52
*** HenryG_afk is now known as HenryG15:52
jd__dhellmann: nobody's gonna dare ask me that :p15:52
dhellmannhahahahahahaha15:52
jd__but yeah I'll write that at the bottom of my todo list15:52
i159zzzeek: oh, good! yes, I really like it. It can teach me a tricks that are not in books =)15:54
*** i159 has quit IRC15:55
openstackgerritgordon chung proposed a change to openstack/oslo-specs: graduate-oslo-middleware  https://review.openstack.org/11035316:01
openstackgerritgordon chung proposed a change to openstack/oslo-specs: graduate-oslo-middleware  https://review.openstack.org/11035316:03
gordcjd__: hey... soo.... you writing up at that spec? :)16:05
*** dims has joined #openstack-oslo16:08
*** SridharG has joined #openstack-oslo16:11
*** markmcclain has joined #openstack-oslo16:15
*** nacim has joined #openstack-oslo16:16
*** ildikov has joined #openstack-oslo16:19
gordczzzeek: when you have time, could you take a quick look at last comment: https://review.openstack.org/#/c/101009/16:22
zzzeekgordc: ok16:22
gordczzzeek: thanks!16:23
zzzeekgordc: oh is this back to what we talked about 2 months ago ?16:26
dimshowdy folks16:28
dimsdhellmann, ping16:28
gordczzzeek: yep... kind of an undestatment, but i procrastinate...16:28
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017016:29
*** gordc is now known as gordc_lunch16:32
*** yamahata has joined #openstack-oslo16:36
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017016:38
dimsdhellmann, i don't seem to have privileges to push tags - http://paste.openstack.org/show/88956/16:40
*** Alexei_987 has quit IRC16:41
dimsdhellmann, looks like i don't have oslo-ptl karma. can you please add me if appropriate16:48
*** dims has quit IRC16:49
*** dims has joined #openstack-oslo16:50
dimsdhellmann, looks like i don't have oslo-ptl karma. can you please add me if appropriate16:50
*** pblaho_ has joined #openstack-oslo16:52
dhellmanndims: done16:58
dimsthanks, looks like it is in progress16:59
*** tsekiyama has joined #openstack-oslo17:01
dhellmanndims: woo!17:02
dimsdhellmann, hmm, don't see oslo.utils on pypi17:04
*** SridharG has quit IRC17:04
dhellmanndims: did you not register the project? that has to be done by hand, first17:04
dimsdhellmann, i "inherited" oslo.utils and assumed it was there already. will register17:05
*** tsekiyama has quit IRC17:05
dhellmanndims: ok, that may mean tagging again as 0.1.117:06
dimsunderstood17:06
*** praneshp has joined #openstack-oslo17:06
dimsdhellmann, dropping email to the -dev list17:23
dhellmanndims: cool, thanks17:24
*** gmurphy has quit IRC17:26
*** gmurphy has joined #openstack-oslo17:29
*** harlowja_away is now known as harlowja17:36
*** gordc_lunch is now known as gordc17:48
*** tsekiyama has joined #openstack-oslo17:56
*** Alexei_987 has joined #openstack-oslo17:58
*** SridharG has joined #openstack-oslo18:04
*** markmcclain has quit IRC18:12
*** markmcclain has joined #openstack-oslo18:16
*** markmcclain1 has joined #openstack-oslo18:17
*** markmcclain has quit IRC18:21
harlowjawoot, oslo.utils, nice18:21
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017018:23
*** noelbk has joined #openstack-oslo18:41
*** pabelanger has joined #openstack-oslo18:43
pabelangerAre questions about oslo.messaging usage appropriate for this room?18:44
gordczzzeek: just to confirm, you would recommend building tables similar to api models, even if it means more duplicate data... (and assuming we have some performance baseline to reference)18:46
zzzeekgordc: I’d not recommend duplicate data unless a clear need is demonstrated18:46
zzzeekgordc: id go for normalized first18:47
zzzeeke.g. user_id is on resource18:47
gordczzzeek: ok, but our api model of 'Meter' also references a few resource attributes as well. so to build a meter we'd need meter->sample->resource18:49
zzzeekgordc: yeah, the prposed change you have in https://review.openstack.org/#/c/101009/8/specs/juno/big-data-sql-v2.rst w/ three tables looks OK to me18:49
*** gmurphy has quit IRC18:50
gordczzzeek: ok. i'll give that a try. i wasn't sure how much we should try to avoid joins... the one thing i remembered was joins can be a problem.18:50
zzzeekgordc: they can, but subqueries are worse18:51
zzzeekgordc: starting with normalized is always a good idea18:51
gordczzzeek: ah, got it. i'll give the proposal a try.18:51
gordczzzeek: thanks for the review18:51
zzzeekgordc: with MySQL you sometimes can get away with pulling a small table into a list of ids, then doing a second query with IN, that’s a last resort kind of thing18:51
zzzeekgordc: joins aren’t terrible in MySQL if subqueries aren’t used18:52
zzzeekgordc: we just need to do an EXPLAIN and see where the bottlenecks are18:52
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Implement a dialect-level function dispatch system  https://review.openstack.org/10943618:52
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017018:52
gordczzzeek: i see. i'll try building up proposed solution and see what EXPLAIN shows.18:52
zzzeekgordc: also INNER JOINs, vs. outer joins.  avoid outer joins18:53
gordczzzeek: yeah, i noticed that. i tried outer joins on another set of tables... that blew up.18:54
*** pblaho_ is now known as pblaho18:56
*** gmurphy has joined #openstack-oslo18:56
dhellmannpabelanger: yes19:12
pabelangerdhellmann, Thanks.  I think I figured out my question for the moment19:15
dhellmannpabelanger: even better :-)19:16
Alexei_987noelbk: Hi you can ping me here if needed19:31
*** lbragsta_ has joined #openstack-oslo19:31
Alexei_987noelbk: expiry fix is definetely better in terms of HA deployment since it doesn't cause any errors on the sender side so maybe we should combine both approaches19:32
*** lbragst__ has joined #openstack-oslo19:32
*** lbragst__ is now known as lbragstad_19:33
*** lbragsta_ has quit IRC19:33
noelbkAlexei_987: Yes, the expiry is good too for other cases where the receiver dies.  Let's do both.  My remaining task in mine is to get the server to time out if the client fails to recreate the reply queue19:34
Alexei_987noelbk: +1 sounds like a good plan19:34
*** lbragstad has quit IRC19:34
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Implement a dialect-level function dispatch system  https://review.openstack.org/10943619:35
noelbkAlexei_987: Could you make your expiry timeout a config variable?19:36
noelbkAlexei_987: I'm currently looking for how to wire a config variable in to the server reply timeout19:37
Alexei_987noelbk: Yeah you can mention it in patch. and we'll update it19:37
noelbkAlexei_987: I did mention the config variable in my comment to the expiry patch... did you mean mention it somewhere else?19:38
Alexei_987noelbk: oh sorry.. must have missed it19:38
Alexei_987noelbk: we'll update the patch19:38
noelbkAlexei_987: also the unit test, although my own test seems a little hackish19:38
Alexei_987noelbk: IMHO unit tests are useless for rabbit driver19:39
Alexei_987noelbk: we don't actually test anything19:39
Alexei_987noelbk: I'm working on functional tests19:39
noelbkAlexei_987: but making sure the right parameter gets passed to kombu is important19:39
noelbkAlexei_987: and protects against someone else breaking it later19:39
Alexei_987noelbk: IMHO it's much more important to test functionality19:40
Alexei_987noelbk: and not each parameter19:40
Alexei_987noelbk: functional tests for failover will cover that19:40
Alexei_987noelbk: we are using inmemory transport for kombu that is different from real rabbitmq19:41
Alexei_987noelbk: so unit test can pass and driver will still be broken19:41
*** gordc has quit IRC19:41
noelbkAlexei_987: point taken.  I prefer to add the unit test as well as functional.  Even though that doesn't really confirm that rabbit will behave the right way, it prevents someone from breaking things in a future pacth19:43
Alexei_987noelbk: Ok :)19:43
*** dims has quit IRC19:47
*** openstackgerrit has quit IRC19:48
dhellmanndims: https://review.openstack.org/#/c/107690/ takes care of adding oslo.utils to the governance repo for you19:50
noelbkAlexei_987: so, the timeout argument in publisher_send is pretty mu unused.  There's no timeout argument to ensure()19:51
*** lbragstad_ has quit IRC19:56
*** lbragstad has joined #openstack-oslo19:56
*** arnaud has joined #openstack-oslo19:56
*** lbragstad has quit IRC19:59
*** lbragstad has joined #openstack-oslo19:59
*** gordc has joined #openstack-oslo19:59
*** markmcclain1 has quit IRC19:59
*** markmcclain has joined #openstack-oslo20:00
*** dims has joined #openstack-oslo20:19
*** pblaho has quit IRC20:46
Alexei_987zzzeek: Hi are you available?20:46
*** lbragstad has quit IRC20:48
*** lbragstad has joined #openstack-oslo20:49
*** lbragstad has quit IRC20:53
*** openstackgerrit has joined #openstack-oslo20:58
zzzeekAlexei_987: whats up20:58
Alexei_987zzzeek: wanted to ask you about dogpile.cache21:02
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017021:02
zzzeekAlexei_987: yah21:02
Alexei_987zzzeek: we need to set socket timeout somehow21:02
Alexei_987for all cache operations21:02
zzzeekfor what backend21:02
Alexei_987zzzeek: and it seems that it depends on backend21:02
Alexei_987zzzeek: that's the question21:03
zzzeekAlexei_987: that is true21:03
zzzeekAlexei_987: not all backends have a timeout21:03
zzzeekAlexei_987: for example, dbm, memory21:03
Alexei_987zzzeek: ah.. I see so we need to do fix backend specific21:03
Alexei_987zzzeek: and ensure we use proper backend21:03
Alexei_987zzzeek: we are using memcached21:04
Alexei_987zzzeek: but it also has 3 different connectors21:04
zzzeekAlexei_987: OK, so not redis, and a single memcached python lib ?21:04
*** lbragstad has joined #openstack-oslo21:04
Alexei_987zzzeek: and only 1 supports timeout21:04
zzzeekAlexei_987: well all but pylibmc suck21:04
*** haypo has left #openstack-oslo21:04
zzzeekAlexei_987: id recommend stick with one backend, assuming its pylibmc :)21:05
Alexei_987zzzeek: from what I see it doesn't support timeout21:06
Alexei_987zzzeek: but maybe I'm wrong21:06
zzzeekAlexei_987: http://sendapatch.se/projects/pylibmc/behaviors.html21:06
*** lbragstad has quit IRC21:07
Alexei_987zzzeek: ah true21:07
zzzeekAlexei_987: connect_timeout, receive_timeout, send_timeout, timeouts galore21:07
Alexei_987zzzeek: I was looking in the wrong file :(21:07
Alexei_987zzzeek: thanks21:07
*** lbragstad has joined #openstack-oslo21:07
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Implement a dialect-level function dispatch system  https://review.openstack.org/10943621:08
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely.  https://review.openstack.org/11017021:09
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Use dialect dispatch for engine initiailization.  https://review.openstack.org/11044621:10
*** flaper87 is now known as flaper87|afk21:12
*** SridharG has quit IRC21:18
*** gordc has quit IRC21:49
*** lbragsta_ has joined #openstack-oslo21:51
*** lbragstad has quit IRC21:54
*** lbragsta_ has quit IRC21:55
*** HenryG is now known as HenryG_afk22:18
*** jaosorior has quit IRC22:22
*** jecarey has quit IRC22:25
*** bknudson has quit IRC22:30
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Use testr instance provisioning to lazily create databases  https://review.openstack.org/11048622:36
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Use testr instance provisioning to lazily create databases  https://review.openstack.org/11048622:38
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely  https://review.openstack.org/11017022:39
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Use testr instance provisioning to lazily create databases  https://review.openstack.org/11048622:39
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Use dialect dispatch for engine initiailization.  https://review.openstack.org/11044622:42
*** tsekiyam_ has joined #openstack-oslo22:43
*** tsekiyama has quit IRC22:47
*** tsekiyam_ has quit IRC22:48
openstackgerritDolph Mathews proposed a change to openstack/pycadf: revise readme with a project description  https://review.openstack.org/11049022:51
openstackgerritDolph Mathews proposed a change to openstack/pycadf: add CONTRIBUTING doc  https://review.openstack.org/11049122:53
*** arnaud has quit IRC23:04
*** alexpilotti has quit IRC23:05
openstackgerritDolph Mathews proposed a change to openstack/pycadf: clean up license headers  https://review.openstack.org/11049823:09
*** dims has quit IRC23:14
*** yamahata_ has quit IRC23:15
*** dims has joined #openstack-oslo23:16
*** dims is now known as Guest1391823:16
*** Guest13918 is now known as dims_23:17
*** dims_ has left #openstack-oslo23:19
*** bknudson has joined #openstack-oslo23:20
*** dims_ has joined #openstack-oslo23:20
*** bknudson has quit IRC23:25
guszzzeek: mysqlconnector doesn't accept execute("sql stmt1; sql stmt 2"), and the sqlalchemy docs are unclear on whether that should be allowed or not23:30
zzzeekthere was discusson of this somewhere, oh in an email.  there’s a silly flag the DBAPI wants to allow that.23:31
gusShould mysqlconnector use cursor.execute(multi=True), or should I track down and fix callers issuing multiple statements at once?23:31
zzzeekId go for the latter23:31
gusthe latter?23:31
zzzeekmutliple statemnts in execute() is pretty amateur23:31
gusack.23:31
zzzeek:)23:31
gusI'll go on a semicolon hunt :P23:31
zzzeekwe have to do it in *one* case, in the pyodbc SQL server driver23:31
gusoh wait, what?23:31
gusI found this in the context of mysqldb->mysqlconnector.23:32
zzzeekthats SQLAclhemy.  openstack deosnt work on SQL Server :)23:32
zzzeekyeah i know23:32
gusso mysqldb (and presumably postgres and anywhere else we've ever deployed keystone) apparently supports multiple statements.23:33
gusmysqlconnector does not.23:33
gus(and possibly other non-default driver choices)23:33
gusso where does pyodbc come into this?23:34
*** bknudson has joined #openstack-oslo23:34
gushttps://github.com/openstack/keystone/blob/master/keystone/common/sql/migrate_repo/versions/036_havana.py23:36
gus^ is the example of multiple statements I ran across first.23:36
zzzeekpyodbc comes into this b.c. wihtin all of sqlalchemy it is the only place where a “;” is unavoidable in one particular case23:37
gusaha.23:37
gus.. so does that mean mysqlconnector needs to be fixed to always use multi=True anyway?23:38
zzzeekno, why?23:40
zzzeekmysqlconnevtor has nothing to do with pyodbc23:40
gusoh ok - then I don't know how pyodbc and sqlalchemy interact (if at all) ;)23:41
zzzeekits one of many DBAPIs we support23:41
zzzeekin sqlalchemy23:41
gusoh right, as a backend driver - yeah that has nothing to do with mysqlconnector then.23:42
*** nacim has quit IRC23:42
gus.. so sqla's execute() only supports a single statement and I should fix any callers who try otherwise.  should be easy enough to exercise the migration paths with a fresh devstack install.23:43
*** HenryG_afk is now known as HenryG23:45

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