15:02:18 #startmeeting keystone 15:02:18 Meeting started Tue Jul 19 15:02:18 2022 UTC and is due to finish in 60 minutes. The chair is dmendiza[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:18 The meeting name has been set to 'keystone' 15:02:28 #topic Roll Call 15:02:33 Courtesy ping for admiyo, bbobrov, crisloma, d34dh0r53, dpar, dstanek, hrybacki, knikolla, lbragstad, lwanderley, kmalloc, rodrigods, samueldmq, ruan_he, wxy, sonuk, vishakha, Ajay, rafaelwe, xek 15:02:42 o/ 15:03:13 o/ 15:03:23 o/ 15:03:29 lurking, conflict with another meeting 15:05:31 Hi y'all 15:05:35 Let's get started 15:05:41 #topic Review Past Meeting Action Items 15:05:53 I'm still kicking this bandit action item down the road 15:06:01 Actually, let me try that real quick 15:06:26 #link https://meetings.opendev.org/meetings/keystone/2022/keystone.2022-07-12-15.00.html 15:06:56 o/ 15:08:05 OK, kicking off that bandit run 15:08:34 The other action item was about M2 15:09:56 Hmmm ... doesn't look like Keystone is in the Milestone-2 releases 🤔 15:13:20 #action dmendiza[m] to check on milestone-2 release 15:13:44 back to Bandit 15:13:54 looks like I was able to run `tox -e bandit` from a fresh clone without any problems 15:14:04 using Python 3.9 15:14:21 so I think we're good? Not sure admiyo is around anymore anyway? 15:14:37 We probably don't need to revisit this. I'll move out of the agenda 15:15:12 #info `tox -e bandit` appears to work with a fresh clone of keystone in Python 3.9 15:15:31 #topic Liaison Updates 15:15:36 No updates from me. 15:15:45 #topic OAuth 2.0 15:15:52 hi h_asahina 15:15:57 hi 15:16:45 i've found the line about OAuth2.0 on the etherpad 15:16:57 > We should consider moving the MTLS spec to AA 15:17:21 Yeah, we were discussing that during the last reviewathon 15:17:33 does this mean you want to postpone merging to the next release? 15:17:38 and given our review capacity it would probably be better to move that spec to the next cycle 15:18:32 I think it's going to be difficult for us to merge everything we have pending and also the mTLS work 15:21:04 I understand, but to be honest, we are in trouble if the spec won't be merged as scheduled. 15:21:38 Oh? 🤔 15:23:34 we have started to develop our other projects based on the this feature described in the spec. 15:24:01 /the this/this/ 15:25:53 i understnad there's not enough keystone cores although there are some other specs to review. 15:26:24 I understand it may be disappointing to have to wait another cycle, but I think this is a feature that we don't want to rush. We are ceirtanly wanting to get the work merged in the AA cycle. 15:28:05 i'm afraid of that the same thing will happen in the AA cycle 15:29:10 I see. I am hoping that by the time AA cycle starts we will be able to have a few more core reviewers 15:30:15 I hope that too. all we can do is submitting the spec and patch on schedule believing it works. 15:31:16 starting from spec review again in the AA release makes me a little bit anxious 15:31:31 I do appreciate you continuing to work with us to get these features merged into Keystone. 15:31:57 We don't have to wait until AA to review the spec 15:32:05 We can continue to review the spec now 15:32:24 the implementation will have to wait until AA to be merged 15:32:29 ok, there's no room for negotiation? 15:34:26 I think that the best that we can do is continue to review the spec and implementation and see how far we get before Milestone-3 15:34:41 but there is a possibility that we will run out of time 15:35:54 also can i think there's a few possiblity to merege this spec before Milestone-3? 15:36:44 We have about ~5 weeks 15:38:58 I am not sure how we can merge the spec and all the required work in that time? 🤔 15:39:04 I think we should be able to merge the spec 15:40:09 i don't think we should rush, but i guess we can give it a shot. 15:40:39 agreed knikolla 15:40:59 let's play it by ear, h_asahina and see how far we can get in the next few weeks 15:41:32 thanks. it will be helpful. 15:42:26 dmendiza[m]: d34dh0r53: xek: we can try to go through the oauth 2.0 with mtls RFC so that on Friday's meeting we have done the background reading and can go through the spec as a group. 15:42:39 go through during the week* (homework) 15:42:41 ack 15:43:00 #action (all) go through the OAuth 2.0 spec 15:43:29 Sounds good 15:43:41 Let's move on to Secure RBAC 15:43:59 #topic Secure RBAC 15:45:06 Not a whole lot of progress on my end 15:45:16 Looks like this week's pop-up meeting is canceled 15:45:26 the next meeting will be on August 2 15:45:41 I'll definitely join tne next one and see where we're at 15:45:56 I'll also probably make some time before M-3 to do the needful for Keystone 15:46:54 Any questions/comments about Secure RBAC 15:46:55 ? 15:50:41 OK, moving on 15:50:54 #topic open dicussion 15:51:03 Any other topics y'all want to talk about? 15:58:09 Alrighty then, y'all. 15:58:16 See you Friday for the reviewathon. 15:58:22 Please read your homework before then. 15:58:26 #endmeeting