16:00:02 #startmeeting keystone 16:00:03 Meeting started Tue Mar 20 16:00:02 2018 UTC and is due to finish in 60 minutes. The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:07 The meeting name has been set to 'keystone' 16:00:15 o/ 16:00:17 #link https://etherpad.openstack.org/p/keystone-weekly-meeting 16:00:17 Hello 16:00:19 agenda ^ 16:00:23 o/ 16:00:25 o/ 16:00:26 o/ 16:01:23 o/ 16:01:27 o/ 16:01:28 pretty light agenda - so we can give folks a few minutes 16:03:05 o/ 16:03:07 #topic office hours thoughts 16:03:09 hrybacki: o/ 16:03:17 o/ 16:03:30 So, I went ahead and updated the office hours etherpad 16:03:32 #link https://etherpad.openstack.org/p/keystone-office-hours 16:03:52 based on our conversations at PTG 16:04:14 If folks could glance at that I would appreciate it -- any feedback is awesome. 16:05:00 Additionally, the list at the bottom is a holdover -- there were many names I recognized but did not want to assume are still active. So, if you have a strong feeling that person X is out for good, go ahead and delete it 16:05:09 Also add yourself and your irc handles if you'd like to be pinged :) 16:05:17 I like the "no account required" bit about Bluejeans, so I disagree with " 16:05:20 Do we want to port this to a Google Doc?" 16:05:32 jgr: good point! 16:06:21 While I may have a Google account for situations where somebody forces me to use it, I certainly wouldn't admit to having it :-) 16:06:31 ++ let's not use closed services when we have open ones like etherpad available 16:06:35 The other big question is -- when do we want to decide on a focus for a give Office Hours? Right before (during this meeting) or at the end of the Office Hours (giving folks a week to prepare if needed) 16:06:56 cmurphy++ 16:07:39 for the sake of freshness - i wouldn't be opposed to using the tail end of the meeting to set priorities for office hours (pending time constraints) 16:08:27 lbragstad++ 16:08:42 sounds fine to me 16:08:54 +1 I spent 20 minutes giving myself pros and cons for each side. In the end I figured that having an idea at the end of office hours (to allow for preparation) is a good idea IF we allow us to change that as needed during the weekly meeting (if something better arise). 16:08:57 Too complicated? 16:09:17 that works for me 16:09:32 that might work well for large pieces of work that span multiple sessions, too 16:09:35 * lbragstad shrug 16:09:40 true 16:09:56 Okay, let's just pick a focus at the end of the weekly meeting for now. Can adjust later if that turns out to be sub-optimal 16:10:06 ++ 16:10:33 bluejeans is the best option imo 16:10:47 as unreliable as it is, it's the most reliable option I've found to date 16:10:48 if we need video 16:10:54 and it is most cross-platform 16:10:58 ++ 16:11:06 I think having an open video session is nice. 16:11:12 AND it supports recording if someone with a real account hosts (e.g. hrybacki or myself) 16:11:13 Folks know where it is and can lurk if they want 16:11:34 kmalloc: ack. lbragstad has my moderator code for recording/starting sessions in my absence 16:11:44 but it's good to note that you have one as well 16:12:03 that's all I had lbragstad -- pending any questions from the team 16:12:57 do we want to come up with a plan for today's office hours now? 16:13:06 before having open discussion? 16:13:19 Sure 16:13:31 #topic office hours planning 16:13:31 What needs the most attention right now lbragstad ? 16:13:40 we have several patches in flight that close bugs 16:14:06 we also have a bunch of specs to review 16:14:36 #link https://goo.gl/obdy7E 16:14:41 Ack, so focused review session? 16:15:03 #link https://goo.gl/vJyKpC 16:16:51 o/ 16:17:21 this is the review dashboard that i use if anyone wants to copy/modify it http://paste.openstack.org/show/706266/ 16:18:43 oh nice 16:18:55 https://bugs.launchpad.net/keystone/+bug/1756140 and https://bugs.launchpad.net/keystone/+bug/1756190 have fixes ready to go 16:18:58 Launchpad bug 1756140 in OpenStack Identity (keystone) "Project Tags Documentation Wrong - Create Tag" [Low,In progress] - Assigned to Gage Hugo (gagehugo) 16:18:59 Launchpad bug 1756190 in OpenStack Identity (keystone) "Project tags is too restrictive" [Medium,In progress] - Assigned to Nicolas Helgeson (nhelgeson) 16:19:53 you can pass a dashboard ini file to https://github.com/openstack/gerrit-dash-creator and it will generate a link for you 16:20:03 hrh 16:20:04 heh* 16:20:35 then you can save it into your gerrit settings (which appears under your My tab 16:22:46 i also said i was going to review adriant's spec yesterday 16:22:56 yeah, it is much improved 16:23:01 there is some work still to be done 16:23:07 and clarifications but he's made a nice change 16:23:11 so i'll do that after i review the fixes from nick and gagehugo 16:23:48 and i'll look at jgr's spec, it's been a week since i've looked at that 16:24:13 Thanks :-) 16:24:17 lbragstad, kmalloc: I'm about if anyone does have questions/discussion about the that spec 16:24:29 just a reminder - specification freeze is in a month 16:25:15 adriant: i know there are a few more comments i have. but i had to wait for the recent patch to add them 16:25:22 it's looking pretty close imo 16:25:41 and a few things are just "this isn't needed" type details, so minor fixes 16:26:48 kmalloc: comment on the spec when you get the chance and I'll fix as needed :) 16:27:13 adriant: i'm commenting now, hold on updates until lbragstad and/or cmurphy comments too 16:27:17 I tried to expand as much as possible on the last patch 16:27:22 * adriant nods 16:27:36 this was a great update. big move forward 16:27:38 is there anything else folks want to tackle for office hours? 16:28:49 lbragstad: want to take a crack at updating the RoR spec with me? 16:28:55 yes 16:29:14 hrybacki: johnsom had some comments on it 16:29:23 awesome 16:29:28 * cmurphy will look at all the specs again 16:29:44 they highlighted that we still don't do a real good job communicating what "scope" means 16:29:44 cmurphy is about to become one with the Matrix 16:29:54 especially from a service developer perspective 16:29:56 o/ 16:30:15 johnsom: o/ 16:30:21 Sorry for the newbie perspective. I'm just trying to map what we currently allow to the new naming scheme. 16:30:51 it's been brought up a few times, which means we probably need to update and clarify thigns 16:30:54 things* 16:31:06 i attempted to capture some of the problem areas in https://bugs.launchpad.net/keystone/+bug/1757151 16:31:07 Launchpad bug 1757151 in OpenStack Identity (keystone) "Token and scope documentation needs an update" [Medium,In progress] - Assigned to Lance Bragstad (lbragstad) 16:31:48 hrybacki: if we fix up the documentation to better describe that stuff to other developers, we can likely include it in the RoR specification 16:32:31 lbragstad: ack. Let's do a review of the spec, make list of homework points, and research those before making more patchsets 16:33:10 works for me, i can address problem areas this week and we should be able to work the openstack spec and the doc improvements in parallel 16:33:18 +1 16:34:04 Feel free to ping me if I can help review, etc. 16:34:31 ++ will do, i think a fresh perspective will help 16:34:52 anything else we wanna tackle for office hours, or do we think this is a pretty full plate? 16:37:21 It sounds like we have a bunch of bug related reviews, some specs, and then the default roles spec/strategy/docs stuff 16:38:05 sounds about right 16:38:44 #topic open discussion 16:39:05 anything else folks want to talk about before we adjourn 16:39:25 lbragstad: would you midn opening the video call? I need to find food still 16:39:55 yeah - i can do that 16:40:28 thanks lbragstad 16:40:32 no problem 16:40:43 lbragstad: I saw the oslo.limit spec has been merged. What's the next step? 16:41:07 wxy|_: yep - i think the next official step is getting https://review.openstack.org/#/c/550496/ merged 16:41:26 because https://github.com/openstack/oslo.limit technically exists 16:41:40 then we'll need to finalize the groups and ACLs for it 16:41:53 (which I think I've already done, but just need to double check stuff) 16:42:26 then we should be good to start defining the minimum things we need and working on the interface 16:43:29 Got it. Good to know that. 16:43:45 yeah - it's moving along, we should be able to start committing to it soon 16:44:11 once that governance patch merges, we should reach out to cinder, nova, and cyborg 16:44:17 i remember those projects being interested in this 16:47:52 anything else? 16:47:52 BTW, the limit APIs refactor related things: https://review.openstack.org/#/c/549766/ and https://bugs.launchpad.net/keystone/+bug/1754184 16:47:53 ah - that's another spec i need to review 16:47:53 wxy|_: do we expose an API endpoint for enforcement model discovery? 16:47:54 Launchpad bug 1754184 in OpenStack Identity (keystone) "Unified limits API shouldn't return a list of all limits" [Medium,In progress] - Assigned to wangxiyuan (wangxiyuan) 16:48:26 No, It's still under discussion I think. 16:48:39 ok 16:49:24 adriant: commented on your spec. 16:50:01 kmalloc: will take a gander, just replying to another spec in the meantime 16:51:25 alright - sounds like we can wrap up 16:51:41 i'll get things rolling in about 10 minutes for office hours 16:51:49 thanks for coming 16:51:52 #endmeeting