Earlier  
Posted Nick Remark
#openstack-sdks - 2018-06-12
14:28:35 mordred mnaser: identity_api_version: 3 doesn't control auth - if you want to control auth, you want auth_type: v3password
14:29:01 mordred mnaser: we could add auth_type: v3password to the vexxhost profile
14:29:34 mnaser mordred: that would be ideal given v2.0 is going to be gone in the next few days and a 404 is confusing most likely
14:29:39 mordred mnaser: otherwise it uses the password auth_type, and keystone auth will infer which of v2password and v3password it should use based on domains existing
14:30:44 mnaser mordred: i'm confused
14:30:49 mnaser os_client_config.vendors is gone?
14:30:55 mordred mnaser: it's in openstacksdk now
14:31:07 mnaser ok gotcha
14:31:08 mordred mnaser: openstack.config.vendors
14:31:11 mnaser sorry i'm not up to date with all of this
14:31:22 mordred no worries - it's been shifting around
14:31:30 mordred (and sorry for all the shifting)
14:31:37 mnaser so os-client-config won't see any releases anymore i take it?
14:31:50 mnaser and it looks like you missed a profile for limestone in os-client-config :p
14:32:21 mnaser oh.
14:32:23 mnaser that's a little oppsie
14:32:35 mnaser openstacksdk/openstack/config/vendors has "vendors" inside it too
14:32:37 mnaser which has limestone
14:32:40 mnaser i'll fix that too
14:34:07 openstackgerrit Mohammed Naser proposed openstack/openstacksdk master: Switch VEXXHOST to 'v3password' auth_type https://review.openstack.org/574745
14:35:01 openstackgerrit Mohammed Naser proposed openstack/openstacksdk master: Fix path for Limestone Networks vendor file https://review.openstack.org/574746
14:36:32 openstackgerrit Mohammed Naser proposed openstack/os-client-config master: Shift Limestone Networks profile to openstacksdk https://review.openstack.org/574747
14:36:34 mnaser mordred: those 3 are for you ^
14:37:53 mordred mnaser: we should double-check that v3password for you wrks without domain info
14:38:17 mnaser i think it might just complain about missing domain info (and that might be a better failure than a 404)
14:38:18 mnaser but let me check
14:44:33 mordred mnaser: oh - poo. I think we might be being too clever in the openstack.config code
14:44:34 mnaser mordred: worked and looks like it even added 'default' as domain info
14:44:49 mordred oh - great! my local test was orked then
14:44:55 mnaser or maybe my env wasn't clean
14:45:02 mnaser do you want to double check on your side, i'd trust yours more than mine
14:45:03 mnaser :p
14:45:09 mnaser the weird thing is
14:45:13 mnaser i didnt even add auth_type: v3password ..
14:45:23 mnaser just profile: vexxhost
14:45:25 mnaser and it picked v3
14:46:26 mordred mnaser: I want to make a better local env - I now don't trust anything
14:46:51 mnaser mordred: i hear you can login to horizon and downloads a clouds.yaml file ;)
14:51:19 mnaser mordred: fwiw, dependency was on "shade~=1.27.1"
15:01:51 openstackgerrit Mohammed Naser proposed openstack/python-openstackclient master: Allow setting volume attach status https://review.openstack.org/574719
15:52:25 openstackgerrit Eric Fried proposed openstack/keystoneauth master: raise_exc default in Adapter https://review.openstack.org/574784
16:46:42 openstackgerrit David Moreau Simard proposed openstack-infra/shade master: Add a description field for port_create, port_update https://review.openstack.org/566359
16:47:37 mordred dmsimard: if you get a sec, could you cherry-pick that ^^ to sdk as well?
16:48:00 openstackgerrit David Moreau Simard proposed openstack-infra/shade master: Add a description field for port_create, port_update https://review.openstack.org/566359
16:48:11 dmsimard mordred: oh, sure, I was just fixing the thing Shrews asked me
16:48:19 dmsimard mordred: should I abandon the shade patch then ?
16:49:35 mordred dmsimard: you can keep the shade patch ... are you wanting to get this support in to ansible though?
16:49:59 dmsimard mordred: I was planning on plumbing the thing through to ansible, yeah
16:50:04 dmsimard haven't sent the ansible PR tho
16:55:00 dmsimard mordred: oh, isn't that just a great opportunity to test cross-project depends-on :)
16:58:57 mordred dmsimard: k. if you want it in ansible, then you definitely want to make the patch for openstacksdk - as ansible depends directly on openstacksdk now
16:59:42 dmsimard hmk
17:03:51 dmsimard mordred: it's not immediately clear to me where that translates to in openstacksdk
17:04:39 dmsimard description appears to be a known valid attribute already in http://git.openstack.org/cgit/openstack/openstacksdk/tree/openstack/network/v2/port.py
17:11:10 vadim q
17:11:14 vadim q
17:21:07 mordred dmsimard: in the shade layer - openstack/cloud/openstackcloud.py
17:21:34 mordred dmsimard: you should actually be ale to do "cd ../openstacksdk ; git fetch ../shade ; git cherry-pick FETCH_HEAD"
17:25:04 openstackgerrit David Moreau Simard proposed openstack/openstacksdk master: Add a description field for port_create, port_update https://review.openstack.org/574831
17:25:08 dmsimard mordred: ^
17:25:15 mordred dmsimard: woot! thanks
17:31:44 vadim hi, any ideas https://storyboard.openstack.org/#!/story/2002142 ?
18:00:37 mordred vadim: I believe this is fixed in master but not yet released -- looking
18:02:04 mordred vadim: nope. I was wrong
18:28:55 openstackgerrit Nicola Soranzo proposed openstack/cliff master: Build universal wheels https://review.openstack.org/574846
19:45:56 openstackgerrit Merged openstack/keystoneauth master: raise_exc default in Adapter https://review.openstack.org/574784
23:02:20 mnaser could we get an openstacksdk release anytime soon? :x
23:19:29 openstackgerrit Sami Makki proposed openstack/python-openstackclient master: Fix the `role implies list` command. https://review.openstack.org/557359
23:30:17 mnaser mordred: i'm a bit stuck. i'm trying to use os_client_config (openstacksdk seems to have not gotten me very far) to talk to placement api
23:30:33 mnaser `placement = os_client_config.make_rest_client('placement')` and then making any requests
23:30:47 mnaser spits out a traceback
23:31:03 mnaser http://paste.openstack.org/show/723359/
23:31:15 mnaser if you have *any* few seconds to have a look that'd be great, but i've been stuck for the past hour on this
#openstack-sdks - 2018-06-13
07:55:53 umbSublime when creating a connection with openstack.connect, how can I specify an alternate path to the default clouds.yaml file ?
08:20:43 frickler mnaser: mordred: dtroyer: IIUC it would make sense to release OSC and sdk together, after having this merged https://review.openstack.org/533809
08:39:20 openstackgerrit tianhui proposed openstack/python-openstackclient master: Compute: Add tags support for server https://review.openstack.org/569386
08:41:52 openstackgerrit tianhui proposed openstack/python-openstackclient master: Compute: Add tags support for server https://review.openstack.org/569386
09:39:16 openstackgerrit yanpuqing proposed openstack/python-openstackclient master: Modify the argument when setting floating ip other properties https://review.openstack.org/575057
10:50:53 openstackgerrit yanpuqing proposed openstack/python-openstackclient master: Do not require port argument when updating floating IP https://review.openstack.org/575057
12:17:43 umbSublime How can I specify an arbitrary cloud config file when using the openstacksdk ?
12:18:16 umbSublime rather "arbitrary path for the cloud config file"
12:57:28 mordred umbSublime: you can either set the env var OS_CLIENT_CONFIG_FILE or you can pass a list of paths to the config_files parameter of openstack.config.OpenStackConfig- so like: config = openstack.config.OpenStackConfig(config_files=['/path/to/file']) ; cloud_region = config.get_one(cloud='my_cloud') ; conn = openstack.connection.Connection(config=cloud_region)
12:58:27 mordred frickler: I'm getting failing osc-tips jobs on https://review.openstack.org/#/c/557935/ but it doesn't make immediate sense to me why - does it make sense to you?
12:58:58 mordred mnaser: ah - interesting. "Skipping over invalid version data. No stability status in version."
12:59:12 mordred cdent: ^^ does placement's version discovery doc not have a status field?
13:00:03 mordred cdent: http://paste.openstack.org/show/723359/ is the paste in question
13:00:05 cdent mordred: apparently not. I can fix that
13:00:37 cdent what is it supposed to say. or rather, which of your tomes tells me what to do?
13:01:07 cdent nm, this seems good enough: http://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html#version-discovery
13:01:41 mordred cdent: yes - that would be ideal
13:02:06 mordred mnaser: in the mean time, try setting placement_endpoint_override to your placement endpoint
13:02:19 cdent hmmm. we've always had a id, {min,max}_version, but never a status
13:02:55 cdent what's different from what mnaser is doing and what what the scheduler report client (which uses ksa) is doing?
13:03:09 mordred cdent: when keystoneauth does version discovery it filters out statuses that are not CURRENT or SUPPORTED unless you provide a flag
13:03:28 mordred cdent: I'm not 100% sure yet why it's working in nova
13:04:26 mordred cdent: where can I look at the scheduler report client?
13:04:40 cdent nova/scheduler/client/report.py
13:06:34 mordred cdent: weird. I'll have to dig a bit more to figure it out
13:06:38 umbSublime awesome thanks mordred
13:07:49 cdent mordred: it may be in the way nova.utils.get_ksa_adapter is happening

Earlier   Later