| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2017-11-16 | |||
| 19:07:55 | mordred | dtroyer: ^^ we seem to have both been thinking about the same general area this morning :) | |
| 19:11:04 | dtroyer | Nice, thanks. That'll work for now, eventually the SDK instantiation should move to Clientmanager directly… | |
| 19:13:23 | openstackgerrit | Merged openstack-infra/shade master: Remove setting of version/release from releasenotes https://review.openstack.org/520667 | |
| 19:59:05 | mordred | dtroyer: ++ | |
| 21:05:46 | openstackgerrit | Andreas Jaeger proposed openstack/os-client-config master: Remove setting of version/release from releasenotes https://review.openstack.org/520790 | |
| 21:06:26 | openstackgerrit | Andreas Jaeger proposed openstack/osc-lib master: Remove setting of version/release from releasenotes https://review.openstack.org/520791 | |
| 21:13:42 | dklyle | dtroyer, openstackclient question if you have a minute | |
| 21:13:56 | dtroyer | dklyle: sure | |
| 21:14:08 | dklyle | OS_DOMAIN_ID is from the project scoped token? | |
| 21:14:25 | dklyle | not the user's domain, but the project domain? | |
| 21:15:22 | dklyle | Horizon doesn't provide that value, but gophercloud requires it, want to provide the proper value | |
| 21:15:31 | dklyle | in the openrc file | |
| 21:16:49 | dklyle | I'm missing something in the openstackclient code as I couldn't tell where the env is read | |
| 21:17:00 | dklyle | only some documentation | |
| 21:17:24 | dtroyer | it's a ksa thing actually, and the exact context depends on which plugin is in use | |
| 21:17:44 | dtroyer | but this question should be answerable…I'm looking through KSA now | |
| 21:18:05 | dklyle | ksa is the piece I was missing | |
| 21:19:03 | dtroyer | but for gophercloud anting it, I have no idea if that uses things in the same way | |
| 21:19:17 | dtroyer | it should, for all of our sanity | |
| 21:19:44 | dklyle | let me double check gophercloud's usage | |
| 21:21:27 | dklyle | I think they intend project domain. It's used for auth when providing username | |
| 21:22:42 | dklyle | the possibility of domain scoped tokens has domain id very complicated in Horizon as does v3 policy | |
| 21:22:43 | dtroyer | the KSA plugin classes have domain_id and project_domain_id | |
| 21:23:17 | dklyle | so domain_id is the domain gophercloud is auth'ing to | |
| 21:24:16 | dtroyer | now that I think about it, I'm not sure how it works to use different domains for user and project. this is just across the edge of my keystone experience | |
| 21:24:42 | dklyle | you can cross-domain role assignments | |
| 21:24:56 | dklyle | as long as you have a role in domain-x you can log into it | |
| 21:25:01 | dtroyer | ok. I've never actually used a non-default domain cloud | |
| 21:25:14 | dklyle | regardless if your user is from domain-y | |
| 21:25:58 | dklyle | I think will lead me to the right value, I just wanted to make sure the intention of osc for that value | |
| 21:26:48 | dklyle | *I think this | |
| 21:26:50 | dklyle | thanks | |
| 21:45:56 | openstackgerrit | Monty Taylor proposed openstack-infra/shade master: Add method to cleanup autocreated image objects https://review.openstack.org/520653 | |
| 21:48:03 | mordred | dklyle, dtroyer: we should actually ping gophercloud and get them to split it- OS_USER_DOMAIN_ID and OS_PROJECT_DOMAIN_ID are important distinctions | |
| 21:49:02 | mordred | dklyle: but yes- OS_DOMAIN_ID is for domain scoped tokens - it's not (as I originally thought it should be) a thing one could use if OS_USER_DOMAIN_ID and OS_PROJECT_DOMAIN_ID were the same thing | |
| 21:52:08 | dklyle | mordred, I need to look at ksa more closely | |
| 21:52:22 | mordred | dklyle, dtroyer: also - while I'm pointificating - in case it's useful information - OS_(USER|PROJECT)_DOMAIN_ID are only needed if USERNAME or PROJECT_NAME are being used. if USER_ID or PROJECT_ID are used, domain information is not required | |
| 21:52:22 | dklyle | but I agree they are very different things | |
| 21:52:41 | mordred | tl;dr - user names and project names are only unique within a domain, but ids are unique globally | |
| 21:52:58 | dklyle | right | |
| 21:53:20 | dklyle | gophercloud only requires OS_DOMAIN_ID if using username | |
| 21:54:10 | mordred | dklyle: speaking of ksa - we've added a bunch of things to it this past cycle that may be useful at your python layer - I've been meaning to go poke through code and check | |
| 21:54:54 | mordred | dklyle: yah - that's a thing I'd like to chat with him about- because for people using envvars or clouds.yaml files that would result in different auth behavior between gophercloud and ksa-based things like python-openstackclient | |
| 21:55:07 | dklyle | I can make a PR to gophercloud, so it better aligns with ksa | |
| 21:56:00 | mordred | at least make sure it supports OS_(USER|PROJECT)_DOMAIN_(ID|NAME) - since those are the settings that are most likely be in people's clouds.yaml or openrc files | |
| 21:56:19 | dklyle | mordred, which python layer? | |
| 21:56:22 | mordred | whether it also has different behavior if OS_DOMAIN_ID is there is likely not as big a deal | |
| 21:56:31 | dklyle | yes Horizon doesn't populate an OS_DOMAIN_ID | |
| 21:56:41 | dklyle | in the openrc, hence the issue | |
| 21:56:49 | mordred | dklyle: ++ horizon is doing the right thing imo | |
| 21:57:31 | dklyle | finally | |
| 21:57:48 | mordred | dklyle: the openstack_dashboard code - but nevermind, that's using python-*client for things, so the discovery bits in ksa will bubble up through those | |
| 21:58:09 | dklyle | we talked at the last PTG about ksa integration | |
| 21:58:16 | dklyle | tighter integration | |
| 21:58:26 | mordred | oh neat! I should have dropped in and lurked on that | |
| 21:58:49 | dklyle | we've implemented duplicate functionality over the years, some probably predating | |
| 21:58:59 | mordred | there's definitely some catalog/version-discovery things that I *think* could simplify some things for you ... but I haven't had a chance to look deeply yet | |
| 21:59:02 | mordred | yah. | |
| 21:59:20 | dklyle | our biggest concern is stability | |
| 21:59:23 | mordred | ksa is awesome, but its existence definitely came a bit late | |
| 21:59:37 | dklyle | and someone that understands enough that has enough time to take it on | |
| 21:59:42 | mordred | that's the hardest part | |
| 21:59:45 | dklyle | the same story | |
| 21:59:48 | dklyle | yeah | |
| 22:00:05 | mordred | dang. there was a horizon bug I was going to mention ... but now I forgot what it was ... | |
| 22:00:33 | dklyle | if I can carve out a largish chunk of time, I might try to take it on, but I haven't yet | |
| 22:01:59 | mordred | dklyle: I'll try to help some - the keystoneauth work I needed to get done last cycle is 95% done - doing some work to help consume it isn't a terrible idea | |
| 22:12:07 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Remove ansible functional tests for now https://review.openstack.org/520602 | |
| 22:12:08 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Add OSC tips unittest jobs https://review.openstack.org/520812 | |
| 22:12:48 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Remove ansible functional tests for now https://review.openstack.org/520602 | |
| 22:12:49 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Add OSC tips unittest jobs https://review.openstack.org/520812 | |
| 22:13:54 | mordred | dtroyer: ^^ addition of the osc tips job so that we can make sure we don't break osc ... | |
| 22:14:02 | mordred | dtroyer: should we add the functional test job too? | |
| 22:14:40 | dtroyer | the functional-tips job actually does more, the unit tests mock out a lot | |
| 22:14:45 | mordred | dtroyer: functional-tips is non-voting for osc, so I'm guessing if we did we'd want to also make it non-voting for sdk yeah? | |
| 22:15:02 | dtroyer | for now, yes, I'm close to making it voting though | |
| 22:15:40 | mordred | cool | |
| 22:16:36 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Add OSC tips jobs https://review.openstack.org/520812 | |
| 22:16:50 | mordred | dtroyer: k- that has the functional tips jobs now too | |
| 22:18:28 | openstackgerrit | Merged openstack/python-openstackclient master: Remove setting of version/release from releasenotes https://review.openstack.org/520734 | |
| 23:49:58 | openstackgerrit | Merged openstack/osc-lib master: Remove setting of version/release from releasenotes https://review.openstack.org/520791 | |
| #openstack-sdks - 2017-11-17 | |||
| 02:38:30 | openstackgerrit | chenyb4 proposed openstack/python-openstacksdk master: Add cluster support force delete parameter when cluster/node delete https://review.openstack.org/520854 | |
| 03:41:39 | openstackgerrit | yangweiwei proposed openstack/python-openstackclient master: Fix credentials in create, update and list. https://review.openstack.org/519254 | |
| 04:42:33 | openstackgerrit | Deepak Mourya proposed openstack/keystoneauth master: Remove setting of version/release from releasenotes https://review.openstack.org/520882 | |
| 09:39:17 | openstackgerrit | Jose Castro Leon proposed openstack/python-openstackclient master: Add support for endpoing filter commands https://review.openstack.org/520614 | |
| 10:07:50 | openstackgerrit | Rajat Sharma proposed openstack/python-openstacksdk master: Remove setting of version/release from releasenotes https://review.openstack.org/521050 | |
| 15:17:38 | openstackgerrit | Merged openstack-infra/shade master: Cleanup objects that we create on behalf of images https://review.openstack.org/520652 | |
| 15:26:15 | openstackgerrit | Merged openstack-infra/shade master: Add method to cleanup autocreated image objects https://review.openstack.org/520653 | |
| 18:44:18 | openstackgerrit | Merged openstack/openstackclient master: Zuul: add file extension to playbook path https://review.openstack.org/516113 | |
| 21:33:30 | openstackgerrit | Merged openstack/python-openstackclient master: Add logic to handle old and new sdk constructor https://review.openstack.org/520688 | |
| 21:44:03 | openstackgerrit | Merged openstack/python-openstackclient master: Prepare for os-clinet-config to go away https://review.openstack.org/520675 | |
| #openstack-sdks - 2017-11-18 | |||
| 00:21:27 | thingee | oh I guess everything already got merged for the move. was camping | |
| 00:21:35 | thingee | /move/migration/ | |
| 00:21:43 | thingee | shade->openstacksdk | |
| 00:22:24 | thingee | dtroyer: I still have not heard back about the plans micro version plans for osc. pinged you at the summit. | |
| 03:03:14 | SamYaple | thingee: there is certainly more to do, but a huge chuck of mordreds work got merged. go mordred | |
| 17:20:55 | mordred | \o/ | |
| #openstack-sdks - 2017-11-19 | |||
| 05:49:21 | openstackgerrit | Julia Kreger proposed openstack-infra/shade master: WIP: Complete move of baremetal machine tests https://review.openstack.org/502333 | |
| 06:34:52 | openstackgerrit | Julia Kreger proposed openstack-infra/shade master: Complete move of baremetal machine tests https://review.openstack.org/502333 | |
| 06:54:19 | openstackgerrit | Julia Kreger proposed openstack-infra/shade master: De-client-ify baremetal node_set_provision_state https://review.openstack.org/499773 | |