Earlier  
Posted Nick Remark
#openstack-sdks - 2018-06-12
00:48:00 openstackgerrit Merged openstack/python-openstackclient master: Use Server.to_dict() rather than Server._info https://review.openstack.org/573744
01:14:17 openstackgerrit Merged openstack/python-openstackclient master: Optimize _prep_server_detail to avoid redundant find_resource https://review.openstack.org/573760
03:37:04 openstackgerrit qingszhao proposed openstack-dev/os-http master: change default python 3 env in tox to 3.5 https://review.openstack.org/574537
04:44:38 openstackgerrit Merged openstack/python-openstackclient master: Fix server show for microversion 2.47 https://review.openstack.org/573813
05:44:51 arkadefr Shrews: thanks for the reference. It was a "become" in ansible which change my user to root. I explicitly set become=no and it works :)
08:35:57 openstackgerrit XiaojueGuan proposed openstack/os-client-config master: Update links in README https://review.openstack.org/574645
08:49:54 openstackgerrit Dmitry Tantsur proposed openstack/openstacksdk master: Allow configuring status_code_retries and connect_retries via cloud config https://review.openstack.org/573780
08:59:55 openstackgerrit Dmitry Tantsur proposed openstack/openstacksdk master: [WIP] Add set_node_provision_state to baremetal Proxy https://review.openstack.org/570895
10:24:13 openstackgerrit Dmitry Tantsur proposed openstack/openstacksdk master: [WIP] Add set_node_provision_state to baremetal Proxy https://review.openstack.org/570895
11:53:50 rabel_ hi. isn't https://bugs.launchpad.net/python-openstackclient the correct place to file bugs against OSC?
11:57:14 kimamisa rabel: Try here https://bugs.launchpad.net/ubuntu/+source/python-openstackclient
11:58:45 rabel_ kimamisa: thanks. but isn't that just for the ubuntu package?
12:00:37 kimamisa rabel: true. try here: https://storyboard.openstack.org/#!/project/975
12:10:51 rabel_ thanks
12:12:51 dtantsur cdent, edleafe, I wonder if we should point graphql enthusiasts to storyboard. it just occurred to me that it's a perfect use case.
12:14:55 cdent dtantsur: that does make quite a bit of sense, but I'm not sure it satisfies what might be requirement: demonstrating usefulness (and providing feedback space) to openstack users
12:15:35 dtantsur well, it would allow to collect developers' feedback before throwing users under the train :)
12:15:42 dtantsur and get some mindshare
12:16:09 dtantsur because I wonder: we implement neutron-NG in graphql. how many deployers are going to expose their users to it?
12:16:20 dtantsur I'm pretty my employer won't be the first :-/
12:32:23 mnaser good morning everyone
12:32:58 mnaser https://review.openstack.org/#/c/573997/1 has a +2 from dtroyer but it looks like https://review.openstack.org/#/c/557359/ came before me and does a much better job :)
12:33:42 mnaser i've abandoned my patches but it looks like sami was nice enough to push up a patch end of march and this thing has been broken since
12:40:04 dtroyer mnaser: the dangers of non-contiguous review time is revealed…
12:55:02 edleafe dtantsur: That's a great idea. I might have some time today to start investigating moving the API-SIG stuff to storyboard.
12:58:04 openstackgerrit Mohammed Naser proposed openstack/python-openstackclient master: Allow setting volume attach status https://review.openstack.org/574719
12:58:58 mnaser that's a simple one and it seems to have been tied toa long standing bug too
13:06:47 frickler dtroyer: seems https://review.openstack.org/573202 needs a fresh +w after the devstack dependency merged
13:28:07 cdent edleafe: you probably already know this, but diablo_rojo is your person for all that
13:29:50 edleafe cdent: ack
14:17:18 mnaser mordred: is this considered a "bug"? using clouds.yaml file with profile: vexxhost .. it defaults to v2.0
14:18:00 mnaser mordred: user added "auth_url: https://auth.vexxhost.net/v3/" and got the "missing domain" errors after
14:18:19 mnaser so if there is no domain listed, and even if it explicitely says "identity_api_version: 3" .. it'll still do v2?
14:18:33 mnaser i'm worried because v2.0 is bye-bye on our cloud today ..
14:25:51 dtroyer frickler: done
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

Earlier   Later