Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2019-11-20
08:35:08 eandersson https://review.opendev.org/#/c/695139/4/senlin/profiles/base.py
08:35:12 eandersson This seems to fix the memory leak
09:34:56 openstackgerrit Daniel Bengtsson proposed openstack/osc-lib master: Fix the requirement of keystoneauth1. https://review.opendev.org/695022
13:39:40 openstackgerrit Matt Riedemann proposed openstack/python-openstackclient master: Provide stderr in exception when check_parser fails https://review.opendev.org/682939
17:04:15 efried dtantsur, mordred: is sdk set up for swift such that it would standard ksa conf opts through our shiny new oslo_config kwarg?
17:04:21 efried would accept*
17:05:24 dtantsur efried: it *seems* so. at least we're already using it in this manner in ironic/ironic-inspector.
17:05:53 efried okay, neat. And... we decided the conf section needs to be [swift], not [object-store], I think.
17:06:03 efried which is slightly sad-making
17:08:40 dtantsur yep, I think so
17:08:54 dtantsur it can be easily hacked around, lemme show
17:09:00 efried confirmed (openstack.config.cloud_region.from_conf)
17:09:06 efried nah, sokay.
17:09:20 efried Hacked around without changing code? (Now I'm curious)
17:09:39 dtantsur similar hack https://opendev.org/openstack/ironic/src/branch/master/ironic/drivers/modules/inspector.py#L54-L57
17:09:46 dtantsur no, with code
17:10:18 efried oh, yeah, if we wanted to support it in code, we would just do it in openstack.config.cloud_region.from_conf, the logic would be easy, look for a conf section by service type or project
17:10:41 efried but I don't really care to do that now.
17:36:28 openstackgerrit Merged openstack/python-openstackclient master: Provide stderr in exception when check_parser fails https://review.opendev.org/682939
18:32:40 eandersson mordrerd
18:32:57 eandersson you here?
19:07:51 eandersson * mordred
#openstack-sdks - 2019-11-21
13:21:07 openstackgerrit Daniel Bengtsson proposed openstack/python-openstackclient master: Stop testing python 2 in tox. https://review.opendev.org/695427
14:06:05 openstackgerrit Daniel Bengtsson proposed openstack/python-openstackclient master: Stop testing python 2 in tox. https://review.opendev.org/695427
14:07:31 openstackgerrit Daniel Bengtsson proposed openstack/python-openstackclient master: Stop testing python 2 in tox and zuul. https://review.opendev.org/695427
15:44:32 openstackgerrit Merged openstack/api-sig master: Fix wrong openstack review link . https://review.opendev.org/695126
16:00:34 elmiko API SIG office hour is now open!
16:44:25 dtantsur wow, lonely elmiko!
16:44:30 elmiko hehe
16:44:35 dtantsur hey-hey, how is life?
16:44:47 elmiko not bad, got an acceptance for devconf, so yay \o/
16:44:57 dtantsur devconf.cz?
16:44:59 elmiko yeah!
16:45:11 dtantsur congrats :) (if you see travelling to Brno as a good thing)
16:45:20 elmiko i actually like brno
16:45:24 dtantsur heh
16:45:28 dtantsur I lived there for too long ;)
16:45:28 elmiko the travelling part not so much lol
16:45:31 elmiko fair
16:45:46 elmiko how's life for you? new apartment all settled?
16:47:37 dtantsur well, not all :)
16:47:48 dtantsur I still haven't got a kitchen. Hopefully next week..
16:47:51 elmiko oh wow
16:47:57 elmiko that's tough
16:48:08 dtantsur yeah. interesting experience :)
16:48:14 elmiko lots of doner?
16:48:16 elmiko XD
16:48:20 dtantsur I do have a few appliances that make home cooking possible
16:48:42 elmiko so you haven't built a fire in the middle of the kitchen yet?
16:48:50 dtantsur haha, no
16:48:52 elmiko =)
16:49:04 dtantsur the kitchen space is not full of future kitchen details
16:49:15 dtantsur with the only thing actually working there is the fridge
16:49:26 dtantsur so I can have cold beer, what else do I need?
16:50:08 elmiko good point
16:50:18 elmiko plus cold borsht XD
16:51:43 elmiko sorry, борщ
16:56:29 dtantsur you need it warm :)
16:57:42 elmiko you're gonna need more kitchen then my friend XD
17:01:26 elmiko well, i'm about to pack up shop. have a good one dtantsur o/
17:09:59 dtantsur o/
#openstack-sdks - 2019-11-22
05:54:47 eandersson mordred I might roll something like this until we can find a better idea on how to fix the memory leak https://review.opendev.org/#/c/695628/1/senlin/drivers/os/nova_v2.py
05:58:58 eandersson nvm openstacksdk is leaking even with that
06:14:01 eandersson I think I figured it out mordred
06:14:31 eandersson https://github.com/openstack/openstacksdk/blob/master/openstack/connection.py#L435
06:24:39 eandersson nvm
07:50:51 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
10:38:20 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
11:04:47 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
11:13:50 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
11:28:24 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
11:32:34 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add reset_interfaces argument to patch_node https://review.opendev.org/689414
11:39:08 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
12:10:24 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
12:57:12 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
13:05:14 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
13:07:35 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
13:19:27 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
13:31:32 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
13:38:36 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
14:19:11 openstackgerrit Daniel Bengtsson proposed openstack/python-openstackclient master: Stop testing python 2 in tox and zuul. https://review.opendev.org/695427
14:37:30 openstackgerrit Thomas Goirand proposed openstack/python-openstackclient master: Display the host field and allow filtering by host https://review.opendev.org/695586
17:40:55 efried dtroyer: Sanity check me here please: python-openstackclient is *not* considered a "client library" for purposes of "wait until XX to drop py2 support", right??
17:41:19 efried that rule is for projects that are programmatically consumed by other projects, and osc is not.
17:41:41 efried (programmatically in python; CLI scripting doesn't count)
18:56:40 dtroyer efried: OSC is considered to be a client library in the release freeze timelines because other projects have dependencies on it. For that case the Python API vs CLI distinction doesn't matter. I usually operate with that interpretation for most things without a specific reason otherwise.
18:59:10 efried dtroyer: the specific reason in this case is whether to wait to merge the patch tha removes py2 testing from tox.ini/zuul.
18:59:28 dtroyer specifcally about dropping py2, I am not pushing the envelope to do that quickly but there is a point that not doing so impacts other projects. Think of it as the inverse of lazy-loading, we'll do it when we need to unless someone comes along with the time/energy to do it sooner.
18:59:31 efried if there's nobody that consumes osc by importing it python-wise, there's no reason to wait
18:59:49 efried well, there's a patch in flight being actively worked.
19:00:07 efried https://review.opendev.org/#/c/695427/
19:05:01 dtroyer I can't say that nobody is doing that, the only ones I knew about were some plugins a while back, which is why osc-lib exists now. Hopefully they all have changed.
19:06:00 efried okay, fair enough, might be worth a procedural -2 on ^ in that case
19:06:24 efried I can't imagine how/why anybody could/would be importing python-openstackclient, but whatevs.
19:06:41 efried oh, I think I see what you're saying about plugins.
19:06:52 dtroyer I'll take a look, I'm not sure how else to find out who breaks without just merging it though, I suppose we can revert if necessary
19:06:59 efried well
19:07:15 efried the only way we actually break is if we a) merge this and then b) also merge something that doesn't work in py2
19:07:23 efried given the velocity of the project, that seems vanishingly unlikely.
19:07:56 dtroyer true, I can't remember offhand if any of that changes the jobs that other projects may consume

Earlier   Later