16:59:40 <knikolla> #startmeeting keystone
16:59:41 <openstack> Meeting started Tue Jun 30 16:59:40 2020 UTC and is due to finish in 60 minutes.  The chair is knikolla. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:59:42 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:59:42 <knikolla> o/
16:59:44 <lbragstad> o/
16:59:45 <openstack> The meeting name has been set to 'keystone'
17:00:10 <cmurphy> o/
17:00:41 <knikolla> good to see everyone :) how've you been?
17:00:43 <raildo> o/
17:00:57 <gagehugo> o/
17:01:03 <gagehugo> busy
17:01:28 <lbragstad> ^
17:01:47 <knikolla> busy is good, i've been struggling with productivity levels.
17:02:08 <bnemec> busy doesn't necessarily mean productive. ;-)
17:02:20 <vishakha> o/
17:02:23 <knikolla> haha, true
17:03:19 <knikolla> #topic Announcements
17:03:58 <knikolla> Last day of July is M-3. I will be proposing that as the deadline for merging specs if there are any. (There is no deadline for spec proposal)
17:04:19 <knikolla> Err, M-2
17:04:47 <knikolla> M-3 can then be feature freeze.
17:05:03 <knikolla> comments?
17:07:54 <knikolla> #topic Bugs
17:08:16 <knikolla> I have started the work of collecting M-2 target bugs at
17:08:21 <knikolla> #link https://bugs.launchpad.net/keystone/+milestone/victoria-2
17:08:59 <knikolla> Going through the bugs list there were quite a few which may have already been fixed and not updated
17:09:12 <knikolla> I am planning on seeing if I can reproduce those during this week
17:09:25 <knikolla> Otherwise I will update their status
17:10:15 <knikolla> If you feel some bug deserves targeting for M-2, please feel free to mark it
17:10:19 <vishakha> I am also focusing in high priority bugs
17:10:30 <vishakha> err,on
17:11:42 <knikolla> thanks vishakha, you are doing great work :)
17:13:45 <vishakha> Thanks knikolla :)
17:14:43 <knikolla> #topic Review Requests
17:15:04 <cmurphy> oh i have one this time https://review.opendev.org/726995
17:16:14 <lbragstad> do we want to keep testing suse?
17:16:33 <knikolla> cmurphy: i had one question with regards to that. what does FORCE do?
17:16:48 <cmurphy> knikolla: oh oops i should remove that, it's not needed anymore
17:17:33 <cmurphy> lbragstad: i don't see much value in us testing different OSs, we just want to make sure the keystone side works
17:17:45 <lbragstad> ok
17:19:45 <vishakha> I have some old review requests and one new #link https://review.opendev.org/#/c/738190 closes bug #link https://bugs.launchpad.net/keystone/+bug/1846817
17:19:45 <openstack> Launchpad bug 1846817 in OpenStack Identity (keystone) "v3/role_assignments filtering exposes unnecessary role assignments" [Medium,In progress] - Assigned to Vishakha Agarwal (vishakha.agarwal)
17:21:37 <vishakha> a easy on #link https://review.opendev.org/#/c/737248/
17:25:17 <lbragstad> i'd like to bounce https://review.opendev.org/#/c/738677/ by anyone who is a sqlalchemy pro
17:27:03 <bnemec> lbragstad: Sounds like you want zzzeek.
17:30:17 <lbragstad> ++
17:30:20 <lbragstad> thanks bnemec
17:30:57 <bnemec> I am nothing if not good at signing other people up for work. :-)
17:31:41 <knikolla> if it's the right people, it's the best skill to have.
17:34:03 <knikolla> i guess we can move on to open floor.
17:34:07 <knikolla> #topic Open Floor
17:37:41 <vishakha> I noticed the same behavior for domain role assignments#link http://paste.openstack.org/show/795353/ same as in for system role assignments #link https://bugs.launchpad.net/keystone/+bug/1846817
17:37:41 <openstack> Launchpad bug 1846817 in OpenStack Identity (keystone) "v3/role_assignments filtering exposes unnecessary role assignments" [Medium,In progress] - Assigned to Vishakha Agarwal (vishakha.agarwal)
17:38:38 <vishakha> Since the bug was specific about system. I was thinking to register another bug for domains
17:40:32 <lbragstad> vishakha are you saying that lines 31+ in your paste should include implied roles?
17:41:09 <vishakha> lbragstad: yes
17:41:57 <vishakha> I think this should be the behavior? Please Correct me I am wrong
17:43:53 <lbragstad> i think your question is valid, but i'm not sure it's similar to https://bugs.launchpad.net/keystone/+bug/1846817 ?
17:43:53 <openstack> Launchpad bug 1846817 in OpenStack Identity (keystone) "v3/role_assignments filtering exposes unnecessary role assignments" [Medium,In progress] - Assigned to Vishakha Agarwal (vishakha.agarwal)
17:45:27 <lbragstad> oh - wait
17:49:12 <lbragstad> i think they're two different bugs and different behaviors
17:49:57 <lbragstad> IMO - only referencing direct role assignment makes sense
17:50:12 <lbragstad> especially since we have a separate API for users to figure out what role implications exist
17:50:27 <lbragstad> so - to me, http://paste.openstack.org/show/795353/ looks like the right thing to do
17:50:37 <lbragstad> but i am curious what others think
17:50:46 <cmurphy> i agree
17:50:54 <cmurphy> the original bug is about leaking too much information
17:51:10 <cmurphy> that paste seems to show it returning just the right amount of information
17:51:17 <lbragstad> ++
17:51:56 <lbragstad> i feel like automatically expanding implied roles when listing all role assignments, or even a subset with filter, will lead to massive responses
17:53:11 <vishakha> lbragstad, cmurphy : okay. Thanks for the clarification.
17:53:49 <lbragstad> no problem
17:57:21 <knikolla> alright, we're almost out of time. thanks all!
17:57:23 <knikolla> #endmeeting