16:00:04 #startmeeting policy 16:00:08 Meeting started Wed Jun 21 16:00:04 2017 UTC and is due to finish in 60 minutes. The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:12 The meeting name has been set to 'policy' 16:00:12 ping raildo, ktychkova, rderose, htruta, hrybacki, atrmr, gagehugo, lamt, thinrichs, edmondsw, ruan, ayoung, morgan, raj_singh, johnthetubaguy, knikolla, nhelgeson 16:00:18 o/ 16:00:20 o/ 16:00:21 o/ 16:00:22 o/ 16:00:37 #link https://etherpad.openstack.org/p/keystone-policy-meeting 16:00:39 agenda ^ 16:00:57 Just 10 more minutes... I promise I'll wake up then :P 16:01:12 morgan: sounds like a reason to hit snooze 16:01:15 Or.. erm.. I guess I'm here :P 16:01:20 lol 16:01:21 Right!? 16:01:33 i say that to my phone every morning 16:02:17 o/ 16:02:32 alrighty - let's go ahead and get started 16:02:45 pretty light agenda today - so we should have plenty of time to discuss open topics 16:02:52 #topic policy-docs goal 16:03:01 #link https://review.openstack.org/#/c/469954/ 16:03:10 queens goals are getting firmed up 16:03:23 how many rolecall votes do we need to land this 16:03:24 those those unfamiliar with that proposal - it would be great to get your feedback on it 16:03:48 hrybacki: i believe it needs the majority or unanimous vote from the TC 16:04:01 how many members are on the TC? 16:04:04 and the members of the TC are the only ones with Rollcall power, I believe 16:04:13 * hrybacki googles 16:04:56 okay, 3 more votes and we are gold 16:05:07 hrybacki: https://review.openstack.org/#/admin/groups/205,members 16:05:36 #link https://review.openstack.org/#/admin/groups/205,members 16:05:39 lbragstad++ 16:05:40 which leads to our next topic 16:05:51 #topic policy-docs patches 16:05:57 #link https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:bp/policy-docs 16:06:02 we only have a few patches left 16:06:11 i approved a couple yesterday 16:06:22 I'm close with https://review.openstack.org/#/c/449278/ -- trying to resolve one more failing test that's being a pain 16:06:33 hrybacki: sounds good 16:06:55 #link https://review.openstack.org/#/c/449244/ looks ready to go 16:07:22 #link https://review.openstack.org/#/c/449337/ is also ready to go but I proposed it so i'll abstain from merging it 16:07:56 #link https://review.openstack.org/#/c/449255/ is in the same boat 16:08:43 I'll take a look at the later two after this mtg 16:09:04 awesome 16:09:14 moving on 16:09:18 #topic global roles work 16:09:30 #link https://review.openstack.org/#/c/464763/ is proposed to backlog 16:09:42 we have several other specs proposed to backlog as well 16:10:17 even though we are in specification freeze, I'd be ok merging some of those to backlog (pending reviews) since it won't affect our work for Pike 16:10:45 I'm also planning on setting aside time next week to start writing that implementation 16:10:56 and get something in review well before the PTG 16:11:30 #topic open discussion 16:11:35 out-of-band: how does backlog work for upstream projects? 16:12:11 hrybacki: good question - if we generally agree on something we should do as a project, or a spec, but don't have bandwidth to implement in the current cycle, we merge it to backlog 16:12:27 when we're ready to commit resources to it, its moved from the backlog directory to the release we want to target 16:12:40 ah I see the directory now 16:13:05 during the move from backlog, we take the opportunity to update any stale information in the spec (like the people picking up the implementation) 16:13:26 * hrybacki nods 16:13:48 So are you envisioning moving this out of backlog before Pike GA? 16:13:53 so - in this case, we'd try to merge global roles to backlog, and then as soon as spec freeze is lifted we'd repropose it to queens 16:14:04 * hrybacki nods 16:14:08 I understand now, thanks lbragstad 16:14:16 hrybacki: anything 16:14:24 anytime* rather 16:14:51 do folks have anything else policy wise? 16:15:42 lbragstad: you feel good about the state of policy and docs in code? 16:15:53 in that we'll likely have votes we need in time 16:16:07 hrybacki: i think it's a good path forward and it seems to have positive support 16:16:23 our next step will be working with the oslo.policy team quite a bit 16:17:00 we'll need to develop some functionality in that library in order for some of the policy-in-code and policy-docs work to be super useful 16:17:21 * hrybacki nods 16:17:38 but that will be work in queens for sure 16:18:43 edmondsw: have you heard any follow up on the scoping for global tokens? 16:19:02 edmondsw: i believe that discussion was hanging on security vs. usability related concerns 16:19:23 lbragstad no, I've totally lost track of that 16:19:35 edmondsw: ok 16:19:46 haven't had a chance to look at anything policy related in a while 16:19:55 edmondsw: i haven't heard much either - last thing i did was drop a line in #openstack-security asking for advice 16:20:14 maybe i should go poke again 16:20:26 do you remember what the concerns were? or where someone wrote them down? 16:20:38 edmondsw: yeah 16:21:04 edmondsw: the useability concern was that global roles would be adding yet another scoping mechanism that users have to know about in order to do something 16:21:21 (e.g. i want to live migrate, so i need a globally scoped token from keystone) 16:21:39 the argument was that it makes things harder for clients 16:21:44 and users to understand 16:22:02 I just pulled up the global roles spec, and my first comment is going to be that I don't know that live migrate is a great example 16:22:20 i believe gyee wrote that concern down in the spec 16:22:34 edmondsw: if you can think of a better example, I'll incorporate it into the current revision for sure 16:23:05 lbragstad the prime example in my mind is something like nova's GET /v2.1/servers?all_tenants 16:23:36 you shouldn't be able to see things in all tenants unless you have a global role assignment 16:23:39 that works today if a user has the admin role, right? 16:23:44 right 16:23:52 aha - ok 16:23:54 agreed 16:24:00 well... 16:24:12 you need the global role assignment and it needs to match the role required for that policy in nova 16:24:21 (if i'm thinking about this right) 16:24:35 right 16:24:46 ok - cool 16:24:50 we're on the same page then 16:25:00 so you could just have an observer role, not necessarily admin, as long as it was globally scoped 16:25:03 edmondsw: if you leave a comment, i can update the spec with that example instead 16:25:08 will do 16:25:14 edmondsw: right - yep 16:26:15 sounds like i have a few action itmes 16:26:32 #action lbragstad to update the global roles spec with better examples of global operations 16:26:56 #action lbragstad to follow up with the security team on the usability vs. security concerns of using unscoped tokens for global roles 16:27:51 cool - does anyone have anything else? 16:28:47 looks like we'll get some time back - thanks all! 16:28:49 #endmeeting