Earlier  
Posted Nick Remark
#openstack-sdks - 2018-12-12
15:31:46 dtantsur looks like the fix
15:33:41 Shrews dtantsur: i just rechecked your change to verify if that fixes it for us
15:34:19 dtantsur Shrews: I suspect the new version is not in u-c yet, is it?
15:36:18 Shrews hrm, the PR seems to be a bit different from what we experienced https://github.com/sqlalchemy/dogpile.cache/issues/139
15:36:27 Shrews dtantsur: oh, probably not
15:45:45 Shrews mordred: dtantsur: tested locally, that does NOT appear to fix us :(
15:47:13 dtantsur :(
15:49:31 mordred :(
16:00:57 Shrews aaaaand now our nodepool src test is failing b/c it cannot find a python package. what a fun day
16:05:17 Blotis test
16:51:26 openstackgerrit Merged openstack/python-openstackclient master: Use devstack functional base job https://review.openstack.org/526117
16:53:18 Shrews mordred: i'm wondering if we even need our custom version of cache_on_arguments() anymore. for one, we don't use the 'resource' arg. for another, the original need for it (according to https://review.openstack.org/171456) was because of needing to set the invalidate func, but it looks to me that dogpile.cache always does that for us
16:54:02 Shrews mordred: we tried the per-resource thing, but ended up reverting it: https://review.openstack.org/362901
16:54:47 Shrews maybe i'll try a patch that eliminates our version and see what happens
16:59:54 mordred Shrews: yah - I really want to go back and revive that per-resource thing - I was thinking once we have the sdk and shade layers tied together a bit better, we could potentially do the per-resource sharing in the Resource layer
17:00:27 mordred Shrews: but ... I think maybe just making our current version simplier if it works is probably a great idea
17:05:39 openstackgerrit David Shrewsbury proposed openstack/openstacksdk master: WIP: test using standard cache method https://review.openstack.org/624767
17:06:26 Shrews that ^^^ is probably going to fail spectacularly, but should be fun to watch
17:09:24 Shrews oh, yeah. that's all wrong
17:13:27 Shrews that's a whole lot more complex than i initially thought, so nm :/
17:49:06 edleafe elmiko: Here's a first pass at the blurb for the OSF: http://paste.openstack.org/show/737157/
20:03:03 kmalloc mordred: haven't gotten to that sdk issue yet
20:03:29 kmalloc mordred: on my todo, some dr stuff came up and needed quick attention
20:03:47 kmalloc i'll probably have some kind of direction with that and the other dogpile bits by tomorrow.
20:06:47 Shrews kmalloc: oh, you switched irc nicks on me at some point
20:07:16 Shrews things begin to make sense
20:10:10 kmalloc Shrews: yes... like... a long while ago i swapped nics :P
20:10:56 Shrews i may not be quick, but i sure am slow
20:11:07 morgan Shrews: better?
20:11:09 morgan Shrews: :P
20:11:26 Shrews morgan: i think you are having an identity crisis
20:12:23 morgan nah, just /nick was not letting me go to morgan from kmalloc... oddly
20:24:02 morgan anyway...
20:26:50 mriedem does ksa impose any kind of http response timeout?
20:27:47 mriedem hmm https://github.com/openstack/keystoneauth/blob/ccf6cb79033b2083d9177823094f7836eb68ae0d/keystoneauth1/session.py#L248
21:20:51 morgan mriedem: hmm
21:21:04 morgan mriedem: not by default
21:26:48 mriedem i saw the --timeout option in the CLI defaults to 600
21:26:52 mriedem but that's still more than plenty
21:34:39 morgan ah yeah
21:34:51 morgan keystoneauth is very liberal in the "we don't force timeouts"
21:35:00 morgan but consumers of KSA aren't so easy going :P
21:35:04 morgan but 600s is a long timeout
#openstack-sdks - 2018-12-13
05:50:51 openstackgerrit Rajat Dhasmana proposed openstack/python-openstackclient master: Fix: Restore operation returns 'VolumeBackupsRestore' object is not iterable https://review.openstack.org/624860
07:44:08 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624873
07:47:57 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624874
07:53:00 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624875
07:59:33 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624879
08:03:11 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624880
08:04:05 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624881
08:04:13 openstackgerrit Rajat Dhasmana proposed openstack/python-openstackclient master: Fix: Restore operation returns 'VolumeBackupsRestore' object is not iterable https://review.openstack.org/624860
08:08:20 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624883
08:09:57 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624884
08:11:51 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624886
08:12:50 openstackgerrit machunnan proposed openstack/js-openstack-lib master: change http:// to https:// https://review.openstack.org/624887
08:38:38 openstackgerrit machunnan proposed openstack/js-openstack-lib master: Capitalizes the first letter -- should to Should https://review.openstack.org/624891
08:43:07 openstackgerrit machunnan proposed openstack/js-openstack-lib master: Capitalizes the first letter -- should to Should https://review.openstack.org/624892
11:53:09 frickler mordred: Shrews: is there any news regarding the dogpile.cache issue to fix broken nodepool jobs?
12:59:08 Shrews frickler: mordred has a review up to requirements to limit the version. and morgan is going to look into the actual dogpile.cache change for us
13:00:02 Shrews that's all i know before coffee
13:09:48 frickler Shrews: thx, found the reqs patch, seems that it needs a bug report/story attached. do we have a simple reproducer yet?
13:12:08 Shrews frickler: i have one. 1 sec
13:17:30 Shrews frickler: http://paste.openstack.org/show/737212/
13:30:55 frickler Shrews: thx, created https://storyboard.openstack.org/#!/story/2004605 from that and will add to the reqs patch
13:31:06 frickler mordred: morgan: ^^ fyi
14:33:00 elmiko edleafe: ack, thanks
14:33:36 edleafe elmiko: it's brief
14:34:17 elmiko yeah, but also contains good info imo
14:34:38 cdent I thought it was elegantly sufficient
14:34:42 elmiko me too
14:34:49 elmiko i like it, no objections here edleafe
14:38:09 edleafe okie dokie
14:42:23 elmiko edleafe: reading it over again, i think the only thing that might make me a tad nervous is that it sounds like we could answer all api related issues that come up. i wonder if that gives the impression that any project-specific api issues are fair game to ask the sig? (maybe i'm reading too much, maybe this isn't a concern)
14:44:05 cdent elmiko: to some extent that's supposed to be what SIG means
14:44:14 cdent we are a house for people who care about APIs
14:44:42 elmiko i guess i meant more like, "hey this call to service X isn't working for me, why not? (insert arcane curl command here)"
14:45:05 elmiko and i imagine we would definitely point that person in the right direction
14:45:15 cdent "hey caller, it looks like you're using nova, you might want to talk to ..."
14:45:25 elmiko anyways, it was just a thought. i don't think it's a concern, but if i pushed to make a critique.
14:45:32 elmiko yeah
14:45:52 elmiko i still don't have an objection, i was just trying to go deeper with due diligence =)
14:51:15 edleafe elmiko: Sorry, was afk
14:51:47 edleafe I can see what you mean, but I kinda think that's a good thing. The more interest in the SIG, the better
14:52:16 elmiko i like that attitude =)
14:52:17 edleafe Like cdent said, we may not have the answers, but we might help point people to better resources
14:52:25 elmiko agreed
14:56:41 elmiko thanks for indulging me ;)
15:11:57 cdent elmiko: speaking of indulgences, how did your aqua vit settle in at home. did it even make it home?
15:12:31 elmiko haha, yes! it made it home
15:12:35 elmiko it's been a big hit =)
15:13:02 elmiko people are becoming scared at the volume of clear liquors i am pushing on them when they visit XD
15:13:35 cdent here, try this mysterious thing!
15:23:49 elmiko basically
15:24:31 elmiko at least with the eau de vie they kinda get it, but when i start digging out stuff slike slivovice and awamori things get /interesting/ =D
15:25:24 elmiko the liquor cabinet is starting to look a little nuts though, like "does this guy have a problem?" haha
16:00:17 edleafe API-SIG Office Hour has begun
16:00:43 edleafe Get your feet off the table!! Were you raised in a barn?
16:01:38 elmiko sadly no, just a normal house
16:03:10 edleafe dtantsur: around? Wanted to get your feedback on http://paste.openstack.org/show/737157/
16:03:32 edleafe It's the little blurb for the OpenStack Foundation Annual Report about our SIG

Earlier   Later