Wednesday, 2017-08-16

*** brault has quit IRC00:00
*** edmondsw has quit IRC00:00
*** gouthamr has joined #openstack-meeting-cp00:13
*** markvoelker has quit IRC00:30
*** fredli__ has joined #openstack-meeting-cp01:07
*** gouthamr has quit IRC01:13
*** aselius has quit IRC01:22
*** gouthamr has joined #openstack-meeting-cp01:30
*** yamahata has quit IRC01:35
*** lbragstad has quit IRC01:44
*** edmondsw has joined #openstack-meeting-cp01:44
*** edmondsw has quit IRC01:48
*** markvoelker has joined #openstack-meeting-cp02:31
*** gouthamr has quit IRC02:34
*** yamahata has joined #openstack-meeting-cp02:34
*** diablo_rojo has joined #openstack-meeting-cp02:35
*** markvoelker has quit IRC03:04
*** dklyle has quit IRC03:12
*** david-lyle has joined #openstack-meeting-cp03:31
*** edmondsw has joined #openstack-meeting-cp03:32
*** nhelgeson has quit IRC03:36
*** edmondsw has quit IRC03:37
*** fredli__ has quit IRC03:45
*** markvoelker has joined #openstack-meeting-cp04:01
*** david-lyle has quit IRC04:06
*** david-lyle has joined #openstack-meeting-cp04:08
*** dklyle has joined #openstack-meeting-cp04:15
*** brault has joined #openstack-meeting-cp04:16
*** david-lyle has quit IRC04:18
*** brault has quit IRC04:21
*** markvoelker has quit IRC04:34
*** MarkBaker has quit IRC04:41
*** brault has joined #openstack-meeting-cp04:46
*** brault has quit IRC04:50
*** edmondsw has joined #openstack-meeting-cp05:20
*** knikolla has quit IRC05:22
*** edmondsw has quit IRC05:24
*** markvoelker has joined #openstack-meeting-cp05:32
*** brault has joined #openstack-meeting-cp05:44
*** brault has quit IRC05:48
*** markvoelker has quit IRC06:05
*** brault has joined #openstack-meeting-cp06:05
*** brault has quit IRC06:10
*** hemna__ has quit IRC06:43
*** coolsvap has joined #openstack-meeting-cp06:54
*** markvoelker has joined #openstack-meeting-cp07:02
*** edmondsw has joined #openstack-meeting-cp07:08
*** diablo_rojo has quit IRC07:12
*** edmondsw has quit IRC07:13
*** brault has joined #openstack-meeting-cp07:25
*** markvoelker has quit IRC07:36
*** brault has quit IRC07:40
*** brault has joined #openstack-meeting-cp07:49
*** markvoelker has joined #openstack-meeting-cp08:33
*** edmondsw has joined #openstack-meeting-cp08:57
*** edmondsw has quit IRC09:01
*** markvoelker has quit IRC09:06
*** markvoelker has joined #openstack-meeting-cp10:03
*** yamahata has quit IRC10:21
*** MarkBaker has joined #openstack-meeting-cp10:28
*** MarkBaker has quit IRC10:33
*** markvoelker has quit IRC10:38
*** edmondsw has joined #openstack-meeting-cp10:45
*** edmondsw has quit IRC10:49
*** MarkBaker has joined #openstack-meeting-cp10:49
*** brault has quit IRC11:31
*** markvoelker has joined #openstack-meeting-cp11:35
*** MarkBaker has quit IRC11:55
*** brault has joined #openstack-meeting-cp11:56
*** edmondsw has joined #openstack-meeting-cp11:57
*** markvoelker has quit IRC12:08
*** markvoelker has joined #openstack-meeting-cp12:59
*** brault has quit IRC13:09
*** brault has joined #openstack-meeting-cp13:09
*** gouthamr has joined #openstack-meeting-cp13:15
*** knikolla has joined #openstack-meeting-cp13:23
*** felipemonteiro has joined #openstack-meeting-cp13:35
*** felipemonteiro_ has joined #openstack-meeting-cp13:36
*** MarkBaker has joined #openstack-meeting-cp13:37
*** felipemonteiro has quit IRC13:40
*** zhipeng has joined #openstack-meeting-cp13:57
*** felipemonteiro_ has quit IRC14:10
*** zhipeng has quit IRC14:11
*** zhipeng has joined #openstack-meeting-cp14:12
*** lbragstad has joined #openstack-meeting-cp14:13
*** felipemonteiro has joined #openstack-meeting-cp14:41
*** felipemonteiro_ has joined #openstack-meeting-cp14:42
*** felipemonteiro has quit IRC14:46
*** zhipeng has quit IRC14:54
*** zhipeng has joined #openstack-meeting-cp14:54
*** xyang1 has joined #openstack-meeting-cp14:54
*** aselius has joined #openstack-meeting-cp15:00
*** zhipeng has quit IRC15:05
*** zhipeng has joined #openstack-meeting-cp15:05
*** hemna__ has joined #openstack-meeting-cp15:15
*** coolsvap has quit IRC15:27
*** brault has quit IRC15:41
*** brault has joined #openstack-meeting-cp15:45
*** yamahata has joined #openstack-meeting-cp15:47
*** zhipeng has quit IRC15:48
*** zhipeng has joined #openstack-meeting-cp15:49
*** gagehugo has joined #openstack-meeting-cp15:50
*** blancos has joined #openstack-meeting-cp15:59
lbragstadstartmeeting policy16:00
lbragstad#startmeeting policy16:00
openstackMeeting started Wed Aug 16 16:00:47 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: policy)"16:00
openstackThe meeting name has been set to 'policy'16:00
lbragstadping raildo, ktychkova, rderose, htruta, hrybacki, atrmr, gagehugo, lamt, thinrichs, edmondsw, ruan_he, ayoung, morgan, raj_singh, johnthetubaguy, knikolla, nhelgeson16:00
gagehugoo/16:01
lbragstado/16:01
lbragstad#link https://etherpad.openstack.org/p/keystone-policy-meeting16:01
felipemonteiro_o/16:01
blancoso/16:01
edmondswo/16:01
felipemonteiro_lbragstad: i know i didn't get back to you on mailing list but thanks for the feedback, it helped16:01
lbragstadfelipemonteiro_: sure thing!16:02
lbragstadwe don't have much on the agenda today - so we can go ahead and get started16:03
lbragstad#topic global roles16:03
*** openstack changes topic to "global roles (Meeting topic: policy)"16:03
lbragstadknikolla: and i met on monday to go through the existing PoC that's up16:03
lbragstadand we came up with a road map of what needs to happen to get it into PoC shape for the PTG16:04
lbragstadwe documented it here16:04
lbragstad#link https://etherpad.openstack.org/p/keystone-global-roles-poc16:04
cmurphyo/16:04
lbragstadI'll be working on step 1 this week and my goal is to have the refactor passing tests by EOW16:04
*** Guest20591 is now known as cFouts16:04
lbragstadknikolla: plans to jump in and help out once RC2 is out the door - which will be EOW as well16:05
lbragstadif there is anything you'd like to add to the etherpad that improves the PoC - let me know16:05
lbragstador if the work sounds interesting and you want to help out16:05
lbragstadlet me know - i'm happy to coordinate16:05
edmondswtx lbragstad16:06
lbragstadyep! i'm looking forward to the work16:06
edmondswI'll look over the etherpad today16:06
lbragstadedmondsw: thanks16:06
lbragstad#topic policy at the PTG16:07
*** openstack changes topic to "policy at the PTG (Meeting topic: policy)"16:07
lbragstadi have a dedicated time setup at the PTG to help projects with moving policy into code16:09
lbragstadif you're project needs help here - let me know16:09
lbragstador sign up on the etherpad16:09
lbragstad#link https://etherpad.openstack.org/p/policy-queens-ptg16:10
lbragstadStill waiting on a room assignment - but this will most likely be happening on the cross-project days (monday and tuesday)16:10
lbragstad#topic open discussion16:11
*** openstack changes topic to "open discussion (Meeting topic: policy)"16:11
lbragstadfloor is open16:11
edmondswlbragstad added a couple more questions in the global roles etherpad16:14
lbragstadlooks like we can get some time back - thanks for coming!16:14
lbragstadedmondsw: ack16:14
lbragstadedmondsw: want to discuss them here?16:14
edmondswup to you16:14
lbragstadwe have the time16:14
edmondswsure16:14
edmondsw4.1... you say "new attribute to olso.policy"... but 4 is supposed to be nova changes (3 is oslo.policy), so that seems out of place or misworded16:15
lbragstadyeah - it probably is, trying to think of what made me justify that16:15
lbragstadnow that i think about it16:15
edmondswfeel free to remove my question when you clean it up16:15
lbragstadnova work probably means hacking around the scope check?16:16
lbragstador making it so nova consumes the proper attributes from oslo.policy/oslo.context?16:16
edmondswnova work might be fairly involved, at least for a full implementation... maybe just fix a few things for a demo16:16
lbragstadyeah - that's what i was thinking16:16
lbragstadi wouldn't be surprised if that turned into a rabbit hole16:17
edmondswremember they have their main scope check buried in a non-obvious place in the db code16:17
lbragstadso maybe part of that is figuring out "just how much you have to muck with nova to get the demo to work"16:17
edmondswyeah :)16:17
lbragstadedmondsw: maybe that's not entirely bad16:18
lbragstadi mean - sure16:18
lbragstadvalidation should probably not be done in the database,16:18
lbragstadbut there is nothing preventing us from short-circuiting the check in higher layers16:19
edmondswyeah, we'll have to see... might give you one place to change, if you can figure out how16:19
lbragstadyeah16:19
edmondswwell not one... there are others... that's the main one though16:19
edmondswand what about using observer in the demo? We don't have an observer role defined in any policy yet, so are you going to do a bunch of custom policy to show that?16:20
edmondswseems like you might want to just stick to admin and member for this demo16:20
lbragstadedmondsw: i wasn't planning on doing a bunch of policy changes - i was more or less writing an outline for what would be an effective demo16:21
edmondswotoh, customizing policy to create an observer role shouldn't be too hard16:21
lbragstad(because everyone seems to really gravitate towards the observer role case)16:21
edmondswyep, definitely16:21
lbragstadi figured using that would help people understand how things work since they already have a solid understanding of it because they want it16:21
edmondswdefinitely.. just making sure you realize there is work to be done there that has nothing to do with global scope really16:22
edmondswwould totally be useful if we did that work16:22
lbragstadright - it's something that helps illustrate the global scope thing16:22
lbragstad"if i apply the observer role global, Bob should be able to see all instances across all projects"16:23
lbragstads/global/globally/16:23
edmondswyep16:23
lbragstadedmondsw: good last point16:25
lbragstadyes - it will require a migration16:25
lbragstad(role migration)16:25
lbragstadmaybe show before and after?16:25
lbragstadthis is Bob and Bob has an admin role on a project - which unfortunately gives him god-mode everywhere16:26
lbragstadthen explain that Bob needs the admin role scoped globally to maintain the things he needs to do to admin his cloud16:26
edmondswlbragstad yeah, we'll have to talk about backward compat, which probably means opt-in16:27
lbragstadif a user has admin on a project but shouldn't be doing things globally - then they get fixed automatically16:27
lbragstadyeah16:28
edmondswand interop16:28
lbragstadabout 5.6.216:28
lbragstadthat's going to require rework in each of the services16:28
edmondswyep, totally16:28
lbragstadeach project needs to go through and rework their classification of an operation to fit into multiple scoped16:29
lbragstadscopes*16:29
edmondswnot sure if you want to try to do a little of that to demo it here or leave that for later16:29
lbragstadif someone is trying to create an instance using a globally scoped token, nova should catch it in validation and reject it16:29
edmondswonly if we decide we don't want to allow that16:29
lbragstadi'll defer to the nova folks16:30
lbragstadsince i assume they have more stake in that16:30
edmondswwe could also decide that we do want to allow it, and just make the caller pass the project_id in the POST body16:30
lbragstadsince it would break backwards compatibility16:30
edmondswthe new attribute would just require a new microversion16:30
lbragstadwe typically had a pretty hard stance on not having certain things floating around globally16:31
lbragstad(that also seems to introduce new edge cases in limits and quotas)16:31
edmondswwhat do you mean?16:32
lbragstadwhat if you have instances that are owned globally (not associated to a project)16:32
edmondswI'm not suggesting you be able to create something that's global... rather than you can create something that's scoped to a project using a token that is scoped globally16:32
lbragstadohh16:32
lbragstadnevermind16:32
edmondswjust like you can view something that's scoped to a project using a token that's scoped globally16:32
lbragstadyeah - we can totally bring that up to the projects at the ptg16:33
lbragstadthat might help ease the token scope confusion problem16:33
edmondswlbragstad reworded to clarify16:33
lbragstad(do i need a project scoped token to do X or do i need a globally scoped token?)16:34
edmondswexactly16:34
lbragstadthat also might be answered by a capabilities endpoint after 3.3 is done16:34
edmondswtalking to our UI guys (PowerVC has a custom UI, not horizon), they hate the idea of having to get a different token for each project in order to present a global view16:34
lbragstadyeah16:35
lbragstadi think horizon feels the same way16:35
edmondswI would expect so16:35
lbragstadbut gyee mentioned the pain of having to constantly wonder what the required scope is for an opertion16:35
lbragstadoperation*16:35
lbragstad3.3 might fix that for us with a consistently exposed endpoint16:36
edmondswwhat's happening with 3.3?16:36
edmondswwhat's 3.3?16:36
lbragstadi think i figured out why i put that under nova owrk16:36
lbragstadlet me grab an example16:36
*** yamahata has quit IRC16:36
lbragstad#link https://github.com/openstack/keystone/blob/master/keystone/common/policies/endpoint.py#L18-L2316:37
lbragstadwhat if we added something ^ there to do this:16:38
lbragstadhttp://paste.openstack.org/show/618561/16:38
lbragstadwhich would render the scope for a given api with the documentation or sample policy files16:38
lbragstadbut it would also make the scope available to advertise through a capabilities api16:39
lbragstadlibraries and clients would be able to programmatically determine what scope is required for an operation by inspecting the document provided by a capabilities API16:40
edmondswI was rather thinking we avoid the issue by not limiting APIs to a specific scope16:40
edmondswe.g. the create thing... let folks create using a token with either project or global scope16:41
*** zhipeng has quit IRC16:41
*** zhipeng has joined #openstack-meeting-cp16:41
edmondswthe thing they're creating might still be project-scoped... maybe what you're suggesting comes in there?16:41
lbragstadwell - today the project is pulled from the token in those cases16:42
edmondswright... and I would assert we need to fix that16:42
lbragstadah16:42
edmondswmaking people get tokens scoped a certain way to do certain things is onerous and unnecessary16:43
edmondsw(or rather, should be unnecessary)16:43
lbragstadthis would add another condition to scope checking16:43
lbragstadbut i understand the usability arguments16:43
edmondswyou should be able to do or not do things based on your role and whether the scope of what you're trying to do is equal to or within the scope of your token, period16:43
edmondswthen you don't need to be making statements about scope for every individual API16:44
edmondswand the UI teams will cheer! :)16:44
lbragstadthe only thing about that statement that doesn't apply today is the "within" bit16:44
edmondswright... because we don't have global roles yet16:45
edmondswso it didn't apply16:45
edmondswbut now it will16:45
lbragstadok - counter argument16:45
lbragstadonce all this stuff is working and inplace16:46
lbragstaddoes this make compromised admin-tokens too dangerous?16:46
edmondswmore than they already are? no16:46
edmondswthe opposite, actually16:46
lbragstadhence the already working part16:46
lbragstad(one of the arguments i've heard for scoping is that it limits the damage of a compromised token to a single project)16:47
edmondswtoday, a compromised admin token won't let you create except in one project, sure, but it will let you view/update/delete in all, and those things are worse16:47
lbragstadbut a compromised admin token are all of what we discussed is in place, would allow someone to create instances anywhere16:48
edmondswtomorrow, with global roles and ability to create with such, yes, a compromised global admin token will be slightly more powerful (can create) but that's only negligibly worse because view/update/delete are the things you really worry about first and foremost16:48
edmondswand you'll have far fewer such tokens than project-scoped admin tokens, so the chances of compromise are reduced16:49
edmondswif someone can delete things but can't create, I don't feel any better than if they could both delete and create16:49
edmondswI'll say "they can delete! nooooo!!!"16:50
edmondswand forget about create16:50
edmondsw:)16:50
edmondswlbragstad right?16:50
lbragstadyeah - that makes sense16:50
lbragstadi need to ponder this a bit more16:51
edmondswsure16:51
lbragstadi like how it eases usability of scoping though16:51
*** zhipeng has quit IRC16:52
lbragstadedmondsw: anything else on the etherpad you want to cover?16:53
edmondswI think that's it for now... thanks for this!16:54
lbragstadyeah - i hope it helps get things in order to the PTG16:54
lbragstadi'd say if we get through 5 - we're doing well16:54
edmondswvery16:54
lbragstadcool - anything else for open discussion?16:55
edmondswand, with a short agenda, we took the full hour :)16:55
lbragstadi know it16:55
lbragstadkinda nice16:55
lbragstadedmondsw: do we want to save bringing this up to the nova folks until the ptg?16:55
lbragstadthe project_id thing?16:55
edmondswfor create APIs?16:55
lbragstadi was debating a thread to kickstart policy discussions16:55
edmondswyeah, without johnthetubaguy there I don't know how interested the rest are in all this16:56
lbragstadhoping it will help us be more productive while we're in denver16:56
lbragstadjohnthetubaguy: is supposedly going to be in Denver16:56
edmondswit shouldn't hurt to throw something on the ML and see if we get any response16:56
edmondswawesome16:57
lbragstadok - i'll mention it when i start spamming folks about policy early next week16:57
lbragstadalright - just about out of time16:58
lbragstadthanks for the discussion!16:58
lbragstad#endmeeting16:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Wed Aug 16 16:58:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/policy/2017/policy.2017-08-16-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/policy/2017/policy.2017-08-16-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/policy/2017/policy.2017-08-16-16.00.log.html16:58
*** blancos has quit IRC17:01
*** diablo_rojo has joined #openstack-meeting-cp17:06
*** gagehugo has left #openstack-meeting-cp17:09
*** yamahata has joined #openstack-meeting-cp17:16
*** MarkBaker has quit IRC17:29
*** nhelgeson has joined #openstack-meeting-cp18:01
*** gouthamr has quit IRC20:46
*** felipemonteiro_ has quit IRC20:48
*** brault has quit IRC20:49
*** diablo_rojo has quit IRC20:55
*** diablo_rojo has joined #openstack-meeting-cp20:57
*** edmondsw has quit IRC21:32
*** felipemonteiro has joined #openstack-meeting-cp21:36
*** felipemonteiro_ has joined #openstack-meeting-cp21:54
*** felipemonteiro has quit IRC21:57
*** iyamahat has joined #openstack-meeting-cp22:07
*** xyang1 has quit IRC22:11
*** felipemonteiro_ has quit IRC22:34
*** edmondsw has joined #openstack-meeting-cp22:49
*** brault has joined #openstack-meeting-cp22:49
*** brault has quit IRC22:54
*** edmondsw has quit IRC22:54
*** notmyname has quit IRC23:19
*** notmyname has joined #openstack-meeting-cp23:23
*** gouthamr has joined #openstack-meeting-cp23:27

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!