Wednesday, 2018-01-10

*** felipemonteiro has quit IRC00:40
*** markvoelker has joined #openstack-meeting-cp00:43
*** markvoelker has quit IRC00:45
*** markvoelker has joined #openstack-meeting-cp00:49
*** markvoelker has quit IRC00:50
*** david-lyle has joined #openstack-meeting-cp00:58
*** markvoelker has joined #openstack-meeting-cp01:08
*** markvoelker has quit IRC01:09
*** felipemonteiro has joined #openstack-meeting-cp01:25
*** felipemonteiro_ has joined #openstack-meeting-cp01:47
*** felipemonteiro__ has joined #openstack-meeting-cp01:51
*** felipemonteiro_ has quit IRC01:51
*** felipemonteiro has quit IRC01:51
*** felipemonteiro__ has quit IRC01:55
*** iyamahat has joined #openstack-meeting-cp01:57
*** iyamahat has quit IRC02:00
*** sdague has quit IRC02:01
*** felipemonteiro__ has joined #openstack-meeting-cp02:07
*** david-lyle has quit IRC02:07
*** iyamahat has joined #openstack-meeting-cp02:07
*** iyamahat has quit IRC02:09
*** felipemonteiro__ has quit IRC02:18
*** harlowja has quit IRC02:24
*** nhelgeson has quit IRC02:34
*** iyamahat has joined #openstack-meeting-cp02:34
*** lbragstad has quit IRC02:54
*** david-lyle has joined #openstack-meeting-cp04:46
*** david-lyle has quit IRC04:53
*** coolsvap has joined #openstack-meeting-cp04:59
*** harlowja has joined #openstack-meeting-cp05:24
*** markvoelker has joined #openstack-meeting-cp05:39
*** edmondsw has joined #openstack-meeting-cp06:00
*** edmondsw has quit IRC06:04
*** harlowja has quit IRC07:49
*** iyamahat has quit IRC08:44
*** markvoelker has quit IRC09:08
*** coolsvap has quit IRC10:29
*** markvoelker has joined #openstack-meeting-cp11:08
*** yamahata has quit IRC11:22
*** markvoelker has quit IRC11:42
*** sdague has joined #openstack-meeting-cp11:58
*** sdague has quit IRC12:31
*** markvoelker has joined #openstack-meeting-cp12:39
*** edmondsw has joined #openstack-meeting-cp13:01
*** markvoelker has quit IRC13:12
*** ttx has quit IRC13:21
*** ttx has joined #openstack-meeting-cp13:23
*** sdague has joined #openstack-meeting-cp14:00
*** stvnoyes has joined #openstack-meeting-cp14:05
*** markvoelker has joined #openstack-meeting-cp14:10
*** zhipeng has joined #openstack-meeting-cp14:15
*** lbragstad has joined #openstack-meeting-cp14:38
*** coolsvap has joined #openstack-meeting-cp14:40
*** markvoelker has quit IRC14:43
*** iyamahat has joined #openstack-meeting-cp14:46
*** markvoelker has joined #openstack-meeting-cp14:51
*** iyamahat has quit IRC14:56
*** iyamahat has joined #openstack-meeting-cp14:56
*** felipemonteiro__ has joined #openstack-meeting-cp14:57
*** felipemonteiro_ has joined #openstack-meeting-cp14:59
*** felipemonteiro__ has quit IRC15:03
*** markvoelker has quit IRC15:03
*** iyamahat has quit IRC15:03
*** iyamahat has joined #openstack-meeting-cp15:09
*** iyamahat has quit IRC15:24
*** iyamahat has joined #openstack-meeting-cp15:26
*** iyamahat has quit IRC15:33
*** felipemonteiro_ has quit IRC15:33
*** felipemonteiro_ has joined #openstack-meeting-cp15:34
*** markvoelker has joined #openstack-meeting-cp15:37
*** david-lyle has joined #openstack-meeting-cp15:43
*** yamahata has joined #openstack-meeting-cp15:47
*** felipemonteiro__ has joined #openstack-meeting-cp15:57
lbragstad#startmeeting policy16:00
openstackMeeting started Wed Jan 10 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
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, kmalloc, raj_singh, johnthetubaguy, knikolla, nhelgeson16:00
lbragstad#link https://etherpad.openstack.org/p/keystone-policy-meeting16:00
cmurphyo/16:00
edmondswo/16:00
lbragstado/16:00
lbragstadso - we don't have anything on the agenda16:00
lbragstad#topic open discussion16:00
*** openstack changes topic to "open discussion (Meeting topic: policy)"16:00
lbragstadbut we can open it up in case anyone has topics16:00
*** felipemonteiro_ has quit IRC16:01
edmondswdon't everyone talk at once... ;)16:03
lbragstad:)16:03
lbragstadjust fyi - in case anyone finds this interesting16:03
lbragstadi'm refactoring all the system scope patches16:03
lbragstadspecifically the bits for role assignments16:03
*** dklyle has joined #openstack-meeting-cp16:04
*** david-lyle has quit IRC16:04
lbragstadso that we don't use ?scope.system as a boolean16:04
lbragstadi should have those ready for review by eod16:05
lbragstadi'm hoping16:05
lbragstadbut that's all i have16:05
cmurphylbragstad: you brought up some questions at yesterday's meeting but i don't think edmondsw was there, do you want to bring it up again now?16:06
lbragstadsure - we can go through those16:06
*** zhipeng has quit IRC16:07
edmondswwhat'd I miss?16:07
lbragstadedmondsw: you know how the policy objects have an attribute for scope_types now?16:07
edmondswyeah16:07
lbragstadi took a stab at trying to define those for all resources keystone owns16:08
lbragstad#link https://review.openstack.org/#/q/topic:add-scope-types+(status:open+OR+status:merged)16:08
lbragstadin doing so, it became apparent that different behaviors will be expected depending on the scope_types used in the request16:09
edmondswyes16:09
lbragstadi attempted to highlight each of these cases with a FIXME https://review.openstack.org/#/c/526159/3/keystone/common/policies/project.py16:09
lbragstad#link https://review.openstack.org/#/c/526159/3/keystone/common/policies/project.py16:09
lbragstadyesterday, i brought it up during the keystone meeting to figure out how we should go about handling those16:09
lbragstad(does each one get a bug report, do all FIXMEs for a single resource get tracked for a bug, how do we want to organize the scope check code in keystone, etc..)16:10
edmondswthis was one of the things I brought up in Austin, I believe...16:10
edmondsw:)16:10
lbragstadthe TL;DR at the end of the meeting was that we should filter some of the context information and policy information down to the managers (since this is essentially business logic)16:11
edmondswyou might want a blueprint to tackle those across keystone, or just start picking away at them under an existing blueprint, rather than try to file 100 bugs16:11
lbragstadyeah - yesterday we said pretty much the same thing, but instead of a blueprint, use a single bug "Fix all scope types for projects"16:12
lbragstadand that patch would address all FIXMEs in #link https://review.openstack.org/#/c/526159/3/keystone/common/policies/project.py16:12
edmondswI guess even with a single bug could use multiple patches to fix it16:13
lbragstadsure16:13
edmondswyep, will be very happy to see that fixed16:13
lbragstadbut it wouldn't require a bug for a the FIXME on line 20 and another bug for the FIXME on line 32, etc...16:13
edmondswyeah, that would get onerous16:14
lbragstadright..16:14
lbragstadso - that's what we talked about yesterday16:14
edmondswcool, tx for the recap16:14
lbragstadbut i expect each review to generate some discussion16:14
knikollamakes sense16:14
lbragstadat least for the resources that can be operated on with project scope and system scope16:14
lbragstadbut... i'm hoping folks review so we can accurately document the behavior we want for each scope in the fixme16:15
lbragstadwhen the patch merges, i'll open a bug report for the resource and all of it's fixmes16:15
*** gagehugo has joined #openstack-meeting-cp16:15
lbragstadwhich should make it easier to divvy up work16:16
lbragstadbut things like:16:16
lbragstad#linkhttps://review.openstack.org/#/c/525695/16:16
lbragstad#link https://review.openstack.org/#/c/525695/16:16
lbragstadand #link https://review.openstack.org/#/c/525696/16:16
lbragstadshould be pretty easy, since they only deal with system scope16:16
lbragstad(so not every review will generate a bug, which is good)16:17
lbragstadthoughts, comments, questions, or concerns?16:18
*** markvoelker has quit IRC16:19
edmondswwhen I flip on the scope enforcement, will it treat someone with a project-scoped token for the admin project as if that was a system-scoped token?16:20
lbragstadi haven't written any code that makes that mapping16:21
lbragstadbut if someone has a policy that looking for the admin project and allows it for a policy, then it would work16:21
edmondswwithout a warning? e.g. I don't want log warnings if I use an admin-project-scoped token to create an endpoint in the catalog16:22
*** markvoelker has joined #openstack-meeting-cp16:22
edmondswat least I don't think I do... maybe I do?16:23
lbragstadoslo policy issues the warning, but it doesn't understand the admin_project16:23
knikollaprobably when we deprecate admin project?16:23
lbragstadit just attempts to look at the context passed in and determine project scope or system scope16:23
lbragstadand then compares that to the scope_types of the policy being enforced16:24
edmondswI'm sorry I haven't kept up... but one of the things we talked about in Sydney was the need for clients (e.g. Horizon) to be able to do a variety of things with a single token, rather than have to get a differently-scoped token for everything16:26
edmondswis that supported?16:26
*** markvoelker has quit IRC16:27
lbragstadnot - it isn't supported today.. but i do have an item on my list of things to do to write a PoC for a capabilities API16:27
edmondswe.g. see all VMs in all projects with a single request16:27
edmondswhow would a capabilities API help?16:28
lbragstads/not/no/16:28
edmondswI think that solves a different problem16:28
edmondswWHAT can I do vs. ALLOW me to do16:28
lbragstadwell - it depends on how it is implemented16:28
lbragstadyou could have the capabilities API return operations and have scope_types be part of that16:29
* lbragstad is open to suggestions here16:31
edmondswmaybe horizon could get a project-scoped token for a domain that includes all projects if they want to list VMs in all projects with a single request... but nova would have to understand that that project-scope is the top-level domain16:31
lbragstadyes16:32
lbragstadin my mind, that's how it makes sense16:32
edmondswwhich would be tricky16:32
lbragstadin order to do that, we'd need to get the hardcoded 'admin' role checks fixed16:33
edmondswthat too, but I'm worried about how nova would know which project is the top-level project16:33
edmondswand all deployments would need to have a top-level project (domain)16:34
lbragstadthey'd need to make a callback to keystone?16:34
lbragstador get that information in middleware somehow?16:34
lbragstad(a similar pattern is going to exist with the unified limit work)16:34
edmondswwait, what do we set as the parent for a top-level domain today?16:35
edmondswthere's a hidden root domain, right?16:35
lbragstadyes - but i think it is hidden to other services16:35
lbragstadi don't think we actually expose it?16:35
edmondswwe would need nova, etc. (or oslo_policy?) to understand that is the root so if someone has a token scoped to that they can do things across all projects16:35
edmondswI guess we also have the issue of what if someone is scoped to a domain that is not top-level, and wants to list all VMs anywhere in that domain. Or at any other level in the hierarchy... nova/etc. have to understand hierarchy16:36
lbragstadyeah...16:37
edmondswugh16:37
lbragstadthat's the idea16:37
lbragstadwhich is going to be hard to do, but seems like the proper way to implement it16:37
edmondswyeah16:37
edmondswI wonder if anyone will actually use system scoping until all that is addressed16:38
lbragstadthis is what drove a lot of the questions i had yesterday16:38
lbragstadthat's another good question16:38
lbragstadmy guess is that people can use it for things that don't fall in the gray area between system scope and project scope16:39
lbragstad(e.g. using system scope to have cloud administrator manage endpoints/services)16:39
lbragstador granting someone a reader role on the system16:40
lbragstadbut yeah - all of this certainly becomes more useful when we start working the hierarchy (if present) into the service16:41
edmondswyeah16:42
lbragstadat the same time, there is only so much code you can write in a release :)16:42
edmondswno ;)16:42
edmondswyeah, hopefully you've made a good stab at things16:43
edmondswand we can build on it16:43
lbragstadright - and that's my hope16:43
lbragstadi'd like to get a good idea of this built out in keystone16:43
lbragstadand start tackling it in nova16:43
lbragstadthen i'm hoping others will catch on and carry the model into their own projects16:43
edmondswI'd suggest building things out in keystone and nova in parallel, since they are pretty different16:45
edmondswwill help us do things in a way that will work for both16:46
lbragstadyeah16:46
lbragstadi'll need to sit down with a few nova folks16:46
lbragstadbut that would be a good topic for the PTG16:46
edmondswyep16:46
lbragstadcross project topic*16:46
edmondswand we went from having nothing to talk about to taking 45 minutes :)16:47
lbragstad++16:47
lbragstadit sounds like we're all on the same page with the scope-types stuff16:48
*** felipemonteiro__ has quit IRC16:48
*** felipemonteiro__ has joined #openstack-meeting-cp16:48
edmondswI hope so16:48
edmondswI haven't been able to keep up with the reviews16:49
lbragstadwell - any feedback will be appreciated16:51
lbragstadand there are some easy ones up16:51
edmondswthe easy ones probably aren't the ones where my feedback would be valuable :)16:52
lbragstadprojects, role assignments, credentials16:52
edmondswhonestly, I'm probably limited to attending this meeting at the moment16:52
edmondswjust too much on my plate16:52
lbragstadthat's understandable16:52
lbragstadanything else we want to discuss?16:53
edmondswit from me16:54
lbragstadcool - well thanks for the time16:55
lbragstad#endmeeting16:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:55
openstackMeeting ended Wed Jan 10 16:55:42 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/policy/2018/policy.2018-01-10-16.00.html16:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/policy/2018/policy.2018-01-10-16.00.txt16:55
openstackLog:            http://eavesdrop.openstack.org/meetings/policy/2018/policy.2018-01-10-16.00.log.html16:55
*** dklyle has quit IRC17:03
*** yamahata has quit IRC17:05
*** harlowja has joined #openstack-meeting-cp17:16
*** david-lyle has joined #openstack-meeting-cp17:16
*** breton has quit IRC17:31
*** zerick has joined #openstack-meeting-cp17:39
*** iyamahat has joined #openstack-meeting-cp17:40
*** iyamahat_ has joined #openstack-meeting-cp17:40
*** iyamahat has quit IRC17:40
*** zerick has quit IRC17:41
*** zerick has joined #openstack-meeting-cp17:42
*** felipemonteiro_ has joined #openstack-meeting-cp17:43
*** zerick has quit IRC17:45
*** zerick has joined #openstack-meeting-cp17:46
*** felipemonteiro__ has quit IRC17:46
*** iyamahat_ has quit IRC17:58
*** iyamahat has joined #openstack-meeting-cp18:00
*** david-lyle has quit IRC18:07
*** coolsvap has quit IRC18:18
*** felipemonteiro_ has quit IRC18:19
*** felipemonteiro_ has joined #openstack-meeting-cp18:19
*** nhelgeson has joined #openstack-meeting-cp18:23
*** openstack has joined #openstack-meeting-cp18:30
*** ChanServ sets mode: +o openstack18:30
*** harlowja has quit IRC18:37
*** david-lyle has joined #openstack-meeting-cp18:59
*** felipemonteiro__ has joined #openstack-meeting-cp19:03
*** felipemonteiro_ has quit IRC19:06
*** harlowja has joined #openstack-meeting-cp19:13
*** harlowja_ has joined #openstack-meeting-cp19:16
*** harlowja has quit IRC19:19
*** gagehugo has left #openstack-meeting-cp19:23
*** breton has joined #openstack-meeting-cp19:30
*** iyamahat has quit IRC19:38
*** iyamahat has joined #openstack-meeting-cp19:48
*** zerick has quit IRC19:51
*** zerick_ has joined #openstack-meeting-cp19:51
*** iyamahat has quit IRC19:57
*** iyamahat has joined #openstack-meeting-cp20:05
*** iyamahat has quit IRC20:17
*** iyamahat has joined #openstack-meeting-cp20:56
*** iyamahat_ has joined #openstack-meeting-cp20:56
*** iyamahat has quit IRC21:00
*** iyamahat_ has quit IRC21:01
*** felipemonteiro__ has quit IRC21:03
*** felipemonteiro__ has joined #openstack-meeting-cp21:04
*** yamahata has joined #openstack-meeting-cp21:13
*** felipemonteiro_ has joined #openstack-meeting-cp21:20
*** felipemonteiro__ has quit IRC21:23
*** felipemonteiro_ has quit IRC21:32
*** felipemonteiro_ has joined #openstack-meeting-cp21:33
*** yamahata has quit IRC22:03
*** yamahata has joined #openstack-meeting-cp22:04
*** yamahata has quit IRC22:09
*** felipemonteiro__ has joined #openstack-meeting-cp22:29
*** felipemonteiro_ has quit IRC22:33
*** edmondsw has quit IRC22:59
*** felipemonteiro__ has quit IRC23:10
*** haint has quit IRC23:41
*** sdague has quit IRC23:47
*** SergeyLukjanov has quit IRC23:53
*** SergeyLukjanov has joined #openstack-meeting-cp23:54
*** edmondsw has joined #openstack-meeting-cp23:55

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