17:00:07 #startmeeting keystone 17:00:08 Meeting started Tue Jun 16 17:00:07 2020 UTC and is due to finish in 60 minutes. The chair is knikolla. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:11 The meeting name has been set to 'keystone' 17:00:13 o/ 17:00:15 o/ 17:00:18 o/ 17:00:18 o/ 17:00:39 o/ on another call for a minute 17:00:41 o/ 17:02:49 how's everyone? no traveling or jetlag returning from ptg for once. 17:04:06 Yeah 17:04:49 debating about working from outside this afternoon 17:05:13 do it! if your screen is bright enough. 17:05:44 i print out everything as pdf on my eink tablet and do some disconnected work and code reviews by the park. 17:06:48 #topic Announcements 17:07:07 We're already at M-1 this week. Time flies. 17:07:20 I've set out some time this afternoon to organize bugs that we can target for M-2. 17:08:23 I will also send out a doodle poll for a retrospective, since we didn't do one during the PTG. (We usually have beer with them) 17:09:23 #topic Review Requests 17:10:03 I have some reviews for the team #link https://review.opendev.org/#/c/731087/ 17:10:16 #link https://review.opendev.org/#/c/720789/ 17:10:27 and https://review.opendev.org/#/c/734549/ 17:12:05 thanks vishakha :) 17:12:29 I will have a look later today 17:12:47 Thanks knikolla 17:13:31 About https://review.opendev.org/#/c/726929/ what is the status then ? 17:14:22 Look like there is proposition to make to different section for oslo_limit, oslo.limit and oslo.limit-ksa, I don't know if any other oslo library are doing the same 17:15:14 I don't know that we have any other libraries that talk to Keystone. 17:15:43 https://review.opendev.org/#/c/733881/ is the proposed solution based on our PTG discussions. 17:16:14 Oh so there was PTG discussion about that ? I miss that 17:17:24 Yeah, it was a brief part of the unified limits topic. 17:17:37 There wasn't much dissension so it wrapped up quickly. :-) 17:18:47 Ok, so if it is a consensus it is ok for me too, my only point is, as an operator, I find it a bit heavy to configure two separate section, and my question was does it was already done during openstack history 17:19:14 and if not, does we agree to do it for oslo_limit 17:21:35 I believe it is an existing pattern (feel free to correct me), and we have to have separate configs in any case because we can't rely on the ksa opts in oslo.limit for the reasons I outlined in the commit message. 17:23:55 It's ok for me too then 17:24:30 I will update the patch and the user guide accordingly, and try to check with openstacksdk when will the next release published 17:24:45 Sounds good, thanks! 17:25:01 cool :) 17:25:53 anything else on the topic? or additional review requests? 17:29:00 jeez i am on the wrong timezone! completely missed this 17:29:07 #topic Open Floor 17:29:15 gshippey: you are perfectly in time 17:29:33 https://bugs.launchpad.net/keystone/+bug/1883247 17:29:33 Launchpad bug 1883247 in OpenStack Identity (keystone) "Able to assign users to projects/groups across different domains" [Undecided,New] 17:30:39 is there a firm decision here? anyone currently deploying federation with OSA currently will be using assignations across domains 17:31:28 i do have it set up like that. our projects are in default, our users are in the default domain and the domain of the idp. 17:32:25 as i responded in the bug report, i am missing the historical context for why it is possible, or if it shouldn't have been possible. either way, it is what it is. 17:32:50 so i am hoping I can just assume what we are doing is fine then :) 17:33:27 yes, i guess the action item out of this is to document that this is possible. 17:34:15 cool, perhaps that wiki i reference should be updated too 17:34:26 if possible 17:34:34 +1 17:34:54 great, thanks :) 17:35:07 yeah, we haven't really used wikis in the past 4 years so everything keystone related in them is definitely stale. 17:36:35 #link https://bugs.launchpad.net/keystone/+bug/1800161 17:36:35 Launchpad bug 1800161 in OpenStack Identity (keystone) "Policy names need to be updated for consistency" [Medium,In progress] - Assigned to Vishakha Agarwal (vishakha.agarwal) 17:37:01 I just wanted to know, is this still in focus for keystone. 17:37:03 ? 17:37:28 Should we update all the policies name as per the https://docs.openstack.org/oslo.policy/latest/user/usage.html#naming-policies 17:38:23 good question. i assume it still is. 17:38:36 You might run into problems with double deprecations if you rename a policy that's already deprecated. 17:39:10 ++, this may need to hold off until we can consume the policy improvements. 17:39:14 I am concerned it might break the operators 17:40:46 Yeah it might need to hold off 17:41:49 i don't think that is a concern since the police in code will handle reading the deprecated policy if people don't update it. 17:42:02 correct me if i'm wrong :) 17:42:42 Hoping lbragstad can give some inputs on it 17:43:25 i don't think it's as high of a priority atm 17:43:50 ++ 17:43:57 i think it's probably better to get things working wrt consistent RBAC and then reassess the naming 17:44:09 ++ 17:44:15 for context... 17:44:42 sure. Thanks knikolla lbragstad 17:44:43 i opened that because using a convention across names made things easier for people using the http_check 17:44:43 * gagehugo put operator hat on 17:44:46 I would want to make sure that any policy name changes make it into the release notes and have high visibility in the docs for upgrading to the release that it lands 17:45:20 a fallback to deprecated names would be good too 17:45:42 that said - i think consistent names are pretty much moot until we find a way to expose them (e.g., a capabilities API) 17:47:13 okay 17:48:20 #link https://bugs.launchpad.net/keystone/+bug/1804041. I wanted to gain some information about nginx 17:48:20 Launchpad bug 1804041 in OpenStack Identity (keystone) "Federation documentation should include examples for nginx" [Medium,Triaged] 17:48:41 So that I can help in upating this documentaion. 17:49:05 I am not sure from where to learn about it. 17:49:34 Mostly nginx is used in keystone 17:54:33 vishakha: not sure what suggestion to offer besides to look up the nginx documentation 17:56:04 Thanka cmurphy I will dig more into it 17:58:20 I guess we can call the meeting to a close, thanks everyone :) 17:58:22 #endmeeting