Tuesday, 2015-11-10

*** pm90_ has joined #openstack-oslo00:06
*** ndipanov has joined #openstack-oslo00:06
*** pm90_ has quit IRC00:14
*** achanda has joined #openstack-oslo00:16
*** jeckersb_gone is now known as jeckersb00:17
*** harlowja has joined #openstack-oslo00:20
*** achanda has quit IRC00:25
*** mtanino has quit IRC00:28
*** achanda has joined #openstack-oslo00:30
openstackgerritJoshua Harlow proposed openstack/tooz: Add programatic introspection of drivers capabilities  https://review.openstack.org/24068100:32
openstackgerritJoshua Harlow proposed openstack/tooz: Add decorator that can be used to ensure a driver is capable  https://review.openstack.org/24105600:33
*** dims_ has quit IRC00:33
*** rohit_ has joined #openstack-oslo00:33
*** jamielennox is now known as jamielennox|away00:33
*** dims has joined #openstack-oslo00:36
*** sputnik13 has quit IRC00:45
*** dims_ has joined #openstack-oslo00:51
*** dims has quit IRC00:51
*** _amrith_ is now known as amrith00:52
harlowjadims_ https://gist.github.com/harlowja/099cf904365d7fed31e7 was what i am starting to form to maybe get some new core recruits01:10
harlowjamission impossible themed ^ ;)01:10
harlowjarun like01:11
harlowja$ python maybe_oslo_core.py  "John" "Doe" "oslo.messaging"01:11
dims_harlowja nice! got a list of people too?01:11
harlowjacan do, gotta analyze that git-inspector report01:11
*** rjaiswal has quit IRC01:15
*** thumpba has joined #openstack-oslo01:16
*** thumpba has quit IRC01:18
*** achanda has quit IRC01:29
*** SurajD has joined #openstack-oslo01:32
harlowjaSpamapS ok, i referenced your tooz policy in https://review.openstack.org/#/c/209661/01:37
harlowjadenoted that your tooz policy spec will be the thing that decided if a tooz driver lives/dies (and/or what it must conform to)01:37
*** amrith is now known as _amrith_01:45
*** _amrith_ is now known as amrith01:46
*** yamamoto has joined #openstack-oslo01:53
openstackgerritJoshua Harlow proposed openstack/oslo.service: Avoid the dual-naming confusion  https://review.openstack.org/23871701:54
openstackgerritSuraj Deshmukh proposed openstack/oslo.utils: Added ICMP 'type' and 'code' checking capability to 'netutils' module  https://review.openstack.org/24066101:54
*** mc_nair has quit IRC01:54
SurajDCan somebody review this https://review.openstack.org/#/c/240661/01:55
*** pm90_ has joined #openstack-oslo02:00
openstackgerritJoshua Harlow proposed openstack/oslo.utils: Add useful 'time_it' decorator  https://review.openstack.org/23122002:00
openstackgerritDavanum Srinivas (dims) proposed openstack/oslo.messaging: Decouple transport for RPC and Notification  https://review.openstack.org/23325802:01
*** dims_ has quit IRC02:01
*** dims has joined #openstack-oslo02:05
*** SurajD has quit IRC02:05
openstackgerritMerged openstack/tooz: Updated from global requirements  https://review.openstack.org/23904802:06
*** SurajD has joined #openstack-oslo02:08
*** bana_k has quit IRC02:10
*** salv-orlando has joined #openstack-oslo02:12
*** yamamoto has quit IRC02:14
*** yamamoto has joined #openstack-oslo02:17
*** yamamoto has quit IRC02:21
*** SurajD has quit IRC02:22
*** ozamiatin has joined #openstack-oslo02:29
*** jamielennox|away is now known as jamielennox02:34
*** ozamiatin has quit IRC02:37
*** pm90_ has quit IRC02:42
*** rohit_ has quit IRC02:46
*** bapalm has quit IRC02:54
openstackgerritMerged openstack/oslo-specs: Add spec for tooz driver policy  https://review.openstack.org/24037302:54
*** thumpba has joined #openstack-oslo02:56
*** thumpba has quit IRC03:02
*** rjaiswal has joined #openstack-oslo03:02
*** bapalm has joined #openstack-oslo03:02
*** yamamoto has joined #openstack-oslo03:07
*** dims has quit IRC03:13
rjaiswaldims: https://review.openstack.org/#/c/243360/ for bumping up the requirements03:16
openstackgerritMerged openstack/oslo.versionedobjects: Ensure__repr__ return value is encoded  https://review.openstack.org/24296403:41
openstackgerritMerged openstack/oslo.messaging: Move supported messaging drivers in-tree  https://review.openstack.org/24060803:49
openstackgerritMerged openstack/oslo.privsep: Initial basic privsep functionality  https://review.openstack.org/23833303:58
*** links has joined #openstack-oslo03:59
*** salv-orlando has quit IRC03:59
*** mriedem_away has quit IRC04:05
*** david-lyle has joined #openstack-oslo04:07
*** thumpba has joined #openstack-oslo04:22
*** thumpba has quit IRC04:26
*** jerrygb has quit IRC04:28
openstackgerritOpenStack Proposal Bot proposed openstack/oslo.privsep: Updated from global requirements  https://review.openstack.org/24340504:33
*** jerrygb has joined #openstack-oslo04:36
*** amotoki has joined #openstack-oslo04:50
*** salv-orlando has joined #openstack-oslo05:01
*** jamielennox is now known as jamielennox|away05:01
*** jamespage has quit IRC05:05
*** salv-orlando has quit IRC05:05
*** jamespage has joined #openstack-oslo05:06
*** yamamoto_ has joined #openstack-oslo05:13
*** yamamoto has quit IRC05:15
*** jerrygb has quit IRC05:20
*** gcb has joined #openstack-oslo05:22
*** jerrygb has joined #openstack-oslo05:23
*** jerrygb has quit IRC05:23
openstackgerritAkihiro Motoki proposed openstack/oslo.config: Add maxlen check to StrOpt  https://review.openstack.org/24288005:49
*** ozamiatin has joined #openstack-oslo05:51
*** achanda has joined #openstack-oslo06:03
*** ig0r__ has quit IRC06:05
*** ig0r__ has joined #openstack-oslo06:10
*** bana_k has joined #openstack-oslo06:11
*** jerrygb has joined #openstack-oslo06:24
*** thumpba has joined #openstack-oslo06:24
*** jerrygb has quit IRC06:28
*** thumpba has quit IRC06:29
*** rjaiswal has quit IRC06:35
*** itisha has joined #openstack-oslo06:57
*** alexpilotti has joined #openstack-oslo07:15
*** nkrinner has joined #openstack-oslo07:20
*** bana_k has quit IRC07:21
*** jerrygb has joined #openstack-oslo07:25
*** thumpba has joined #openstack-oslo07:25
*** achanda has quit IRC07:27
*** jerrygb has quit IRC07:29
*** thumpba has quit IRC07:29
*** alexpilotti has quit IRC07:35
*** bana_k has joined #openstack-oslo07:37
*** openstackgerrit has quit IRC07:46
*** openstackgerrit has joined #openstack-oslo07:46
*** ozamiatin_ has joined #openstack-oslo07:48
*** ozamiatin has quit IRC07:51
*** zigo has quit IRC08:01
*** zigo has joined #openstack-oslo08:03
*** ozamiatin_ has quit IRC08:06
*** bana_k has quit IRC08:10
*** ozamiatin_ has joined #openstack-oslo08:22
*** browne has quit IRC08:22
*** ozamiatin_ has quit IRC08:22
*** jerrygb has joined #openstack-oslo08:26
*** jerrygb has quit IRC08:31
*** openstackgerrit has quit IRC08:31
*** openstackgerrit has joined #openstack-oslo08:31
*** ozamiatin_ has joined #openstack-oslo08:35
*** ozamiatin_ has quit IRC08:46
*** ozamiatin_ has joined #openstack-oslo08:56
*** achanda has joined #openstack-oslo08:57
*** achanda has quit IRC09:02
*** yassine has joined #openstack-oslo09:23
*** jerrygb has joined #openstack-oslo09:27
*** jerrygb has quit IRC09:32
*** ihrachys has joined #openstack-oslo09:35
*** achanda has joined #openstack-oslo10:00
*** achanda has quit IRC10:05
openstackgerritVladimir Eremin proposed openstack/oslo.config: [WIP] Support ZooKeeper and Consul for oslo.config  https://review.openstack.org/24318210:08
*** ozamiatin_ has quit IRC10:08
*** gcb has quit IRC10:09
openstackgerritMerged openstack/oslo.service: Forbid launching services with 0 or negative number of workers  https://review.openstack.org/24124010:22
*** ozamiatin has joined #openstack-oslo10:22
haypoi found 11 clients using cliutils.py (of oslo-incubator). on these 11 clients, 8 uses oslo.utils, but 3 (mistraclient, solumclient, tuskarclient) don't use oslo.utils yet10:22
haypowould it make sense to graduate cliutils.py to oslo.utils?10:22
*** jamielennox|away is now known as jamielennox10:24
*** jerrygb has joined #openstack-oslo10:28
*** nikhil_k has joined #openstack-oslo10:29
*** nikhil has quit IRC10:30
*** jerrygb has quit IRC10:34
*** cdent has joined #openstack-oslo10:35
*** ozamiatin has quit IRC10:37
*** ihrachys has quit IRC10:38
*** ihrachys has joined #openstack-oslo10:39
*** pblaho has quit IRC10:39
*** ig0r__ has quit IRC10:40
*** yamamoto_ has quit IRC10:44
haypojd__: the openstack-sdk is https://github.com/openstack/python-openstacksdk ?11:02
jd__haypo: yes11:02
haypojd__: if i understood correctly, openstacksdk is a new implementation of many clients. but i don't understand what we are supposed to do with novaclient11:04
hayponovaclient should be a thin wrapper to openstacksdk?11:04
jd__haypo: maybe? how would I know11:04
haypojd__: what is your plan for ceilometer?11:04
jd__we don't really have plan for ceilometer since most of its api is moving away11:05
jd__but for gnocchiclient and aodhclient we don't plan on working with openstack-sdk11:05
*** dims has joined #openstack-oslo11:05
jd__we just use keystoneauth111:05
*** ozamiatin has joined #openstack-oslo11:07
*** ihrachys has quit IRC11:18
openstackgerritJulien Danjou proposed openstack/oslo.messaging: Revert "Robustify locking in MessageHandlingServer"  https://review.openstack.org/24353811:19
*** ihrachys has joined #openstack-oslo11:19
*** dims has quit IRC11:21
haypojd__: do you know where does the "openstack" CLI command come from?11:21
*** itisha has quit IRC11:21
jd__haypo: openstackclient11:21
*** dims has joined #openstack-oslo11:22
haypohum, and openstackclient doesn't use openstacksdk11:23
*** ihrachys has quit IRC11:23
*** yamamoto has joined #openstack-oslo11:35
*** yamamoto has quit IRC11:39
*** yamamoto has joined #openstack-oslo11:39
*** yamamoto_ has joined #openstack-oslo11:40
*** jaypipes has joined #openstack-oslo11:42
*** yamamoto has quit IRC11:43
*** ihrachys has joined #openstack-oslo11:49
*** achanda has joined #openstack-oslo11:54
*** yamamoto_ has quit IRC12:06
*** ajo is now known as ajo\lunch12:14
akwasnie_hey, i am trying to configure oslo log to log tracebacks to syslog, but it seems that it does not work form me. I have set syslog_level to debug and use_syslog to true, but still there is no sign of any tracebacks in syslog. errors and infos are logged properly12:18
akwasnie_any guide on how to fix this?12:21
*** gordc has joined #openstack-oslo12:22
*** achanda has quit IRC12:23
dimshaypo: at this point i am thinking of oslo.cli = apiclient/*.py + cliutils.py12:25
*** freyes has quit IRC12:26
*** freyes has joined #openstack-oslo12:26
*** yamamoto has joined #openstack-oslo12:27
*** jerrygb has joined #openstack-oslo12:32
*** jerrygb has quit IRC12:37
*** dims has quit IRC12:53
*** amrith is now known as _amrith_12:54
*** dims has joined #openstack-oslo12:56
*** ajo\lunch is now known as ajo12:57
openstackgerritDaisuke Fujita proposed openstack/oslo.log: The user_identity format flexibility  https://review.openstack.org/21813912:58
*** pblaho has joined #openstack-oslo13:03
*** ozamiatin has quit IRC13:04
haypodims: ah yes i was also thinking at puting cliutils inside apiclient13:08
openstackgerritMarkus Zoeller (markus_z) proposed openstack/oslo.config: Add help text generation for OptGroups  https://review.openstack.org/24247213:09
haypodims: that's also why i read the spec and the mail about apiclient ;)13:09
*** stevemar_ has joined #openstack-oslo13:11
openstackgerritJulien Danjou proposed openstack/oslo-incubator: Remove deprecated `apiclient'  https://review.openstack.org/24357813:13
openstackgerritJulien Danjou proposed openstack/oslo-incubator: tests: remove unused testmods  https://review.openstack.org/24357913:16
*** gcb has joined #openstack-oslo13:17
*** stevemar_ has quit IRC13:20
*** stevemar_ has joined #openstack-oslo13:21
*** achanda has joined #openstack-oslo13:23
*** salv-orlando has joined #openstack-oslo13:23
*** jerrygb has joined #openstack-oslo13:24
*** fultonj has joined #openstack-oslo13:24
*** yamamoto has quit IRC13:27
*** jerrygb has quit IRC13:29
*** ozamiatin has joined #openstack-oslo13:30
*** achanda has quit IRC13:30
haypodims, jd__ : apiclient/, cliutils.py, cliff, keystoneauth, openstackclient, openstacksdk, ... ok, now i'm lost :-)13:32
haypobut we probably have too many choices, creating yet another library may not help :)13:33
*** kgiusti has joined #openstack-oslo13:34
jd__that's why I'm proposing to remove apiclient13:35
haypojd__: ok, i replied on the list. i found projects using cliff *and* cliutils. there is maybe something that we can do to remove cliutils.py from clients too?13:53
openstackgerritChangBo Guo(gcb) proposed openstack/oslo.config: Allow method set_override with parameter override=None for all types  https://review.openstack.org/24300113:53
jd__haypo: I would think so13:54
haypojd__: i'm not sure that i understood the whole story, but i like the idea of having a single obvious way to write clients :)13:54
haypoand i understand that existing clients may use the "old" way ;)13:55
*** yamamoto has joined #openstack-oslo13:56
*** rlrossit has joined #openstack-oslo13:59
*** stevemar_ has quit IRC14:04
*** links has quit IRC14:08
*** thumpba has joined #openstack-oslo14:09
rbradforI got a jenkins failure on review in a gate-tempest-dsvm-neutron-src-oslo.i18n gate, however the change is only in docs. Is this a gate that sometimes fails14:13
*** stevemar_ has joined #openstack-oslo14:13
hayporbradfor: yes :-(14:14
hayporbradfor: most gates are unstable14:14
hayporbradfor: (functional and integration tests)14:14
rbradforhaypo, thanks. I'll just resubmit then.14:15
hayporbradfor: just add the comment "recheck"14:15
hayporbradfor: it schedules a recheck of all tests14:15
rbradforhaypo, that's even better. I was unaware of that tip. thanks.14:15
hayporbradfor: see my notes, http://haypo-notes.readthedocs.org/openstack.html#hack-openstack14:17
openstackgerritVladimir Eremin proposed openstack/oslo.config: [WIP] Support ZooKeeper and Consul for oslo.config  https://review.openstack.org/24318214:18
rbradforhaypo, thanks14:24
*** ndipanov has quit IRC14:24
*** yamamoto has quit IRC14:27
*** freyes has quit IRC14:30
*** _amrith_ is now known as amrith14:33
*** pballand has quit IRC14:35
haypodims, jd__, sileht : cool enhancement for oslo.config to review, https://review.openstack.org/#/c/221394/14:37
*** yassine has quit IRC14:39
*** regXboi has joined #openstack-oslo14:40
*** takedakn has joined #openstack-oslo14:40
dimshaypo +2A!14:42
*** sigmavirus24_awa is now known as sigmavirus2414:45
*** yassine has joined #openstack-oslo14:45
*** salv-orlando has quit IRC14:46
openstackgerritVictor Stinner proposed openstack/oslo.config: Remove "Kept for backward-compatibility" comment  https://review.openstack.org/24363014:46
*** ujjain has quit IRC14:46
*** thangp has joined #openstack-oslo14:46
*** pradk has joined #openstack-oslo14:47
*** ujjain has joined #openstack-oslo14:48
*** ujjain has quit IRC14:48
*** ujjain has joined #openstack-oslo14:48
gcbhaypo,  can you help review a python 3 issue fix: https://review.openstack.org/#/c/241591/14:49
*** mriedem has joined #openstack-oslo14:51
*** freyes has joined #openstack-oslo14:53
haypogcb: i'm not sure that "nested" is the right name14:53
haypogcb: it's more an issue with the qualified name, a new feature of 3.3 or 3.4 (i don't recall)14:53
*** stevemar_ has quit IRC14:53
hayponested class is more something like: class A: class B: pass14:53
openstackgerritMerged openstack/oslo.middleware: add missing shortcut for HTTPProxyToWSGI middleware  https://review.openstack.org/24321214:54
*** stevemar_ has joined #openstack-oslo14:54
gcbhaypo, the description may be not correct, I met the problem when port oslo.utils.reflection to keyston in https://review.openstack.org/#/c/241494/14:55
*** cprmrf has joined #openstack-oslo14:57
haypogcb: hum, the docstring says that qualified name is used14:58
haypogcb: and there is an optional fully_qualified parameter14:58
gcbparameter fully_qualified doesn't handle the case14:58
haypogcb: IMHO you must use __qualname__ if fully_qualified, or __name__ otherwise14:58
*** fultonj has left #openstack-oslo14:59
haypogcb: use __name__ instead of using .rsplit('.')[-1], it's simpler ;)14:59
*** mc_nair has joined #openstack-oslo14:59
*** amotoki_ has joined #openstack-oslo15:00
*** links has joined #openstack-oslo15:01
*** cprmrf has quit IRC15:03
haypodims: thanks for approving the oslo.config change ;)15:03
*** links has quit IRC15:05
*** cprmrf has joined #openstack-oslo15:06
*** cprmrf__ has joined #openstack-oslo15:11
*** takedakn has quit IRC15:12
*** pradk has quit IRC15:13
*** pradk_ has joined #openstack-oslo15:13
gcbhaypo,  in Python 3  obj.__qualname__  returns 'ClassA.__init__.<locals>.ClassB',  In python2  obj has no attribue __qualname__, so back to obj.__name__ returns 'ClassB', it returns different name. That 's the problem. Do you mean only use obj.__name__ ?15:14
*** pradk_ is now known as pradk15:14
gcbyou can get test test code in https://bugs.launchpad.net/oslo.utils/+bug/151306715:14
openstackLaunchpad bug 1513067 in oslo.utils "reflection: need clean nested class's name with prefix in Python 3" [Undecided,In progress] - Assigned to ChangBo Guo(gcb) (glongwave)15:14
*** cprmrf has quit IRC15:15
gcbhaypo, I saw your comments thanks15:17
*** pm90_ has joined #openstack-oslo15:18
*** harlowja_at_home has joined #openstack-oslo15:20
*** pm90__ has joined #openstack-oslo15:24
*** rlrossit has quit IRC15:25
*** rlrossit has joined #openstack-oslo15:25
*** pm90_ has quit IRC15:26
*** achanda has joined #openstack-oslo15:27
*** yamamoto has joined #openstack-oslo15:28
openstackgerritChangBo Guo(gcb) proposed openstack/oslo.utils: Fix obj.__qualname__ return class name with prefix in python 3  https://review.openstack.org/24159115:28
rbradfordims, from our conversation yesterday on _i18n -- https://review.openstack.org/#/c/243321/.15:31
*** rjaiswal has joined #openstack-oslo15:31
rbradforThis lead me to seeing how much more documentation is needed to create working examples, e.g. http://paste.openstack.org/show/478443/15:31
rjaiswal7:16 PM <rjaiswal> dims: https://review.openstack.org/#/c/243360/ for bumping up the requirements15:32
*** achanda has quit IRC15:32
*** jerrygb has joined #openstack-oslo15:33
*** yamamoto has quit IRC15:33
rbradforI saw there was a Tokyo session on Better documentation.  Has anybody thought about the approach to blend documentation with working demos, in a documenting plus cut/paste situation15:33
openstackgerritSean Dague proposed openstack/oslo.messaging: Revert "Robustify locking in MessageHandlingServer"  https://review.openstack.org/24365815:33
sdaguedims: ^^^ revert proposed15:33
*** jecarey has joined #openstack-oslo15:34
openstackgerritSean Dague proposed openstack/oslo.messaging: Revert "Robustify locking in MessageHandlingServer"  https://review.openstack.org/24365815:34
dimssdague : +2A15:34
*** gcb has quit IRC15:35
mriedemdims: looks like that waiting log message is hitting some ceilometer/aodh tests too http://logstash.openstack.org/#dashboard/file/logstash.json?query=message:%5C%22has%20been%20waiting%20for%5C%2215:36
mriedemgordc: ^15:36
*** jerrygb has quit IRC15:37
dimsmdbooth harlowja ping about oslo.messaging issues15:37
gordcmriedem: dims: not sure if this is root of issue but we do have this: https://review.openstack.org/#/c/243538/15:38
dimsgordc i approved sdague's revert for the same15:39
gordcdims: kk, i guess jd__ can drop his.15:40
jd__whaat15:42
jd__did sdague just stole my patch15:42
dimsjd__ haha :)15:42
gordcpatch jacked15:43
sdaguejd__: sorry, we didn't see it when doing debug this morning15:43
*** salv-orlando has joined #openstack-oslo15:46
jd__sdague: no offense lol15:46
harlowja_at_homehmmmm, locking issue15:52
harlowja_at_homei'm pretty sure if oslo.messaging was written in go, using redis, it would be all better15:53
harlowja_at_home(snark snark)15:53
dimsLOL15:53
dimsno redis, we need consul or etcd15:53
harlowja_at_homereconsuld15:54
harlowja_at_homewe need ^15:54
harlowja_at_home(i just made that up)15:54
*** freyes has quit IRC15:54
harlowja_at_homehmmm, i wonder what happened with the locking15:55
harlowja_at_homeguess we must of missed some logic15:55
* harlowja_at_home will ponder15:55
sdagueharlowja_at_home: I think it did not anticipate the eventlet case15:56
*** salv-orlando has quit IRC15:57
*** freyes has joined #openstack-oslo15:57
*** mtanino has joined #openstack-oslo15:57
harlowja_at_homesdague, do u mean not using green conditions or something else?15:58
harlowja_at_home(if u know/have ideas)15:58
sdagueharlowja_at_home: don't know entirely, but nova, for instance, uses the fakeimpl driver to build an entire set of nova services in a single process (including possibly multiple computes)15:59
sdagueand run scenarios just like a real environment15:59
sdagueso we're pushing back and forth on that a bunch15:59
sdagueall with greenlets15:59
harlowja_at_homeagreed, so probably something eventlet not being tweaked right16:00
harlowja_at_homemonkey patching threading in that scenario happens though right?16:00
harlowja_at_home*pretty sure in general nova does that16:00
harlowja_at_homeanyways, we'll figure it out16:03
*** jecarey has quit IRC16:06
*** jerrygb has joined #openstack-oslo16:07
* harlowja_at_home pretty sure we just need to simplify '_OrderedTask' in that revert, make it a little more explict whats going on, and in smaller chunks, that will probably help16:08
*** jerrygb has quit IRC16:12
kevinbentonzzzeek: ping re sqlalchemy and polymorphic_identity. got a quick question16:13
sdagueanyway, the nova unit tests definitely expose this 100% locally, so you can use that as a test on this to figure out if it's right16:13
*** jerrygb has joined #openstack-oslo16:13
zzzeekkevinbenton: sure16:13
kevinbentonzzzeek: so in the Employee Manager example, say the employee ID is an auto increment value and that's how manager is related to employee16:14
kevinbentonzzzeek: does sqlalchemy handle the legwork of inserting a manager record of inserting an employee record and using the auto inc value?16:14
*** jerrygb_ has joined #openstack-oslo16:15
zzzeekkevinbenton: yes16:15
*** pballand has joined #openstack-oslo16:15
kevinbentonzzzeek: excellent, any hints i need to give it or is it good to go?16:15
harlowja_at_homesdague, great, that will def help16:16
kevinbentonzzzeek: other than 'polymorphic_identity' of course16:16
zzzeekkevinbenton: in joined table inheritance the child and parent tables are related to each other using a foreign key as usual.  the mapper detects the column in the chlid table that is to be "synchronized" with the parent primary key column.  If not foreign keys, this relationship can also be configured using the "inherit_condition" mapper argument.16:17
zzzeekkevinbenton: the mapper runs an INSERT for the parent table first, fetches the autoinc PK, and "synchronizes" it into the child table value16:17
*** jerrygb has quit IRC16:17
kevinbentonzzzeek: very cool. this is in the context of that neutron patch i was working on before so when i upload a new version you should get a gerrit notice16:18
*** amotoki_ has quit IRC16:19
zzzeekkevinbenton: sure16:20
kevinbentonzzzeek: thanks for your time!16:20
zzzeekkevinbenton: i hope the joined inh is really waht we need there, joined inh is pricey16:21
kevinbentonzzzeek: well based on jay's comments, it sounds like it shouldn't be a big hit if we are using ints16:22
kevinbentonzzzeek: i will do some profiling though to verify16:22
zzzeekkevinbenton: the joins...are heavy.  they are much less heavy in SQLA 1.0 though, we used to rely on subqueries a lot which completely blew mysql away16:22
*** jecarey has joined #openstack-oslo16:23
*** ozamiatin has quit IRC16:23
kevinbentonzzzeek: oh, i see. you mean the way that sqlalchemy is rendering the queries16:23
mdboothharlowja dims: Ooh, fun16:24
mdboothExample?16:24
zzzeekkevinbenton: well yes, the classic case is loading Foo objects that have a collection of Manager, the query needs a right-nested join.   sqlite doesnt support this and maybe mysql didnt a long time ago so we would turn the right-nest into a subuqery16:24
zzzeekselect foo.*, subq.* from foo join (select * from employee join employee on <onclause>) on <onclause>16:24
*** nkrinner has quit IRC16:25
zzzeek^^^^ brings mysql to a halt16:25
harlowja_at_homemdbooth, sdague should be able to point u at the way to run the tests he's talking about, supposedly it always happens, so thats good16:25
harlowja_at_homei'm wondering if its the ordering stuffs16:25
mdboothdims: I'd be -1 on the revert without seeing an example16:25
harlowja_at_homeperhaps something off there...16:25
zzzeekin 1.0 we do:  select foo.*, employee.*, manager.* from foo join (employee join manager on <onclause>) on <onclause>16:25
mdboothThe usage of eventlet in the tests shouldn't be relevant. That basically just makes testing easier.16:25
zzzeeks/employee join employee/employee join manager/16:25
sdaguemdbooth: go look at the bug16:25
dimsmdbooth check nova logs too please16:25
kevinbentonzzzeek: makes sense. is 1.0 in our requirements for openstack though?16:26
dimsirc logs16:26
zzzeekkevinbenton: yes16:26
mdboothsdague: I looked. Didn't see an example.16:26
mdboothPerhaps I looked too quickly.16:26
sdaguemdbooth: define "example"16:26
mdboothAh, ha16:26
mdboothThat's a different bug :)16:26
sdaguethe point is that tests randomly end up taking up to the max timeout16:26
mdboothI was looking at a pretty useless bug16:26
kevinbentonzzzeek: oh okay. so i'll check to see if this has a big impact on our common API operations16:26
mdboothOk, looking16:26
dimsmdbooth http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2015-11-10.log.html#t2015-11-10T14:59:2716:27
*** jamielennox has quit IRC16:28
dimsmdbooth i see nova.tests.functional.test_server_group.ServerGroupTest.test_boot_servers_with_affinity and nova.tests.unit.api.ec2.test_cinder_cloud.CinderCloudTestCase.test_stop_with_attached_volume at the very least in the irc chat16:28
mdboothdims: So, my patch should be producing log messages if it's causing long waits16:31
mdboothdims: I don't know what I'm looking at in those irc logs16:35
mdboothdims: So, hold on a sec16:36
mdboothI'd like to make an alternate proposal16:36
mdboothdims: There's a reasonable chance here that the underlying issue is actually a race in the tests16:37
mdboothWhich results in an ordering issue16:37
mdboothThe hard hang is something I experienced myself, which is why I wrote the tests to use eventlet explicitly16:38
mdboothBecause it doesn't hard hang16:38
mdboothOf course, my tests don't hang at all16:38
mdboothBut when I was debugging, an eventlet hang responds to ctrl-c16:38
mdboothIn this case, the bug is most likely to be in the test, not in oslo.messaging16:39
mdboothAnd the best way to find that would be to have it produce an error rather than hang16:39
*** ansiwen has joined #openstack-oslo16:39
mdboothWhich is what my follow-on patch does16:39
mdboothhttps://review.openstack.org/#/c/238985/16:39
mdboothSo, if we merged that with, say, a default timeout of 5 minutes16:40
mdboothAfter we flush out all the problematic tests we can remove it16:40
mdboothsdague: ^^^ ?16:40
sdaguemdbooth: this is basically blocking all of nova dev, so it should be reverted and a reverted version released16:40
sdaguethen you can experiment on versions of this which fix it in a different way16:41
mdboothsdague: I hear you. Is there another good way to find the buggy tests?16:41
sdaguemdbooth: just run the nova unit tests locally16:41
*** jamielennox has joined #openstack-oslo16:41
mdboothsdague: What proportion were failing?16:41
sdagueI'm not convinced there is anything buggy about the tests16:42
sdaguethey are using the high level semantics that already exist16:42
*** harlowja_at_home has quit IRC16:42
sdaguemdbooth: it's locally reproducable, if you would just do that, it would go a long way16:42
*** salv-orlando has joined #openstack-oslo16:42
mdboothI literally heard about this about 5 minutes ago :)16:43
mdboothsdague: Is it 100% reproducible locally?16:43
mdboothOr is it non-deterministic?16:43
sdaguewe had 4 people working in channel that could all 100% locally reproduce this, and locally produced that the revert of your patch fixed it16:43
sdagueit's 100%16:43
mdboothOk, cool16:43
sdaguewhich is why it needs a revert16:43
mdboothWell, that should be simple enough to sort out16:43
mdboothYup, I agree with a revert in that case16:44
*** cdent has quit IRC16:44
mdboothI'll run nova tests locally with patched oslo.messaging16:44
ansiwenmdbooth: unit tests?16:46
mdboothansiwen: ?16:46
mdboothWhich unit tests?16:46
ansiwenmdbooth: you are going to run the unit tests locally?16:46
ansiwenbecause I just did that, and they were all fine16:47
mdboothansiwen: Hmm16:47
mdboothSo it's non-deterministic...16:47
mdboothThat's unfortunate16:47
mdboothIn that case, I'm not necessarily in favour of the revert16:47
mdboothSo, if you have a look at the original commit, even several of the oslo.messaging tests were calling server methods in the wrong order16:48
ansiwenI just did "tox -e py27"16:48
mdboothansiwen: Are you sure it was using the affected version of oslo.messaging?16:48
ansiwenmdbooth: no :-)16:49
ansiwenprobably not... I already suspected that I was missing an important detail ;-)16:49
*** itisha has joined #openstack-oslo16:52
sdagueansiwen: .tox/py27/bin/pip freeze | grep oslo.messagin16:52
mdboothsdague: Which is the bad version?16:54
sdague2.816:55
mdboothsdague: Oh, interesting. That's what I already have.16:55
sdagueoslo.messaging==2.7.1.dev19 is the largest version that will pass16:55
mdboothI'm convinced I've done several local runs.16:55
sdaguemdbooth: and what's the max test time16:55
mdboothI didn't pay any attention, tbh16:56
mdboothBut I will this time16:57
sdaguemdbooth: right, that's the issue16:57
mdboothsdague: What's a bad value?16:57
sdaguea whole bunch of tests are going to 160s16:57
sdaguethe max test run time should be no more than 20s16:57
sdaguethat all stacks up and we overrun the overall test timeout16:57
sdagueand explode16:57
mdboothsdague: Got it. Do you have to hand a specific example of an overrunning test?16:57
mdboothI can presumably reproduce by running all of them, but if you have one to hand...16:58
sdaguemdbooth: here is a failed test run - http://logs.openstack.org/62/237762/8/check/gate-nova-python27/046e095/console.html there are items in there that hit that16:59
mdboothAh, I think dims posted a couple16:59
sdaguewhen I said 100% repeatable, it's not that each test is 100% fail, it's that the effect is 100% repeatable on the nova unit tests as whole16:59
mdboothsdague: Hmm, ok16:59
sdaguerun all the tests17:00
sdaguetox -e py2717:00
*** bauzas has joined #openstack-oslo17:01
mdboothsdague: Have reproduced locally.17:02
sdaguemdbooth: awesome, cool17:03
mdboothsdague: I'm just pumping you for info, btw :) Assuming the revert will proceed full speed.17:03
sdagueok, no problem, I just got worried with all the language of being -1 on the revert17:04
mdboothsdague: That was before I realised it was 100% reproducible.17:04
mdboothI'm still expecting to find a problem elsewhere, I just didn't want to lose the opportunity.17:05
mdboothIf I can reproduce, that's not an issue.17:05
sdagueyeh, given that we had a bunch of people reproducing it locally (myself included) it seemed like it would be easy enough to test future things17:06
*** salv-orlando has quit IRC17:08
dimsmdbooth the +2A for revert went through before you joined the channel :)17:10
mdboothdims: Glad to know where I stand :)17:11
mdboothYeah, totally makes sense now I have the context.17:11
mdboothOk, I have a suspect17:16
*** pm90__ has quit IRC17:16
mdboothIt's the cleanup of ServiceFixture17:16
mdboothsdague dims: Fixed it17:20
mdboothIt's a bug in ServerGroupTest.setUp()17:20
mdboothIt calls self.start_service(), which adds a ServiceFixture17:20
mdboothWhich adds a cleanup action of kill, which calls stop17:21
mdboothBut it adds a second cleanup action17:21
mdboothThe second one hangs17:21
mdboothAlthough, on second thoughts... should it?17:21
* mdbooth ponders that for a minute17:21
sdagueso, iirc, that was the operation order that was required to not hang in the past17:23
mdboothHehe, fun17:23
sdagueit's been a while since that was out there though17:23
sdagueI think I built those fixtures a year ago17:23
mdboothI'm just trying to work out why the second stop should hang17:24
mdboothBecause it seems it should be a no-op17:24
mdboothAnd not hang17:24
mdboothUnless something has subsequently called wait...17:24
sdagueright, so I'm trying to remember what was happening the last time17:24
sdagueI feel like what was going on was that there was an implied wait in the in memory driver on stop17:25
*** yassine has quit IRC17:25
sdaguebecause it assumed there were still events to process17:25
sdagueand if the queue was already empty then it would just hang17:25
mdboothAh... yes17:25
mdboothIt does:17:25
mdbooth            self.rpcserver.stop()17:25
mdbooth            self.rpcserver.wait()17:25
mdboothdims harlowja: So this is the consequence of the wrapping decision ^^^17:26
mdboothsdague: The reason it hung is because it has stopped and waited, and now assumes it must be started again before you can call stop17:27
*** dims has quit IRC17:27
mdboothsdague: So, that genuinely is a semantic change in oslo.messaging, but it was a deliberate one17:27
mdboothWhich now looks misguided :/17:27
*** dims has joined #openstack-oslo17:28
*** browne has joined #openstack-oslo17:28
mdboothdims: Did you see above before you quit, btw?17:28
sdagueok, yeh, that kind of semantic change is going to need a lot of warning, and might have more unintended downstream effects than this17:28
mdboothsdague: The second kill should also go, I think, but it feels wrong that we didn't handle it17:29
*** achanda has joined #openstack-oslo17:30
* mdbooth will send a mail to the list17:31
mdboothsdague: Sorry for the trouble17:31
sdaguemdbooth: yeh, no problem. Sorry for any frustration. This ended up being the 3rd conversation about the same bug today :)17:31
openstackgerritAkihiro Motoki proposed openstack/oslo.config: Add max length check to StrOpt  https://review.openstack.org/24288017:32
dimssdague mdbooth i think i caught most of it. apologies for the network reconnects17:34
mdboothdims: In case you missed the critical bit, the issue is that a set of nova tests is doing:17:34
mdboothserver.start(), server.stop(), server.wait(), server.stop(), server.wait()17:35
mdboothBecause we decided to allow a server to be restarted, after wait() we're now expecting another start()17:35
dimsmdbooth do we log anything in the step #4?17:35
mdboothdims: Good question, and I'll go look17:35
dims"can't stop something that has not been started"17:36
mdboothYup17:36
*** achanda has quit IRC17:36
mdboothSo the second call to stop() hangs because it's expecting a start17:36
mdboothIf we *don't* allow a server to be restarted, this goes away17:36
mdboothBoth the stop() and the wait() become no-ops17:36
dimsbut then we have to fix folks who are reusing the same thing17:36
mdboothTrue. Is anybody doing that?17:37
dimsmdbooth if we make a release we'll find out...but don't want to take that chance :)17:37
mdboothEither way, I'm not sure it's possible to completely fix both things :)17:37
dimslet's get sileht's opinion too.17:38
mdboothdims: How many projects use oslo.messaging?17:39
mdboothWe could just run all their tests?17:39
mdboothdims: I'll send an email17:41
mdboothProbably easier to do on the list, and no great emergency, I think17:41
dimsmdbooth http://paste.openstack.org/show/478471/17:41
dimsthis is just from my local directories17:41
mdboothThat's doesn't look intractable17:42
mdboothIs there a way we can get jenkins to run them?17:42
mdboothSubmit a patch to requirements.txt, I guess17:42
mdboothThat should run all their tests, no?17:43
dimswish it was that simple17:43
mdboothHowever, that would also require a release...17:43
mdboothIs there a way to get them to run against an arbitrary commit?17:43
mdboothI'm sure I saw you submit some arcane invocation to nova once.17:44
dimsmdbooth y, if it was one project...17:45
dimsthat's why i had the travis setup...looks like the new install_command(s) broke what i had17:46
dims(for unit tests)17:46
mdboothThe problem is, the previous behaviour was basically undefined17:52
mdboothdims: Incidentally, yes the warning message are emitted17:52
mdboothSomewhere17:52
*** pm90_ has joined #openstack-oslo17:55
* mdbooth is interested to know why the test ever completes17:57
*** SurajD has joined #openstack-oslo17:59
*** jecarey has quit IRC17:59
*** browne has quit IRC18:01
harlowjamdbooth soo its stop, wait, start ... (and repeat) stuff showing up?18:03
* harlowja just cathing up18:04
mdboothharlowja: It's start, stop, wait, stop, wait18:04
harlowjaah18:04
mdboothI'm just writing it up in a mail18:04
harlowjakk18:04
harlowjastop wait stop stop stop wait wait wait18:04
harlowjajust messing with u (continue writing the email)18:04
harlowjalol18:04
*** jerrygb has joined #openstack-oslo18:06
mdboothsdague: Incidentally, any idea where the logs for those test runs are going? It should have emitted a log message after 30 seconds, and in my tracing it does exactly that. However, I didn't see the logs anywhere. The log message is both a message at WARN, and a full stack trace at DEBUG.18:09
*** jerrygb_ has quit IRC18:09
*** sputnik13 has joined #openstack-oslo18:10
*** sputnik13 has quit IRC18:11
*** sputnik13 has joined #openstack-oslo18:11
sdaguethey might be in the subunit stream18:11
sdaguedebug is definitely off18:11
sdaguebecause it creates too much output18:11
sdaguehttp://logs.openstack.org/62/237762/8/check/gate-nova-python27/046e095/tmpfFPVIr is the raw subunit stream for the failed test run I posted above18:13
*** pm90__ has joined #openstack-oslo18:13
*** SurajD has quit IRC18:14
*** SurajD has joined #openstack-oslo18:14
SurajDCan somebody review this https://review.openstack.org/#/c/240661/ this is my first upstream contribution18:16
*** pm90_ has quit IRC18:16
dimsSurajD one nit left by gcb...i'll +2 after that18:17
dimsSurajD welcome! :)18:17
SurajDdims, sure18:18
SurajDdims, thanks :)18:18
mdboothsdague: Yup, they're in there. Thanks.18:18
mdboothThere are 818:19
openstackgerritSuraj Deshmukh proposed openstack/oslo.utils: Added ICMP 'type' and 'code' checking capability to 'netutils' module  https://review.openstack.org/24066118:20
*** abitha has joined #openstack-oslo18:22
SurajDdims, done with nit :)18:22
dimscool, Happy Diwali SurajD18:23
SurajDdims, Thank you and same to you :)18:23
*** achanda has joined #openstack-oslo18:25
SurajDdims, Thanks for the Code-review as a DIwali Gift18:28
harlowjalol18:28
*** bnemec has quit IRC18:29
mdboothharlowja: Thar she blows18:31
harlowjakk, let's seeee here18:32
*** rlrossit has left #openstack-oslo18:32
mdboothharlowja: I've blown so far past going home time my wife just turned up with my plated dinner covered in tinfoil :)18:33
mdboothI'm happy to deal with this async. Catch you tomorrow, and thanks for looking.18:33
openstackgerritMerged openstack/oslo.messaging: Revert "Robustify locking in MessageHandlingServer"  https://review.openstack.org/24365818:34
harlowjamdbooth np18:36
dimsmdbooth talk to you tomorrow18:37
dimsharlowja does this look ok to you? https://review.openstack.org/#/c/243275/18:37
harlowjadims looks ok to me, checked hash and thats the one with the change18:39
dimsharlowja mind +1'ing it please?18:39
harlowjakk18:39
*** achanda has quit IRC18:41
rjaiswalthanks harlowja, dims18:42
harlowjanp18:42
*** yamahata has joined #openstack-oslo18:45
*** SurajD has quit IRC18:51
*** mriedem has quit IRC18:53
*** jecarey_ has joined #openstack-oslo18:57
*** jecarey_ has quit IRC18:57
*** jecarey_ has joined #openstack-oslo18:57
*** mriedem has joined #openstack-oslo18:58
sputnik13dims have you tried bringing up devstack with zookeeper lately?18:59
*** browne has joined #openstack-oslo18:59
dimssputnik13 not for a few days, what's up?18:59
sputnik13we've been using zookeeper in devstack and it seems like our jobs fail since the zookeeper addition to devstack19:00
sputnik13we had our own devstack plugin for zookeeper19:00
sputnik13so I removed our plugin and the gate still fails, just wondering whether it's just me19:00
dimsgot a review where this is failing?19:01
*** jerrygb_ has joined #openstack-oslo19:01
harlowjasputnik13 dims a coworker who runs stuff on rhel7 is also investigating it there and figuring out whats packaged and whats not, asked him to send an email to openstack-dev with his results19:02
sputnik13http://logs.openstack.org/66/243366/1/check/gate-cue-integration-dsvm-rabbitmq/5f382f5/logs/devstacklog.txt.gz#_2015-11-10_01_07_45_60619:02
*** achanda has joined #openstack-oslo19:03
*** jerrygb has quit IRC19:04
harlowjahmmm19:05
harlowjamy guess is thats because the infra servers are already starting zookeeper19:05
*** jerrygb has joined #openstack-oslo19:05
harlowjaand devstack should have some smarts to not bother starting zookeeper if its already there and running19:05
harlowja*infra servers / infra vms19:06
sputnik13meh?19:06
dimsharlowja i thought there was a review already for that19:07
harlowjaunsure19:07
harlowjasputnik13 https://review.openstack.org/#/c/241040/ (See second comment)19:07
harlowjabut dims  might know of an existing patch already in the pipeline19:07
harlowjaarun (also commented there, a coworker) is emailing the rhel7/fedora people to figure out about rhel7 zookeeper package (which appears underway)19:08
*** jerrygb_ has quit IRC19:08
dimssputnik13 https://review.openstack.org/#/c/242445/19:08
*** achanda has quit IRC19:09
sputnik13yeah we circumvented this whole deal by just not starting zookeeper19:09
sputnik13since it gets started automatically when you install the package19:10
harlowjaright19:10
sputnik13https://github.com/openstack/cue/blob/master/contrib/devstack/lib/zookeeper#L4719:11
harlowjacool, so ^ might not be needed anymore19:11
harlowja' sudo pip install -e "git+https://github.com/python-zk/kazoo.git#egg=kazoo"'19:11
harlowja:-/19:11
harlowjahmmm19:12
harlowjawhat is this, ha19:12
harlowjahttps://github.com/openstack/cue/blob/master/contrib/devstack/lib/zookeeper#L40 ;)19:12
*** achanda has joined #openstack-oslo19:12
sputnik13well, yeah so that cue review is to remove that, but the gate still fails because the current zookeeper handler in devstack tries to start zookeeper19:12
harlowjaguess that was to get the slow-butt-kaozo-releases19:12
sputnik13https://review.openstack.org/#/c/243366/19:12
harlowjacool19:12
dimssputnik13 you can try Depends-On the review that i pointed to19:13
*** achanda has quit IRC19:13
sputnik13dims the thing is none of our checkins will go through until this is resolved since zookeeper is a required component19:13
sputnik13what's the likelihood this will be merged some time soon19:14
sputnik13does systemd return "running"?19:15
sputnik13I forget19:15
sputnik13err when you do a service status19:15
harlowja$ service zookeeper status19:18
harlowjazookeeper start/running, process 117619:18
harlowjaso seems so19:18
*** sputnik13 has quit IRC19:18
harlowja$ service zookeeper status19:18
harlowjazookeeper stop/waiting19:18
harlowja19:18
harlowja^ for when stopped19:18
harlowjathats on Ubuntu 14.04.1 LTS19:18
dimsdhellmann, lifeless : nova needs to get started on using  oslo.versionedobjects[fixtures], can you please review https://review.openstack.org/#/c/238871/ once more when you get a chance19:19
dimsmriedem ^^19:19
*** sputnik13 has joined #openstack-oslo19:19
dimsmriedem know anyone else who has project-config karma?19:19
mriedemAJaeger19:20
mriedemi'm trying out a hack in tox.ini for now19:20
mriedemjust adding oslo.versionedobjects[fixtures] to deps19:21
mriedemso it's not in test-requirements.txt19:21
*** eezhova has quit IRC19:21
dimsmriedem right.19:21
sdaguehonestly, I think in the zookeeper case the contract is just wrong19:21
sdaguewith all other services we do restart as our contract19:22
openstackgerritJoshua Harlow proposed openstack/oslo.utils: Add useful 'time_it' decorator  https://review.openstack.org/23122019:22
*** eezhova has joined #openstack-oslo19:23
dimssdague so start_service -> restart_service?19:23
sdagueyeh, so, actually, let me take a whack at abstracting this a little19:24
harlowjabtw, https://admin.fedoraproject.org/pkgdb/package/zookeeper/timeline#n1 (also is happening)19:24
harlowja'user: ctubbsii requested branch: epel7 for package zookeeper' ...19:24
dimssdague ack thanks, some services we using restart_service, some start_service, i just happened to pick one :)19:24
sdagueyeh19:24
sputnik13why should start_service == restart_service?19:25
*** ihrachys has quit IRC19:25
dimssputnik13 apparently zookeeperd is already in the CI image deployed, so zookeeper starts even before devstack is installed19:25
*** yamahata has quit IRC19:25
*** yamahata has joined #openstack-oslo19:26
sputnik13I agree it's inconsistent with what the rest of devstack may be doing, but start_service == restart_service intuitively is wrong to me19:26
dimssputnik13 that's why i did not do it :)19:26
*** bauzas has left #openstack-oslo19:36
openstackgerritJoshua Harlow proposed openstack/taskflow: Move engine options extraction to __init__ methods  https://review.openstack.org/24379319:38
sputnik13so uhh...  how does one go about getting their project or gate job added to the devstack project's gate list so that changes like these don't just pull out the rug from under us?19:38
sputnik13is that even an option?19:38
*** subscope has joined #openstack-oslo19:39
harlowjaunsure sdague  might know?19:39
harlowja(or others on infra channel)19:40
*** amotoki has quit IRC19:42
sdaguesputnik13: no, we're not gating the world here. It's about engaging once issues show up19:42
sdaguedims / harlowja - how do you feel about this approach - https://review.openstack.org/24379419:43
sputnik13gate check failed http://logs.openstack.org/45/242445/2/check/gate-tempest-dsvm-neutron-full/c8f0736/console.html#_2015-11-10_19_26_25_55419:43
sdaguesputnik13: yep, that's probably the 35% failure rate issue I posted on the ML19:43
harlowjasdague ok, thats fine with me, we might want to push on the epel7 zookeeper change though (or maybe not?)19:44
sdagueharlowja: what change is this?19:44
sputnik13sdague that assumes dlm is the only user for zookeeper, dlm is a library that uses zookeeper19:44
harlowjasdague https://admin.fedoraproject.org/pkgdb/package/zookeeper/timeline#n119:44
harlowjaepel7 process for packaging zookeeper for rhel7 started...19:44
sputnik13for services that use zookeeper doing "install_dlm" when we want zookeeper seems weird19:45
harlowja(its in fedora already, just someone needs to move it to epel7...)19:45
harlowjasdague that was 4 days ago (not sure how long it takes)19:45
sdaguesputnik13: so, the point of the exercise on using tooz is that we should make sure all the zookeeper interaction, for any purpose, goes through tooz19:46
sdaguewhich probably means extending tooz to support whatever that set of semantics is19:46
sputnik13sdague once again, you're assume zookeeper's only use is for dlm, this is not true19:46
sdaguesputnik13: no, I really don't19:46
sputnik13taskflow uses zookeeper for jobboard19:46
* harlowja will have to figure out what tooz apis are missing for the jobboard stuff19:47
sputnik13monasca uses zookeeper for kafka19:47
harlowjai was thinking about that in the shower this morning19:47
harlowjaand nuff said19:47
harlowjalol19:47
dimstoo much information harlowja19:47
sputnik13yeah I don't really want to know what you do in the shower19:47
sputnik13:)19:47
harlowjalol19:47
sdaguesputnik13: right but if we end up with an environment that's consul & zookeeper to be functional, than this whole thing failed19:48
dimssdague i am ok with the lib/dlm change19:48
harlowjahttp://docs.openstack.org/developer/taskflow/jobs.html (for those who wondering what sputnik13 is talking about)19:48
sdaguedims: cool, just had to fix a set of includes there19:48
harlowjai'll eventually i guess move the drivers there to tooz (sometime in the future)19:49
harlowjai think that makes logical sense to try to do (if we can)19:49
dimssdague some comments at the top with the method names needs fixing19:49
harlowjahttp://docs.openstack.org/developer/taskflow/jobs.html#taskflow.jobs.backends.impl_zookeeper.ZookeeperJobBoard also has other comments about how it works...19:49
sputnik13so are we now saying that anything that uses zookeeper directly can't be used in openstack?19:49
harlowjalol19:50
harlowjai hope not19:50
harlowjacause thats cray cray imho19:50
sputnik13I don't get the need to say zookeeper falls strictly under tooz/dlm19:50
sdagueok, I was not in whatever room the conversations happened in19:50
sdaguebut there seems to be a missing piece of all of this conversation19:51
sdaguebecause this was what projects could assume would always be there, and the abstraction of tooz was picked19:52
sdaguezookeeper direct was not picked19:52
sputnik13sdague I believe the abstraction of tooz as DLM was the decision19:52
sdagueif there are other voices that want zookeeper direct picked, they should voice that fact19:52
sputnik13not that tooz is an abstraction for all zookeeper things19:52
sdaguesputnik13: and that a dlm could be assumed19:52
harlowjaprojects already exist and those things use zookeeper, so we likely need to accept that it will be there in those projects (especially ones we don't control like kafka and others) and for ones we can affect, they should use tooz (if the api works, or can be adjusted to work)19:52
harlowjathats my 2 cents19:53
sdaguethere is no assumption that you can assume zookeeper is there, or that people will deploy zookeeper19:53
sputnik13so anyone needing a DLM like thing must use tooz, that's accepted and agreed, I'm one of the proponents of the idea19:53
sdagueso any use of that in a project probably needs to be optional19:53
harlowjasure, if u don't want to use a feature of a project, well sucks for that person, lol19:53
harlowja*and/or optional feature19:54
sputnik13I'm not questioning whether tooz should be the standard interface for DLM19:54
openstackgerritRyan McNair proposed openstack/oslo.concurrency: Allow deletion of all lock files matching a glob  https://review.openstack.org/24166319:54
sputnik13what I'm saying is, there are existing projects that use zookeeper for something other than DLM, the addition of this "dlm support" to devstack broke said project, which is all fine we're for sharing code and removing duplication so we want to remove our own zookeeper devstack/lib thing and use the common one19:56
*** rlrossit has joined #openstack-oslo19:56
sputnik13but within devstack putting zookeeper strictly under "dlm" seems weird to me since that's just a service that's used by dlm/tooz and now we have assertions being made that zookeeper should never be used directly by anything which is completely beyond the scope of what the DLM conversation/discussion was bout19:58
dimsi see the point sputnik1319:59
dimsnot sure how we went from start/restart to this discussion :)20:00
sputnik13yeah, seems a really windy path doesn't it? :)20:00
openstackgerritMichael Krotscheck proposed openstack/oslo.middleware: Enable latent CORS configuration via pastedeploy  https://review.openstack.org/24098420:03
*** yamahata has quit IRC20:11
*** tristanC has joined #openstack-oslo20:13
tristanCGreeting oslo folks, I'd like to check in on bug 1449062. e.g., can oslo provides a command line utility "prlimit" to accomodate system that does not include util-linux v2.21 (which provide such utility) ?20:15
openstackbug 1449062 in Glance "qemu-img calls need to be restricted by ulimit (CVE-2015-5162)" [High,In progress] https://launchpad.net/bugs/1449062 - Assigned to nikhil komawar (nikhil-komawar)20:15
*** lifeless has quit IRC20:26
*** rjaiswal has quit IRC20:26
*** rjaiswal has joined #openstack-oslo20:27
*** sputnik13 has quit IRC20:38
openstackgerritJoshua Harlow proposed openstack/taskflow: Move engine options extraction to __init__ methods  https://review.openstack.org/24379320:40
openstackgerritJoshua Harlow proposed openstack/taskflow: Move engine options extraction to __init__ methods  https://review.openstack.org/24379320:41
*** pm90__ has quit IRC20:42
*** sputnik13 has joined #openstack-oslo20:42
haypotristanC: where do you want to put such helper script?20:44
tristanChaypo: preferably in $PATH20:46
tristanChaypo: it will be used by glance, cinder and nova, right before each call to qemu-img info actually20:46
haypotristanC: no, i'm asking in which oslo library. there is no such "oslo" library anymore :)20:46
haypooslo.concurrency maybe, there is already a processutils.py20:47
tristanChaypo: yes, that would be the most logical place20:47
*** bnemec has joined #openstack-oslo20:47
haypotristanC: is there a patch somewhere for oslo.concurrency?20:48
tristanChaypo: no, not yet. I'd have to check how a new script can be installed by a library first20:49
haypotristanC: i never used the prlimit command limit tool. it looks like it changes the limit after the process was started20:49
tristanChaypo: that's it, the code will be pretty straightforward, getopt into resource.setrlimit calls before doing the execve20:50
haypooh, right. currently, setup.cfg of oslo.utils doesn't have any entry point20:50
haypodo you really need a command line script if it's written in python? maybe you can use python -c 'import ...; main()' arg1 arg2 ...20:51
*** sputnik13 has quit IRC20:51
*** jerrygb has quit IRC20:51
tristanChum, the proposed idea is to provide a fallback if prlimit is not already installed20:51
*** sputnik13 has joined #openstack-oslo20:52
tristanC(and prlimit is not installed in most LTS system because it needs util-linux-v2.2120:53
haypotristanC: why not calling setrlimit(RLIMIT_AS) and then exec()?20:53
haypotristanC: prlimit call may occur too late, after the child process already killed the memory, no?20:53
tristanChaypo: ha, that's what we tried, but then you call the setrlimit on a process that may already have exceed the limit, resulting in a harakiri type of outcomes...20:54
tristanChaypo: while a command line utility will apply resource limitation on a controlled environment (post execve)20:55
haypotristanC: i'm not proposing to do that after a fork, but after a fork+exec, so basically in a new program20:55
harlowjaisn't there a post execv hook already in python?20:55
haypotristanC: i'm asking why you really want the prlimit program, it doesn't seem safe20:55
tristanCharlowja: not that I'm aware of20:56
haypoharlowja: nope. subprocess provides preexec_fn which occurs between fork and exec, it's different20:56
harlowjahaypo kk, ya, just checked, preexec, not post20:56
harlowjabut why not use preexec to set limits?20:56
harlowja'this object will be called in the child process just before the child is executed. '20:57
harlowja(just a thought)20:57
tristanChaypo: if we call "setrlimit(RLIMIT_AS) and then exec()", then you might not get to the exec if the process already exceed memory limitation20:57
tristanChaypo: fork is not enough since both process will inherit heap/stack/...  We really needs a fork->execve(prlimit)->execve(target)20:58
harlowjaqemu-img need a python api, lol20:58
haypotristanC: which would a fresh process uses more than ... say 50 MB?20:58
haypotristanC: i'm not sure that you understood what i proposed20:58
haypotristanC: i really propose to write an helper program20:58
*** jerrygb has joined #openstack-oslo20:59
*** jerrygb has quit IRC20:59
haypotristanC: nova spawns the command "wrapper --limit=1G qemu-img", wrapper sets RLIMIT_AS and call exec(qemu...)20:59
harlowjaisn't that what preexec_fn can do?20:59
haypospawns: subprocess.call(...), so run a new process using fork+exec20:59
tristanChaypo: oh right! then what you describe is the "prlimit" utility20:59
*** jerrygb has joined #openstack-oslo20:59
haypoharlowja: nope. see what tristanC explained before, it doesn't work. for example, if nova uses 10G, you cannot set the limit to 1G20:59
*** amrith is now known as _amrith_21:00
harlowjanova is using 10G :-/21:00
harlowjai hope not, lol21:00
haypotristanC: oh. i only saw the first usage of prlimit in the man page :) so yes, it can also run a command21:00
haypoharlowja: it was just an example. preexec_fn doesn't work, see the bug21:01
harlowjahaypo ok ok21:01
tristanCharlowja: long story short, I proposed that, it got merged since it passed nova gate, but then fwaas gate made nova process baloon >2Go of ram and the preexec trick broke their gate, patch got reverted in less than 24hours :)21:01
haypotristanC: so yes, i propose to reimplement a simple prlimit in pure python21:01
haypotristanC: and put this in oslo.concurrency21:01
tristanChaypo: awesome, do you want me to propose such change ?21:01
haypotristanC: in term of API, it can be a new parameter passed to execute(), at least for the end user of the API21:02
haypotristanC: about the need of creating a script: we can use python -c '...code...', but i checked, python -m module ... also works on py221:02
haypo(but it's more limited)21:02
haypotristanC: try: echo data|python -m base6421:03
tristanChaypo: well first we need a prlimit in pure python, then either a prlimit python helper to decide whenever use the nativ implementation or the full python;21:03
tristanChaypo: and then, yes, a "resources_limit" parameter to the execute method would be neat21:03
haypotristanC: hum, i would prefer to keep it simple. so support RLIMIT_AS21:03
haypo(only support RLIMIT_AS)21:04
haypoit can be extended later21:04
tristanChaypo: works for me, the python oneliner sounds like a neat trick21:05
haypohaypo@smithers$ python -m oslo_concurrency.prlimit21:05
haypo('hello world', ['/home/haypo/prog/openstack/oslo.concurrency/oslo_concurrency/prlimit.py'])21:05
haypoah yes, it works :)21:05
haypotristanC: i would prefer to avoid entry points in oslo.concurrency setup.cfg. it's a little bit strange to install a script when you install a library, no?21:05
tristanCmuch better than worying about adding a new script to the toolchain21:05
haypo(at least, unusual)21:05
tristanCok, I'll propose something along those lines for oslo.concurency21:06
haypotristanC: so yes, i'm writing a PoC right now21:07
*** lifeless has joined #openstack-oslo21:10
*** salv-orlando has joined #openstack-oslo21:10
*** yamamoto has joined #openstack-oslo21:11
*** jerrygb_ has joined #openstack-oslo21:12
*** jerrygb has quit IRC21:16
*** jerrygb_ is now known as jerrygb21:17
*** yamamoto has quit IRC21:18
tristanChaypo: oh well, if you've something, please submit it, I'll propose Depends-On change for nova to get the full picture21:22
tristanCthe former change was https://review.openstack.org/#/c/209627/21:23
*** jamielennox is now known as jamielennox|away21:25
openstackgerritVictor Stinner proposed openstack/oslo.concurrency: PoC: add memory_limit parameter to execute()  https://review.openstack.org/24382921:27
haypotristanC: ^^ here is a short PoC written in 30 min21:28
*** kgiusti has quit IRC21:28
tristanChaypo: reading... ( https://review.openstack.org/#/c/243829/1/oslo_concurrency/prlimit.py )21:29
haypohum, maybe "memlimit.py" is a better name, since it only supports a memory limit21:29
haypowe may also make it private, to make it more explicit that it must be not used directly, but through execute()21:29
tristanChaypo: we also need RLIMIT_CPU21:30
haypotristanC: ah?21:30
haypotristanC: is it reliable?21:30
haypotristanC: last time i implemented a sandbox (sic), i implemented the timeout in the parent process21:30
tristanChaypo: it is very reliable, set this to 2 and it will prevent more than 2 second of CPU time (not real time)21:31
tristanChaypo: which is good mitigation against infinit loop21:31
*** itisha has quit IRC21:31
haypotristanC: you get a singal. can you catch the signal?21:31
tristanChaypo: it should make the process exit with a return code != 0, leading to execute() raising an exception21:33
tristanChaypo: the child process shouldn't be able to catch that signal21:33
*** yamahata has joined #openstack-oslo21:33
haypooh, it's SIGKILL. i expected SIGXCPU21:35
haypotristanC: well, i wrote the PoC to show what i had in mind. do you like such API and the design? (wrapper written in pure python)21:36
tristanChaypo: it's looking good to me. However nova dev would like to use the native prlimit tool if available21:38
tristanCwhich should be easy to implement in your design21:38
*** sputnik13 has quit IRC21:42
haypotristanC: i'm not sure that a wrapper written in pure python is something secure, i mean you have to trust the PYTHONPATH environment variable and python modules installed in the system21:42
haypotristanC: but i don't know neither if it's a concern for you :)21:43
*** sputnik13 has joined #openstack-oslo21:43
haypopython3 provides a nice -I option which "isolates" python to be a little bit more secure, but it may break setup where oslo.concurrency is not installed "as expected"21:43
tristanChaypo: that's fine, the issue here is about malicious inputs consumed by qemu-img, the host sanity and PYTHONPATH are out of scope21:45
haypotristanC: right21:46
*** thumpba has quit IRC21:54
*** yamahata has quit IRC21:56
*** thangp has quit IRC21:57
*** jerrygb has quit IRC21:57
haypomodify a docstring and see integration tests failing: done :-) https://review.openstack.org/#/c/243630/21:58
openstackgerritMatt Riedemann proposed openstack/oslo.versionedobjects: Remove remote_object_calls from _BaseTestCase  https://review.openstack.org/24384021:58
*** salv-orlando has quit IRC22:01
*** pradk has quit IRC22:03
*** yamamoto has joined #openstack-oslo22:07
*** salv-orlando has joined #openstack-oslo22:10
openstackgerritMerged openstack/oslo-incubator: tests: remove unused testmods  https://review.openstack.org/24357922:11
openstackgerritJohn Eckersberg proposed openstack/oslo.messaging: rabbit: Add rabbit_queue_ttl option  https://review.openstack.org/24384522:12
*** salv-orlando has quit IRC22:13
openstackgerritJoshua Harlow proposed openstack/taskflow: Move engine options extraction to __init__ methods  https://review.openstack.org/24379322:14
*** _amrith_ is now known as amrith22:15
*** jamielennox|away is now known as jamielennox22:24
*** pm90_ has joined #openstack-oslo22:24
*** pm90__ has joined #openstack-oslo22:26
openstackgerritMatt Riedemann proposed openstack/oslo.versionedobjects: Move compare_obj to the fixture module for external consumption  https://review.openstack.org/24385222:26
mriedemdansmith: there we go ^22:26
dansmithcool22:26
openstackgerritMerged openstack/oslo.utils: Added ICMP 'type' and 'code' checking capability to 'netutils' module  https://review.openstack.org/24066122:28
*** pm90_ has quit IRC22:28
*** boris-42 has joined #openstack-oslo22:30
*** nikhil_k has quit IRC22:33
*** regXboi has quit IRC22:33
*** nikhil has joined #openstack-oslo22:33
*** pm90_ has joined #openstack-oslo22:34
*** pm90__ has quit IRC22:37
*** pm90_ is now known as pratikmallya22:37
*** sputnik13 has quit IRC22:41
*** sputnik13 has joined #openstack-oslo22:41
*** bana_k has joined #openstack-oslo22:52
*** cprmrf__ has quit IRC22:54
openstackgerritBanashankar k proposed openstack/oslo.messaging: Fixing the server example code Added server.stop() before server.wait()  https://review.openstack.org/24329422:58
*** rjaiswal has quit IRC23:05
openstackgerritJoshua Harlow proposed openstack/taskflow: Move engine options extraction to __init__ methods  https://review.openstack.org/24379323:06
*** jerrygb has joined #openstack-oslo23:08
*** sputnik13 has quit IRC23:11
*** rlrossit has left #openstack-oslo23:14
*** dims has quit IRC23:15
*** jecarey_ has quit IRC23:15
*** sputnik13 has joined #openstack-oslo23:16
*** fultonj has joined #openstack-oslo23:20
*** fultonj has left #openstack-oslo23:20
*** pballand has quit IRC23:21
*** jecarey has joined #openstack-oslo23:24
*** stevemar_ has quit IRC23:25
*** stevemar_ has joined #openstack-oslo23:26
*** jecarey has quit IRC23:28
*** sigmavirus24 is now known as sigmavirus24_awa23:29
*** stevemar_ has quit IRC23:30
*** pratikma_ has joined #openstack-oslo23:45
*** salv-orlando has joined #openstack-oslo23:45
*** pratikmallya has quit IRC23:49

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