)]}'
{"specs/keystone/ongoing/policy-goals.rst":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":24,"context_line":"operators, and enabling better delegation workflows by allowing operation-role"},{"line_number":25,"context_line":"review:"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"1. As an operator, I should be able to grant an `admin` role to a user on a"},{"line_number":28,"context_line":"   project without compromising data outside of the project."},{"line_number":29,"context_line":"2. As an operator, I should be able to easily understand which policy maps to a"},{"line_number":30,"context_line":"   particular operation or API."},{"line_number":31,"context_line":"3. As an operation, I should have a variety of sensible roles at my disposal"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_00963b40","line":28,"range":{"start_line":27,"start_character":0,"end_line":28,"end_character":60},"updated":"2017-04-27 09:23:47.000000000","message":"This is important, but we missed why. Its about scaling operations through delegation.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":25,"context_line":"review:"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"1. As an operator, I should be able to grant an `admin` role to a user on a"},{"line_number":28,"context_line":"   project without compromising data outside of the project."},{"line_number":29,"context_line":"2. As an operator, I should be able to easily understand which policy maps to a"},{"line_number":30,"context_line":"   particular operation or API."},{"line_number":31,"context_line":"3. As an operation, I should have a variety of sensible roles at my disposal"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_075ac728","line":28,"in_reply_to":"5ff73747_00963b40","updated":"2017-04-27 13:58:27.000000000","message":"Done","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":26,"context_line":""},{"line_number":27,"context_line":"1. As an operator, I should be able to grant an `admin` role to a user on a"},{"line_number":28,"context_line":"   project without compromising data outside of the project."},{"line_number":29,"context_line":"2. As an operator, I should be able to easily understand which policy maps to a"},{"line_number":30,"context_line":"   particular operation or API."},{"line_number":31,"context_line":"3. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":32,"context_line":"   upon installation that I can assign to users."},{"line_number":33,"context_line":"4. As an operator, I should be able to easily modify and maintain my own"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_208c9734","line":30,"range":{"start_line":29,"start_character":0,"end_line":30,"end_character":31},"updated":"2017-04-27 09:23:47.000000000","message":"So I like this, but I think the first thing on this list should be the reverse of this statement, something like:\n\nWhen an operator gives a user a particular role in a particular project, they must understand what access they are delegating to that user.\n\n(PS this is why I wanted to do the policy docs, although we are not totally there yet).\n\nIt feels like the phrase \"security audit\" should be in here somewhere.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":27,"context_line":"1. As an operator, I should be able to grant an `admin` role to a user on a"},{"line_number":28,"context_line":"   project without compromising data outside of the project."},{"line_number":29,"context_line":"2. As an operator, I should be able to easily understand which policy maps to a"},{"line_number":30,"context_line":"   particular operation or API."},{"line_number":31,"context_line":"3. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":32,"context_line":"   upon installation that I can assign to users."},{"line_number":33,"context_line":"4. As an operator, I should be able to easily modify and maintain my own"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_a7b6733d","line":30,"in_reply_to":"5ff73747_208c9734","updated":"2017-04-27 13:58:27.000000000","message":"So, just to confirm. You think the existing statement is still valuable, but you want to have a more specific version of it listed at the top?","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":29,"context_line":"2. As an operator, I should be able to easily understand which policy maps to a"},{"line_number":30,"context_line":"   particular operation or API."},{"line_number":31,"context_line":"3. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":32,"context_line":"   upon installation that I can assign to users."},{"line_number":33,"context_line":"4. As an operator, I should be able to easily modify and maintain my own"},{"line_number":34,"context_line":"   policies."},{"line_number":35,"context_line":"5. As a user, I should be able to determine what I can do in a given"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_80cfeb54","line":32,"updated":"2017-04-27 09:23:47.000000000","message":"Maybe include examples like per-service roles? or read-only roles?\n\nIts common to have a separate admin/operations team on compute and block storage, for example. Monitoring wants to know whats there, and whats not, etc.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":29,"context_line":"2. As an operator, I should be able to easily understand which policy maps to a"},{"line_number":30,"context_line":"   particular operation or API."},{"line_number":31,"context_line":"3. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":32,"context_line":"   upon installation that I can assign to users."},{"line_number":33,"context_line":"4. As an operator, I should be able to easily modify and maintain my own"},{"line_number":34,"context_line":"   policies."},{"line_number":35,"context_line":"5. As a user, I should be able to determine what I can do in a given"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_87e1372d","line":32,"in_reply_to":"5ff73747_80cfeb54","updated":"2017-04-27 13:58:27.000000000","message":"Done","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":30,"context_line":"   particular operation or API."},{"line_number":31,"context_line":"3. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":32,"context_line":"   upon installation that I can assign to users."},{"line_number":33,"context_line":"4. As an operator, I should be able to easily modify and maintain my own"},{"line_number":34,"context_line":"   policies."},{"line_number":35,"context_line":"5. As a user, I should be able to determine what I can do in a given"},{"line_number":36,"context_line":"   deployment."},{"line_number":37,"context_line":"6. As a user, I should be able to review the roles I have and which policies"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_80f80b7b","line":34,"range":{"start_line":33,"start_character":0,"end_line":34,"end_character":12},"updated":"2017-04-27 09:23:47.000000000","message":"I would say people only do this because (3) isn\u0027t good enough for them, its almost a non-goal. Maybe we start a second lower priority list?","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":31,"context_line":"3. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":32,"context_line":"   upon installation that I can assign to users."},{"line_number":33,"context_line":"4. As an operator, I should be able to easily modify and maintain my own"},{"line_number":34,"context_line":"   policies."},{"line_number":35,"context_line":"5. As a user, I should be able to determine what I can do in a given"},{"line_number":36,"context_line":"   deployment."},{"line_number":37,"context_line":"6. As a user, I should be able to review the roles I have and which policies"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_473e8f8c","line":34,"in_reply_to":"5ff73747_80f80b7b","updated":"2017-04-27 13:58:27.000000000","message":"I think adding this bit was more related to the existing work we are doing to move defaults into code, which eventually makes maintenance of policy easier since there is less stuff to keep track of.\n\nI suppose that\u0027s not all that clear from the use case. The use case could be interpreted as something else that does the management for you.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":33,"context_line":"4. As an operator, I should be able to easily modify and maintain my own"},{"line_number":34,"context_line":"   policies."},{"line_number":35,"context_line":"5. As a user, I should be able to determine what I can do in a given"},{"line_number":36,"context_line":"   deployment."},{"line_number":37,"context_line":"6. As a user, I should be able to review the roles I have and which policies"},{"line_number":38,"context_line":"   they allow me to use."},{"line_number":39,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_00a2bbfd","line":36,"updated":"2017-04-27 09:23:47.000000000","message":"I don\u0027t see this as a policy goal, its wider than that, it involves what is supported by the system (like is cinder backup enabled/configured/supported, etc). Hence the capabilities API discussions.\n\nNow when you find out you can\u0027t do that, its interesting to know why, or at least expose why to an operator or admin so they can get them access to that thing if needed.\n\nI am thinking outside API user doing delegation here, just looking at the basics of running a basic system.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":33,"context_line":"4. As an operator, I should be able to easily modify and maintain my own"},{"line_number":34,"context_line":"   policies."},{"line_number":35,"context_line":"5. As a user, I should be able to determine what I can do in a given"},{"line_number":36,"context_line":"   deployment."},{"line_number":37,"context_line":"6. As a user, I should be able to review the roles I have and which policies"},{"line_number":38,"context_line":"   they allow me to use."},{"line_number":39,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_67306ba0","line":36,"in_reply_to":"5ff73747_00a2bbfd","updated":"2017-04-27 13:58:27.000000000","message":"Absolutely, that makes sense. I\u0027ll add another version below and if we want to remove the original, we can.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":35,"context_line":"5. As a user, I should be able to determine what I can do in a given"},{"line_number":36,"context_line":"   deployment."},{"line_number":37,"context_line":"6. As a user, I should be able to review the roles I have and which policies"},{"line_number":38,"context_line":"   they allow me to use."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"Future Use Cases"},{"line_number":41,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_40b3234e","line":38,"updated":"2017-04-27 09:23:47.000000000","message":"I am not sure why you need if you don\u0027t want to do delegate certain permissions to someone, as described in (1) below. I think we should keep the delegation related concerns together.\n\nIn the non-delegation by API user world, its an operator that wants to be able to inspect the logs to help the user get access to the thing they need. Although generally it should have been a conscious choice why they don\u0027t have access, so it really only just be a debugging during testing new rules that you need this sort of thing.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":46,"context_line":"use cases in the previous section (i.e. you must crawl before you can walk, and"},{"line_number":47,"context_line":"walk before you can run)."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"1. As a user, I should be able to give fine-grained access to another user or"},{"line_number":50,"context_line":"   system."},{"line_number":51,"context_line":"2. As an operator, I should be able to build custom policies that can take into"},{"line_number":52,"context_line":"   account users, resources, and scopes."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_00d99b7d","line":49,"range":{"start_line":49,"start_character":8,"end_line":49,"end_character":12},"updated":"2017-04-27 09:23:47.000000000","message":"Maybe we should say API user vs operator?","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":46,"context_line":"use cases in the previous section (i.e. you must crawl before you can walk, and"},{"line_number":47,"context_line":"walk before you can run)."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"1. As a user, I should be able to give fine-grained access to another user or"},{"line_number":50,"context_line":"   system."},{"line_number":51,"context_line":"2. As an operator, I should be able to build custom policies that can take into"},{"line_number":52,"context_line":"   account users, resources, and scopes."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_67974bee","line":49,"in_reply_to":"5ff73747_00d99b7d","updated":"2017-04-27 13:58:27.000000000","message":"Done","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":49,"context_line":"1. As a user, I should be able to give fine-grained access to another user or"},{"line_number":50,"context_line":"   system."},{"line_number":51,"context_line":"2. As an operator, I should be able to build custom policies that can take into"},{"line_number":52,"context_line":"   account users, resources, and scopes."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Cross-Project Impact"},{"line_number":55,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_40ba030a","line":52,"updated":"2017-04-27 09:23:47.000000000","message":"How is this different to #4 above.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":49,"context_line":"1. As a user, I should be able to give fine-grained access to another user or"},{"line_number":50,"context_line":"   system."},{"line_number":51,"context_line":"2. As an operator, I should be able to build custom policies that can take into"},{"line_number":52,"context_line":"   account users, resources, and scopes."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Cross-Project Impact"},{"line_number":55,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_07eac7aa","line":52,"in_reply_to":"5ff73747_40ba030a","updated":"2017-04-27 13:58:27.000000000","message":"Here I was kind of thinking about the Amazon case where you can string together super interesting policies, and not just mapping operations to roles and giving roles to users. For example, if I wanted to write a policy that took into account the `auth_factor_count` attribute from a SAML assertion (i.e. I authenticated via password, tongue print, and retina scan for a token), I could make it so that the `admin` role is available only when the `auth_factor_count` \u003e\u003d 3. That example is really far away from what we have today, which is why I listed it here.\n\nI think the flexibility of being able to do something like that would fit nicely with external Identity Providers and SAML in general.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":61,"context_line":"made several attempts to address these issues (linked below in the References"},{"line_number":62,"context_line":"section), but having the implementation spread across OpenStack makes it"},{"line_number":63,"context_line":"impossible for a single project to propose and fix these issues without"},{"line_number":64,"context_line":"cross-project buy-in."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"One tool that at our disposal today is the usage of"},{"line_number":67,"context_line":"`Community Goals \u003chttps://governance.openstack.org/tc/goals/\u003e`_ to help move"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_000cfbea","line":64,"updated":"2017-04-27 09:23:47.000000000","message":"So currently, it appears keystone tells a project what roles a user has, the project is responsible for enforcing what that means.\n\nUnwinding that (all be it flawed) assumption, takes both sides to be involved, hence much confusion and nashing of teeth.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":61,"context_line":"made several attempts to address these issues (linked below in the References"},{"line_number":62,"context_line":"section), but having the implementation spread across OpenStack makes it"},{"line_number":63,"context_line":"impossible for a single project to propose and fix these issues without"},{"line_number":64,"context_line":"cross-project buy-in."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"One tool that at our disposal today is the usage of"},{"line_number":67,"context_line":"`Community Goals \u003chttps://governance.openstack.org/tc/goals/\u003e`_ to help move"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_c7029f3d","line":64,"in_reply_to":"5ff73747_000cfbea","updated":"2017-04-27 13:58:27.000000000","message":"Done","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"22173e10be000a86167bfc2422aacc1145ab4d29","unresolved":false,"context_lines":[{"line_number":76,"context_line":"An alternative to using cross-project goals would be to define one, or"},{"line_number":77,"context_line":"multiple, use cases into sensible `tags \u003chttps://governance.openstack.org/tc/reference/tags/index.html\u003e`_"},{"line_number":78,"context_line":"that projects can achieve. For example, if a project develops and tests a"},{"line_number":79,"context_line":"specific set of roles and implements them, they can `assert:basic-rbac`."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"References"},{"line_number":82,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_80200b4a","line":79,"updated":"2017-04-27 09:23:47.000000000","message":"Maybe both, but its good to point out these tools we now have to building community wide consensus / information sharing.","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a3c47c39c41a14721a26b55796e54209d8023be2","unresolved":false,"context_lines":[{"line_number":76,"context_line":"An alternative to using cross-project goals would be to define one, or"},{"line_number":77,"context_line":"multiple, use cases into sensible `tags \u003chttps://governance.openstack.org/tc/reference/tags/index.html\u003e`_"},{"line_number":78,"context_line":"that projects can achieve. For example, if a project develops and tests a"},{"line_number":79,"context_line":"specific set of roles and implements them, they can `assert:basic-rbac`."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"References"},{"line_number":82,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_87f81749","line":79,"in_reply_to":"5ff73747_80200b4a","updated":"2017-04-27 13:58:27.000000000","message":"Done","commit_id":"4336e14344030fc8221333dfffb008f9060b623b"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"1cf12953f2d155df2206c7c9074b6205ac9622eb","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Use Cases"},{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"The following list would increase OpenStack adopting by solving immediate"},{"line_number":23,"context_line":"security issues within OpenStack, providing documentation and default roles to"},{"line_number":24,"context_line":"operators, and enabling better delegation workflows by allowing operation-role"},{"line_number":25,"context_line":"review:"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_6265c745","line":22,"range":{"start_line":22,"start_character":44,"end_line":22,"end_character":52},"updated":"2017-04-28 18:50:15.000000000","message":"adoption","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e6a5a0d893e9e9359f5af353f5a948ba4da9492","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Use Cases"},{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"The following list would increase OpenStack adopting by solving immediate"},{"line_number":23,"context_line":"security issues within OpenStack, providing documentation and default roles to"},{"line_number":24,"context_line":"operators, and enabling better delegation workflows by allowing operation-role"},{"line_number":25,"context_line":"review:"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_788441d3","line":22,"in_reply_to":"5ff73747_6265c745","updated":"2017-05-01 14:32:54.000000000","message":"Done","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"1cf12953f2d155df2206c7c9074b6205ac9622eb","unresolved":false,"context_lines":[{"line_number":32,"context_line":"   operations through delegation."},{"line_number":33,"context_line":"3. As an operator, I should be able to easily understand which policy maps to a"},{"line_number":34,"context_line":"   particular operation or API."},{"line_number":35,"context_line":"4. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":36,"context_line":"   upon installation that I can assign to users. For example, I should be able"},{"line_number":37,"context_line":"   to delegate a user or system read-only access to a project without having to"},{"line_number":38,"context_line":"   modify policy across the services to introduce a read-only from scratch."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_e241d7aa","line":35,"range":{"start_line":35,"start_character":9,"end_line":35,"end_character":18},"updated":"2017-04-28 18:50:15.000000000","message":"typo - operator","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e6a5a0d893e9e9359f5af353f5a948ba4da9492","unresolved":false,"context_lines":[{"line_number":32,"context_line":"   operations through delegation."},{"line_number":33,"context_line":"3. As an operator, I should be able to easily understand which policy maps to a"},{"line_number":34,"context_line":"   particular operation or API."},{"line_number":35,"context_line":"4. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":36,"context_line":"   upon installation that I can assign to users. For example, I should be able"},{"line_number":37,"context_line":"   to delegate a user or system read-only access to a project without having to"},{"line_number":38,"context_line":"   modify policy across the services to introduce a read-only from scratch."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_8371deaa","line":35,"in_reply_to":"5ff73747_e241d7aa","updated":"2017-05-01 14:32:54.000000000","message":"Done","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"1cf12953f2d155df2206c7c9074b6205ac9622eb","unresolved":false,"context_lines":[{"line_number":35,"context_line":"4. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":36,"context_line":"   upon installation that I can assign to users. For example, I should be able"},{"line_number":37,"context_line":"   to delegate a user or system read-only access to a project without having to"},{"line_number":38,"context_line":"   modify policy across the services to introduce a read-only from scratch."},{"line_number":39,"context_line":"   This is important because it allows to better usability out-of-the-box,"},{"line_number":40,"context_line":"   which in turn leads to better interoperability."},{"line_number":41,"context_line":"5. As an operator, I should be able to easily modify and maintain my own"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_c2013b3a","line":38,"range":{"start_line":38,"start_character":40,"end_line":38,"end_character":74},"updated":"2017-04-28 18:50:15.000000000","message":"this reads a little strange","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e6a5a0d893e9e9359f5af353f5a948ba4da9492","unresolved":false,"context_lines":[{"line_number":35,"context_line":"4. As an operation, I should have a variety of sensible roles at my disposal"},{"line_number":36,"context_line":"   upon installation that I can assign to users. For example, I should be able"},{"line_number":37,"context_line":"   to delegate a user or system read-only access to a project without having to"},{"line_number":38,"context_line":"   modify policy across the services to introduce a read-only from scratch."},{"line_number":39,"context_line":"   This is important because it allows to better usability out-of-the-box,"},{"line_number":40,"context_line":"   which in turn leads to better interoperability."},{"line_number":41,"context_line":"5. As an operator, I should be able to easily modify and maintain my own"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_436756ea","line":38,"in_reply_to":"5ff73747_c2013b3a","updated":"2017-05-01 14:32:54.000000000","message":"Done","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"1cf12953f2d155df2206c7c9074b6205ac9622eb","unresolved":false,"context_lines":[{"line_number":36,"context_line":"   upon installation that I can assign to users. For example, I should be able"},{"line_number":37,"context_line":"   to delegate a user or system read-only access to a project without having to"},{"line_number":38,"context_line":"   modify policy across the services to introduce a read-only from scratch."},{"line_number":39,"context_line":"   This is important because it allows to better usability out-of-the-box,"},{"line_number":40,"context_line":"   which in turn leads to better interoperability."},{"line_number":41,"context_line":"5. As an operator, I should be able to easily modify and maintain my own"},{"line_number":42,"context_line":"   policies."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_a2918ff3","line":39,"range":{"start_line":39,"start_character":32,"end_line":39,"end_character":58},"updated":"2017-04-28 18:50:15.000000000","message":"allows for better usability or provides better usability","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e6a5a0d893e9e9359f5af353f5a948ba4da9492","unresolved":false,"context_lines":[{"line_number":36,"context_line":"   upon installation that I can assign to users. For example, I should be able"},{"line_number":37,"context_line":"   to delegate a user or system read-only access to a project without having to"},{"line_number":38,"context_line":"   modify policy across the services to introduce a read-only from scratch."},{"line_number":39,"context_line":"   This is important because it allows to better usability out-of-the-box,"},{"line_number":40,"context_line":"   which in turn leads to better interoperability."},{"line_number":41,"context_line":"5. As an operator, I should be able to easily modify and maintain my own"},{"line_number":42,"context_line":"   policies."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_23620ad9","line":39,"in_reply_to":"5ff73747_a2918ff3","updated":"2017-05-01 14:32:54.000000000","message":"Done","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"1cf12953f2d155df2206c7c9074b6205ac9622eb","unresolved":false,"context_lines":[{"line_number":56,"context_line":"use cases in the previous section (i.e. you must crawl before you can walk, and"},{"line_number":57,"context_line":"walk before you can run)."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"1. As an API user, I should be able to give fine-grained access to another user"},{"line_number":60,"context_line":"   or system."},{"line_number":61,"context_line":"2. As an API user, I should be able to build custom policies that can take into"},{"line_number":62,"context_line":"   account users, resources, and scopes."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_3d7c8281","line":59,"range":{"start_line":59,"start_character":39,"end_line":59,"end_character":43},"updated":"2017-04-28 18:50:15.000000000","message":"delegate","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e6a5a0d893e9e9359f5af353f5a948ba4da9492","unresolved":false,"context_lines":[{"line_number":56,"context_line":"use cases in the previous section (i.e. you must crawl before you can walk, and"},{"line_number":57,"context_line":"walk before you can run)."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"1. As an API user, I should be able to give fine-grained access to another user"},{"line_number":60,"context_line":"   or system."},{"line_number":61,"context_line":"2. As an API user, I should be able to build custom policies that can take into"},{"line_number":62,"context_line":"   account users, resources, and scopes."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_436ab619","line":59,"in_reply_to":"5ff73747_3d7c8281","updated":"2017-05-01 14:32:54.000000000","message":"Done","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"1cf12953f2d155df2206c7c9074b6205ac9622eb","unresolved":false,"context_lines":[{"line_number":106,"context_line":"`Policy rules managed from a database specification \u003chttps://review.openstack.org/#/c/133814\u003e`_"},{"line_number":107,"context_line":"`Add policy-remove-scope-checks specification \u003chttps://review.openstack.org/#/c/433037/\u003e`_"},{"line_number":108,"context_line":"`Add additional-default-policy-roles specification \u003chttps://review.openstack.org/#/c/427872/\u003e`_"},{"line_number":109,"context_line":"`Add policy-docs specification \u003chttps://review.openstack.org/#/c/433010/\u003e`_"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_fdacda9f","line":109,"updated":"2017-04-28 18:50:15.000000000","message":"These get rendered all in one line, I think you need to add bullet points.","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e6a5a0d893e9e9359f5af353f5a948ba4da9492","unresolved":false,"context_lines":[{"line_number":106,"context_line":"`Policy rules managed from a database specification \u003chttps://review.openstack.org/#/c/133814\u003e`_"},{"line_number":107,"context_line":"`Add policy-remove-scope-checks specification \u003chttps://review.openstack.org/#/c/433037/\u003e`_"},{"line_number":108,"context_line":"`Add additional-default-policy-roles specification \u003chttps://review.openstack.org/#/c/427872/\u003e`_"},{"line_number":109,"context_line":"`Add policy-docs specification \u003chttps://review.openstack.org/#/c/433010/\u003e`_"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_03702e07","line":109,"in_reply_to":"5ff73747_fdacda9f","updated":"2017-05-01 14:32:54.000000000","message":"Good catch. Done.","commit_id":"ad1e786ebb511d637f46cb9196aaa76181fb7185"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The following goals increase OpenStack adoption by reducing complexity,"},{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_e6c6544a","line":23,"updated":"2017-05-02 21:58:56.000000000","message":"Our first and foremost goal must be to solve bug 968696. I.e. As an operator, I should be able to grant an `admin` role to a user on a project without compromising data outside of that project. We had this as number 1 initially (and need to add it back there), but then it disappeared in patch set 3. Probably in response to John\u0027s comment, but I think he must have misunderstood what that was about. It\u0027s not about scaling and/or delegation. It\u0027s about solving what essentially amounts to either a security vulnerability (if you give folks admins who aren\u0027t supposed to have global access) or an awful limitation (if you don\u0027t give folks admin and they thus cannot do things even on their own projects that they should be able to do, because there are hard-coded requirements that you be admin to do those things).","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"1dcb2b75566fb784f2496f2493049d6a3d529ae4","unresolved":false,"context_lines":[{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The following goals increase OpenStack adoption by reducing complexity,"},{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_f8548356","line":23,"in_reply_to":"5ff73747_561d96bb","updated":"2017-11-28 21:21:33.000000000","message":"AMEN!","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The following goals increase OpenStack adoption by reducing complexity,"},{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_561d96bb","line":23,"in_reply_to":"5ff73747_e6c6544a","updated":"2017-05-03 12:51:54.000000000","message":"Took another stab at defining this without trying to rewrite the book.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"09004784471e81954f8dcfb9fb7e17a58e84fd3a","unresolved":false,"context_lines":[{"line_number":21,"context_line":"The following goals increase OpenStack adoption by reducing complexity,"},{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_d227b1c6","line":24,"updated":"2017-05-01 16:19:08.000000000","message":"Policy is three things today.\n1. RBAC\n2. Scope check\n3. Custom (Neutron etc)\n\nKeystone should only care about RBAC.\n\nThus, one goal should be to split RBAC from scope check, perform scope check in code, and RBAC in Middelware.\n\nThis document should be explicitly focused on RBAC.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":21,"context_line":"The following goals increase OpenStack adoption by reducing complexity,"},{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_46a3c801","line":24,"range":{"start_line":24,"start_character":7,"end_line":24,"end_character":17},"updated":"2017-05-02 21:58:56.000000000","message":"s/inspection/mapping/ would both a) match #2 and b) make grammatical sense (which the current phrasing does not).","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":21,"context_line":"The following goals increase OpenStack adoption by reducing complexity,"},{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_9668be21","line":24,"in_reply_to":"5ff73747_46a3c801","updated":"2017-05-03 12:51:54.000000000","message":"Done","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"48a8771da55ec33a54330a5ab6082315e91980a5","unresolved":false,"context_lines":[{"line_number":21,"context_line":"The following goals increase OpenStack adoption by reducing complexity,"},{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_66581b30","line":24,"in_reply_to":"5ff73747_d227b1c6","updated":"2017-05-01 18:44:20.000000000","message":"Yeah - that makes sense. My main purpose for proposing this document it to agree on high-level goals. I want to keep as much of the implementation out of this document as possible.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_3149188b","line":25,"range":{"start_line":25,"start_character":51,"end_line":25,"end_character":67},"updated":"2017-05-02 21:58:56.000000000","message":"I would not split \"easy to maintain\" from \"easy to understand\" as separate goals. They go hand-in-hand, as does customization (which is not mentioned). How about merge with the one above and say \"easy to understand, customize, and maintain\"?","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"1dcb2b75566fb784f2496f2493049d6a3d529ae4","unresolved":false,"context_lines":[{"line_number":22,"context_line":"allowing better interoperability, and closing existing security flaws."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_38e9cb7f","line":25,"range":{"start_line":25,"start_character":51,"end_line":25,"end_character":67},"in_reply_to":"5ff73747_3149188b","updated":"2017-11-28 21:21:33.000000000","message":"They might be at odds.  One aspect of \"East to maintain\" is that we insulate the user from more advanced policy modifications that are also more likely to break things.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"266c17d539f06c1c414c97e9dbc66f28e2a5082b","unresolved":false,"context_lines":[{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."},{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_a8df120b","line":26,"updated":"2017-05-01 17:40:45.000000000","message":"You are mixing two things here.  One is the general tooling for managing policy, and the other is the policy as applied to Keystone.\n\nBoth are important, but Keystone cannot dictate what policy another service actually implements.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"48a8771da55ec33a54330a5ab6082315e91980a5","unresolved":false,"context_lines":[{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."},{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_c6780f91","line":26,"in_reply_to":"5ff73747_a8df120b","updated":"2017-05-01 18:44:20.000000000","message":"Not sure I understand the mixing bits. I do agree that keystone shouldn\u0027t be setting those standards, that sound be an OpenStack-wide decision if anything.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":24,"context_line":"1. The inspection of policies to operations should be easy to understand."},{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."},{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"},{"line_number":30,"context_line":"   installation, or upgrade."},{"line_number":31,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_515ed645","line":28,"range":{"start_line":27,"start_character":3,"end_line":28,"end_character":34},"updated":"2017-05-02 21:58:56.000000000","message":"because endpoints aren\u0027t project-specific, is that what you mean to say? I can\u0027t think of another reason, yet I think missing that \"because\" is causing some confusion here. And that the first sentence is way too ambiguous. I think (hope?) you\u0027re trying to talk about bug 968696 here, in a way, but that\u0027s not coming across. E.g. 968696 isn\u0027t about \"Roles\", it\u0027s specifically about a single role - admin. And you didn\u0027t mention that bug, or the project scope boundary. Etc. We don\u0027t have a problem with roles in general. We only have this problem with admin. Which I guess you kind of alluded to with \"administrative\", but... not clear enough.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":25,"context_line":"2. The mapping of policies to operations should be easy to maintain."},{"line_number":26,"context_line":"3. Roles should be granular in their administrative rights. For example,"},{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."},{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"},{"line_number":30,"context_line":"   installation, or upgrade."},{"line_number":31,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_16994e1e","line":28,"in_reply_to":"5ff73747_515ed645","updated":"2017-05-03 12:51:54.000000000","message":"Yeah - I was trying to simplify the context of that bug into a single statement (which I must not have done). I took another stab at this and renumbered it to goal #1.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"266c17d539f06c1c414c97e9dbc66f28e2a5082b","unresolved":false,"context_lines":[{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."},{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"},{"line_number":30,"context_line":"   installation, or upgrade."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Future Goals"},{"line_number":33,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_c8d37e00","line":30,"updated":"2017-05-01 17:40:45.000000000","message":"Suggest we replace \"sensibe\" with something like \"identified set of roles that implementing then most common requested use cases\"\n\nMore essential than adding new roles it making it possible for people with existing role setups to migrate to the standardized set of roles.  Please make that either a sub section of step 4 or its own top level bullet.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."},{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"},{"line_number":30,"context_line":"   installation, or upgrade."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Future Goals"},{"line_number":33,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_7444201c","line":30,"in_reply_to":"5ff73747_2667b3eb","updated":"2017-05-02 21:58:56.000000000","message":"I think \"easy to maintain\" and \"possible to migrate to this new thing\" are different... the former can easily assume you\u0027ve already done the latter (or started with this new thing and didn\u0027t even need migration).","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."},{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"},{"line_number":30,"context_line":"   installation, or upgrade."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Future Goals"},{"line_number":33,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_2afe1aae","line":30,"in_reply_to":"5ff73747_7444201c","updated":"2017-05-03 12:51:54.000000000","message":"Yeah - so my main reason for doing this was to try and separate those two things, because I think both are important. We have users that customize policy and we can\u0027t break them, hence goal #2. At the same time, we should get to a point where we can supply a bunch of default roles that doesn\u0027t require a new deployment to have to customize things on their own. For this case I was thinking about project admin type roles, or observer type roles that should be available out of the box (i.e. Google offers a bunch of roles out of the box).\n\nI think the benefits of having defaults work out of the box (pending a fix for bug 968696) will address 95% of policy customization today and hopefully result in better interoperability (each deployment shouldn\u0027t have a special unicorn that is policy if they don\u0027t need it).","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"48a8771da55ec33a54330a5ab6082315e91980a5","unresolved":false,"context_lines":[{"line_number":27,"context_line":"   granting an administrator role to a user on a project shouldn\u0027t result in"},{"line_number":28,"context_line":"   the ability to modify endpoints."},{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"},{"line_number":30,"context_line":"   installation, or upgrade."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Future Goals"},{"line_number":33,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_2667b3eb","line":30,"in_reply_to":"5ff73747_c8d37e00","updated":"2017-05-01 18:44:20.000000000","message":"++ I agree, but I also think that is implied by the second point in this list.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"},{"line_number":30,"context_line":"   installation, or upgrade."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Future Goals"},{"line_number":33,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The following goals have been brought up in discussions several times. At this"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_5487e4b7","line":32,"updated":"2017-05-02 21:58:56.000000000","message":"In our last meeting we had discussed that it should be possible to ask (i.e. new API) what actions a given role (and/or token?) allows you to perform (subject to policy constraints... e.g. with default policy we\u0027d probably only allow a non-admin to ask about roles that they have, while an admin could ask about all possible roles for their scope). I think this was in an earlier version, but removed when John commented that this is part of the ongoing capabilities discussions. I agree that there is definitely overlap with that other discussion. I still think it bears mentioning here, with references to the capabilities discussion. There are significant policy concerns there, and this is a policy goals spec.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":29,"context_line":"4. A variety of sensible roles should be available by default upon"},{"line_number":30,"context_line":"   installation, or upgrade."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Future Goals"},{"line_number":33,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The following goals have been brought up in discussions several times. At this"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_ed3a8c96","line":32,"in_reply_to":"5ff73747_5487e4b7","updated":"2017-05-03 12:51:54.000000000","message":"I attempted to add this back into the Future goals section. Let me know what you think.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"266c17d539f06c1c414c97e9dbc66f28e2a5082b","unresolved":false,"context_lines":[{"line_number":39,"context_line":"and walk before you can run)."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"1. It should be possible to delegate fine-grained access to another user or"},{"line_number":42,"context_line":"   system."},{"line_number":43,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":44,"context_line":"   account users, resources, and scopes."},{"line_number":45,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_08f7268d","line":42,"updated":"2017-05-01 17:40:45.000000000","message":"So, it is already possible to delegate fine grained access, or at least as fine grained as possible.\n\nIf you are talking about delegating less than roles (individual operations not covered by roles) than I would argue we should not do that.\n\nI think you should remove the above line.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":39,"context_line":"and walk before you can run)."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"1. It should be possible to delegate fine-grained access to another user or"},{"line_number":42,"context_line":"   system."},{"line_number":43,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":44,"context_line":"   account users, resources, and scopes."},{"line_number":45,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_ed796c93","line":42,"in_reply_to":"5ff73747_08f7268d","updated":"2017-05-03 12:51:54.000000000","message":"Done","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"48a8771da55ec33a54330a5ab6082315e91980a5","unresolved":false,"context_lines":[{"line_number":39,"context_line":"and walk before you can run)."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"1. It should be possible to delegate fine-grained access to another user or"},{"line_number":42,"context_line":"   system."},{"line_number":43,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":44,"context_line":"   account users, resources, and scopes."},{"line_number":45,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_e68aeb61","line":42,"in_reply_to":"5ff73747_08f7268d","updated":"2017-05-01 18:44:20.000000000","message":"I should amend this because your comment is proof that this is lacking an important piece, the resource.\n\nThis should explain that there should be fine-grained access to other users or systems on specific resources (i.e. I want to give Bob the ability to reboot a specific instance). Which isn\u0027t exactly possible today since even if roles were honored across projects, I\u0027d be giving Bob the ability to reboot any instances, and not *this* particular instance.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"266c17d539f06c1c414c97e9dbc66f28e2a5082b","unresolved":false,"context_lines":[{"line_number":41,"context_line":"1. It should be possible to delegate fine-grained access to another user or"},{"line_number":42,"context_line":"   system."},{"line_number":43,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":44,"context_line":"   account users, resources, and scopes."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Cross-Project Impact"},{"line_number":47,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_083cc62c","line":44,"updated":"2017-05-01 17:40:45.000000000","message":"Scopes are hard coded, and should be checked by the projects.  \n\nPolicy/RBAC is already built around scopes.\n\nI think what youare trying to say is that per user and per resource is out of the scope here, and I fully concur.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"48a8771da55ec33a54330a5ab6082315e91980a5","unresolved":false,"context_lines":[{"line_number":41,"context_line":"1. It should be possible to delegate fine-grained access to another user or"},{"line_number":42,"context_line":"   system."},{"line_number":43,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":44,"context_line":"   account users, resources, and scopes."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Cross-Project Impact"},{"line_number":47,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_86f1e703","line":44,"in_reply_to":"5ff73747_083cc62c","updated":"2017-05-01 18:44:20.000000000","message":"Yes - exactly. Let\u0027s crawl before we walk.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":41,"context_line":"1. It should be possible to delegate fine-grained access to another user or"},{"line_number":42,"context_line":"   system."},{"line_number":43,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":44,"context_line":"   account users, resources, and scopes."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Cross-Project Impact"},{"line_number":47,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_94db2c4e","line":44,"in_reply_to":"5ff73747_86f1e703","updated":"2017-05-02 21:58:56.000000000","message":"Lance, I\u0027m not understanding this one. We can (and I do) customize policy today, taking into account users, resources, and scopes. Edit: ok, I see your response to John about this in patch set 2... but I think you need some kind of clarification/elaboration in the spec itself rather than just in the comments.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":41,"context_line":"1. It should be possible to delegate fine-grained access to another user or"},{"line_number":42,"context_line":"   system."},{"line_number":43,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":44,"context_line":"   account users, resources, and scopes."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Cross-Project Impact"},{"line_number":47,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_ca445677","line":44,"in_reply_to":"5ff73747_94db2c4e","updated":"2017-05-03 12:51:54.000000000","message":"Agreed - I took another stab at it.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":50,"context_line":"as a problem space within the OpenStack Identity umbrella. While that statement"},{"line_number":51,"context_line":"logically makes sense, the current implementation of policy is enforced across"},{"line_number":52,"context_line":"the OpenStack services making the ownership of the problem harder to pin point."},{"line_number":53,"context_line":"Keystone currently only acts as an information point to the service, who is"},{"line_number":54,"context_line":"ultimately responsible for enforcing the policy decision based on information"},{"line_number":55,"context_line":"from keystone and information from the project. The OpenStack community has"},{"line_number":56,"context_line":"made several attempts to address these issues (linked below in the References"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_3fcaf14e","line":53,"range":{"start_line":53,"start_character":69,"end_line":53,"end_character":72},"updated":"2017-05-02 21:58:56.000000000","message":"nit: s/who/which/","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":50,"context_line":"as a problem space within the OpenStack Identity umbrella. While that statement"},{"line_number":51,"context_line":"logically makes sense, the current implementation of policy is enforced across"},{"line_number":52,"context_line":"the OpenStack services making the ownership of the problem harder to pin point."},{"line_number":53,"context_line":"Keystone currently only acts as an information point to the service, who is"},{"line_number":54,"context_line":"ultimately responsible for enforcing the policy decision based on information"},{"line_number":55,"context_line":"from keystone and information from the project. The OpenStack community has"},{"line_number":56,"context_line":"made several attempts to address these issues (linked below in the References"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_4a584655","line":53,"in_reply_to":"5ff73747_3fcaf14e","updated":"2017-05-03 12:51:54.000000000","message":"Done","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":56,"context_line":"made several attempts to address these issues (linked below in the References"},{"line_number":57,"context_line":"section), but having the implementation spread across OpenStack makes it"},{"line_number":58,"context_line":"impossible for a single project to propose and fix these issues without"},{"line_number":59,"context_line":"cross-project buy-in, even if 95% of the work is proposed to keystone."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Cross-Project Resolution"},{"line_number":62,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_ffc36937","line":59,"range":{"start_line":59,"start_character":22,"end_line":59,"end_character":69},"updated":"2017-05-02 21:58:56.000000000","message":"which won\u0027t be the case, so I don\u0027t think we should imply that. Case in point, all the work John has been doing in nova this release needs to be done in all the other projects.","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":56,"context_line":"made several attempts to address these issues (linked below in the References"},{"line_number":57,"context_line":"section), but having the implementation spread across OpenStack makes it"},{"line_number":58,"context_line":"impossible for a single project to propose and fix these issues without"},{"line_number":59,"context_line":"cross-project buy-in, even if 95% of the work is proposed to keystone."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Cross-Project Resolution"},{"line_number":62,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_0d4c9874","line":59,"in_reply_to":"5ff73747_ffc36937","updated":"2017-05-03 12:51:54.000000000","message":"Sorry - I don\u0027t think I\u0027m following here. What won\u0027t be the case? Project buy-in? Work in keystone?","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"149998b21c2ceab86d587e32a6c3e40eacd7db94","unresolved":false,"context_lines":[{"line_number":62,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"If a proposed solution to one of the above goals requires a coordinated effort"},{"line_number":65,"context_line":"between projects, we need to use either `community goals \u003chttps://governance.openstack.org/tc/goals/\u003e`_,"},{"line_number":66,"context_line":"`tags \u003chttps://governance.openstack.org/tc/reference/tags/index.html\u003e`_,"},{"line_number":67,"context_line":"or both. These tools require cross-project communication, buy-in, and"},{"line_number":68,"context_line":"commitment."}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_1fccd55f","line":65,"range":{"start_line":65,"start_character":21,"end_line":65,"end_character":28},"updated":"2017-05-02 21:58:56.000000000","message":"nit: s/need to/will/","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":62,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"If a proposed solution to one of the above goals requires a coordinated effort"},{"line_number":65,"context_line":"between projects, we need to use either `community goals \u003chttps://governance.openstack.org/tc/goals/\u003e`_,"},{"line_number":66,"context_line":"`tags \u003chttps://governance.openstack.org/tc/reference/tags/index.html\u003e`_,"},{"line_number":67,"context_line":"or both. These tools require cross-project communication, buy-in, and"},{"line_number":68,"context_line":"commitment."}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_8d3f88b4","line":65,"in_reply_to":"5ff73747_1fccd55f","updated":"2017-05-03 12:51:54.000000000","message":"Done","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"266c17d539f06c1c414c97e9dbc66f28e2a5082b","unresolved":false,"context_lines":[{"line_number":80,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"The following are references to past or present specifications:"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* `Role Check from Middleware specification \u003chttps://review.openstack.org/#/c/391624\u003e`_"},{"line_number":85,"context_line":"* `Tokens with subsets of roles specification \u003chttps://review.openstack.org/#/c/186979\u003e`_"},{"line_number":86,"context_line":"* `Role Check on Body Key specification \u003chttps://review.openstack.org/#/c/456974\u003e`_"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_c8413ea8","line":83,"updated":"2017-05-01 17:40:45.000000000","message":"Please reference bug 968696 here","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"670d7d6210cef8be7434c3074a43f1b6fdbbb9c8","unresolved":false,"context_lines":[{"line_number":80,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"The following are references to past or present specifications:"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* `Role Check from Middleware specification \u003chttps://review.openstack.org/#/c/391624\u003e`_"},{"line_number":85,"context_line":"* `Tokens with subsets of roles specification \u003chttps://review.openstack.org/#/c/186979\u003e`_"},{"line_number":86,"context_line":"* `Role Check on Body Key specification \u003chttps://review.openstack.org/#/c/456974\u003e`_"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ff73747_2a55fa1d","line":83,"in_reply_to":"5ff73747_c8413ea8","updated":"2017-05-03 12:51:54.000000000","message":"Done","commit_id":"2efcd1a2a60a49cf96e7a63b4ef6bbc534dc6c32"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"5f74ade7c87b6eaafbb6b6cf6955efed97acf7fa","unresolved":false,"context_lines":[{"line_number":43,"context_line":"   another user or system."},{"line_number":44,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":45,"context_line":"   account users, resources, and scopes. This could result in policy being fed"},{"line_number":46,"context_line":"   different assertion on specific resources. For example, having a policy that"},{"line_number":47,"context_line":"   says a specific user can access my instance only on specific days and only"},{"line_number":48,"context_line":"   if they have specific assertions available in the SAML document they used to"},{"line_number":49,"context_line":"   authenticate."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5ff73747_cdcfd027","line":46,"range":{"start_line":46,"start_character":13,"end_line":46,"end_character":22},"updated":"2017-05-03 13:05:01.000000000","message":"assertions","commit_id":"a763946ae1fd77cd1490e75a1b74946c2d463e3d"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"685ef284c51a3d86c7ef9709acd71747ec3f335b","unresolved":false,"context_lines":[{"line_number":43,"context_line":"   another user or system."},{"line_number":44,"context_line":"2. It should be possible to build custom policies that can take into"},{"line_number":45,"context_line":"   account users, resources, and scopes. This could result in policy being fed"},{"line_number":46,"context_line":"   different assertion on specific resources. For example, having a policy that"},{"line_number":47,"context_line":"   says a specific user can access my instance only on specific days and only"},{"line_number":48,"context_line":"   if they have specific assertions available in the SAML document they used to"},{"line_number":49,"context_line":"   authenticate."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5ff73747_4f7defe5","line":46,"in_reply_to":"5ff73747_cdcfd027","updated":"2017-05-03 16:06:12.000000000","message":"Done","commit_id":"a763946ae1fd77cd1490e75a1b74946c2d463e3d"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"5f74ade7c87b6eaafbb6b6cf6955efed97acf7fa","unresolved":false,"context_lines":[{"line_number":58,"context_line":"Policy and Role Based Access Control (RBAC) has traditionally been thought of"},{"line_number":59,"context_line":"as a problem space within the OpenStack Identity umbrella. While that statement"},{"line_number":60,"context_line":"logically makes sense, the current implementation of policy is enforced across"},{"line_number":61,"context_line":"the OpenStack services making the ownership of the problem harder to pin point."},{"line_number":62,"context_line":"Keystone currently only acts as an information point to the service, which is"},{"line_number":63,"context_line":"ultimately responsible for enforcing the policy decision based on information"},{"line_number":64,"context_line":"from keystone and information from the project. The OpenStack community has"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5ff73747_cde8f07d","line":61,"range":{"start_line":61,"start_character":69,"end_line":61,"end_character":78},"updated":"2017-05-03 13:05:01.000000000","message":"pinpoint","commit_id":"a763946ae1fd77cd1490e75a1b74946c2d463e3d"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"685ef284c51a3d86c7ef9709acd71747ec3f335b","unresolved":false,"context_lines":[{"line_number":58,"context_line":"Policy and Role Based Access Control (RBAC) has traditionally been thought of"},{"line_number":59,"context_line":"as a problem space within the OpenStack Identity umbrella. While that statement"},{"line_number":60,"context_line":"logically makes sense, the current implementation of policy is enforced across"},{"line_number":61,"context_line":"the OpenStack services making the ownership of the problem harder to pin point."},{"line_number":62,"context_line":"Keystone currently only acts as an information point to the service, which is"},{"line_number":63,"context_line":"ultimately responsible for enforcing the policy decision based on information"},{"line_number":64,"context_line":"from keystone and information from the project. The OpenStack community has"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5ff73747_4fcbaf1d","line":61,"in_reply_to":"5ff73747_cde8f07d","updated":"2017-05-03 16:06:12.000000000","message":"Done","commit_id":"a763946ae1fd77cd1490e75a1b74946c2d463e3d"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"ab096da334edbe1682833475b974cd8d62121d5e","unresolved":false,"context_lines":[{"line_number":100,"context_line":"* `Policy rules managed from a database specification \u003chttps://review.openstack.org/#/c/133814\u003e`_"},{"line_number":101,"context_line":"* `Add policy-remove-scope-checks specification \u003chttps://review.openstack.org/#/c/433037/\u003e`_"},{"line_number":102,"context_line":"* `Add additional-default-policy-roles specification \u003chttps://review.openstack.org/#/c/427872/\u003e`_"},{"line_number":103,"context_line":"* `Add policy-docs specification \u003chttps://review.openstack.org/#/c/433010/\u003e`_"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5ff73747_5906e222","line":103,"updated":"2017-05-03 14:55:12.000000000","message":"add https://review.openstack.org/#/c/386555/","commit_id":"a763946ae1fd77cd1490e75a1b74946c2d463e3d"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"685ef284c51a3d86c7ef9709acd71747ec3f335b","unresolved":false,"context_lines":[{"line_number":100,"context_line":"* `Policy rules managed from a database specification \u003chttps://review.openstack.org/#/c/133814\u003e`_"},{"line_number":101,"context_line":"* `Add policy-remove-scope-checks specification \u003chttps://review.openstack.org/#/c/433037/\u003e`_"},{"line_number":102,"context_line":"* `Add additional-default-policy-roles specification \u003chttps://review.openstack.org/#/c/427872/\u003e`_"},{"line_number":103,"context_line":"* `Add policy-docs specification \u003chttps://review.openstack.org/#/c/433010/\u003e`_"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5ff73747_4f996f1d","line":103,"in_reply_to":"5ff73747_5906e222","updated":"2017-05-03 16:06:12.000000000","message":"Aha - thanks!","commit_id":"a763946ae1fd77cd1490e75a1b74946c2d463e3d"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"c613335956238d09dc5d40a703393992f9eed57c","unresolved":false,"context_lines":[{"line_number":65,"context_line":"made several attempts to address these issues (linked below in the References"},{"line_number":66,"context_line":"section), but having the implementation spread across OpenStack makes it"},{"line_number":67,"context_line":"impossible for a single project to propose and fix these issues without"},{"line_number":68,"context_line":"cross-project buy-in, even if 95% of the work is proposed to keystone."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Cross-Project Resolution"},{"line_number":71,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":6,"id":"5ff73747_989a1f6c","line":68,"range":{"start_line":68,"start_character":22,"end_line":68,"end_character":70},"updated":"2017-05-03 17:16:28.000000000","message":"I think the 95% thing needs to be removed to avoid incorrect expectations... see reasoning in patch set 4 comments.","commit_id":"86790651fb0fb581e5bcf48d447038b6e6770bae"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"7270cd73ce76857eaf885e20f36234a475b0d608","unresolved":false,"context_lines":[{"line_number":65,"context_line":"made several attempts to address these issues (linked below in the References"},{"line_number":66,"context_line":"section), but having the implementation spread across OpenStack makes it"},{"line_number":67,"context_line":"impossible for a single project to propose and fix these issues without"},{"line_number":68,"context_line":"cross-project buy-in, even if 95% of the work is proposed to keystone."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Cross-Project Resolution"},{"line_number":71,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f044301_3c569108","line":68,"in_reply_to":"5ff73747_989a1f6c","updated":"2017-05-03 18:55:06.000000000","message":"Got it - ok that makes sense. I wanted to double check.","commit_id":"86790651fb0fb581e5bcf48d447038b6e6770bae"},{"author":{"_account_id":9098,"name":"Nathan Kinder","email":"nkinder@redhat.com","username":"nkinder"},"change_message_id":"223960f6699a3febbda167a1802b8d58856f142f","unresolved":false,"context_lines":[{"line_number":27,"context_line":"   endpoints aren\u0027t a project-specific resource."},{"line_number":28,"context_line":"2. The mapping of policies to operations should be easy to understand,"},{"line_number":29,"context_line":"   customize, and maintain."},{"line_number":30,"context_line":"3. A variety of sensible roles should be available by default upon"},{"line_number":31,"context_line":"   installation, or upgrade."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Future Goals"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3f044301_3309b3dc","line":30,"range":{"start_line":30,"start_character":16,"end_line":30,"end_character":30},"updated":"2017-05-08 21:19:18.000000000","message":"It\u0027s not just sensible default roles that are needed, but sensible default policies as well.  This needs to be done across all services.  This may already be implied, but I think it should be called out explicitly here as a goal.","commit_id":"f44dfbea759ff38abe33dca159576fadb9aa8f75"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"94b3246d56a2fbf8109f9db63c381abef63088c5","unresolved":false,"context_lines":[{"line_number":27,"context_line":"   endpoints aren\u0027t a project-specific resource."},{"line_number":28,"context_line":"2. The mapping of policies to operations should be easy to understand,"},{"line_number":29,"context_line":"   customize, and maintain."},{"line_number":30,"context_line":"3. A variety of sensible roles should be available by default upon"},{"line_number":31,"context_line":"   installation, or upgrade."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Future Goals"}],"source_content_type":"text/x-rst","patch_set":7,"id":"1f013ff3_0850eb5c","line":30,"in_reply_to":"3f044301_3309b3dc","updated":"2017-05-16 15:50:52.000000000","message":"Ah - good point. Adding that to the next patch set.","commit_id":"f44dfbea759ff38abe33dca159576fadb9aa8f75"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"c695e50256c50bee4608aadc32df36eacc49598b","unresolved":false,"context_lines":[{"line_number":30,"context_line":"3. A variety of sensible roles should be available by default upon"},{"line_number":31,"context_line":"   installation, or upgrade. These roles should correspond to the default"},{"line_number":32,"context_line":"   policies provided by each project. This will require cross-project"},{"line_number":33,"context_line":"   communication to ensure the roles make sense across project boundaries."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Future Goals"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":10,"id":"ff0f0b1f_55459b16","line":33,"updated":"2017-05-17 16:21:44.000000000","message":"I think we should talk about the operator goals more directly, such as:\n\n* give a user read only access to a project\n* give a user per project admin access\n* give a user access to only one particular service for a given project\n* ability to cusomtize the policy for specific needs, so you need to understand how the policies map to operations\n\nFrom an API user point of view, there is the delegation problem, but thats in the future stuff, quite correctly.","commit_id":"dab52a344bf4bc1b0780ea6ddbf924d104dca255"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"27f2c7d56ffeab18458d48080f8adbfd1a7fdcf1","unresolved":false,"context_lines":[{"line_number":30,"context_line":"3. A variety of sensible roles should be available by default upon"},{"line_number":31,"context_line":"   installation, or upgrade. These roles should correspond to the default"},{"line_number":32,"context_line":"   policies provided by each project. This will require cross-project"},{"line_number":33,"context_line":"   communication to ensure the roles make sense across project boundaries."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Future Goals"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":10,"id":"ff0f0b1f_e1b25c94","line":33,"in_reply_to":"ff0f0b1f_55459b16","updated":"2017-05-19 22:04:29.000000000","message":"I took a crack at this, let me know if I need to add more detail though.","commit_id":"dab52a344bf4bc1b0780ea6ddbf924d104dca255"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"4d1ff08afeb4a190ab19d268ba1fbc93fb3fcb41","unresolved":false,"context_lines":[{"line_number":24,"context_line":"1. Administrative rights, via the `admin` role, should be treated consistently"},{"line_number":25,"context_line":"   across OpenStack. For example, granting an administrator role to a user on a"},{"line_number":26,"context_line":"   project shouldn\u0027t result in the ability to modify endpoints because"},{"line_number":27,"context_line":"   endpoints aren\u0027t a project-specific resource."},{"line_number":28,"context_line":"2. The mapping of policies to operations should be easy to understand,"},{"line_number":29,"context_line":"   customize, and maintain."},{"line_number":30,"context_line":"3. A variety of sensible roles should be available by default upon"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_cad99357","line":27,"range":{"start_line":27,"start_character":47,"end_line":27,"end_character":48},"updated":"2017-05-22 11:14:58.000000000","message":"adding something in the lines: \"or in the ability to modify another project\u0027s resources because roles only apply to the scope they are granted.\" would be great so that we state that roles on projects do not apply to some contexts (endpoints, hypervisors, etc) and that they only have effect within that project (bug 968696)\n\nor maybe add these 2 examples as sub-bullet points or add more details separately as you did for 3. in the lines 30-33?","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"7d13a8d042ddce0a9218f955caa727f7b7931428","unresolved":false,"context_lines":[{"line_number":24,"context_line":"1. Administrative rights, via the `admin` role, should be treated consistently"},{"line_number":25,"context_line":"   across OpenStack. For example, granting an administrator role to a user on a"},{"line_number":26,"context_line":"   project shouldn\u0027t result in the ability to modify endpoints because"},{"line_number":27,"context_line":"   endpoints aren\u0027t a project-specific resource."},{"line_number":28,"context_line":"2. The mapping of policies to operations should be easy to understand,"},{"line_number":29,"context_line":"   customize, and maintain."},{"line_number":30,"context_line":"3. A variety of sensible roles should be available by default upon"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_f4c435f7","line":27,"range":{"start_line":27,"start_character":47,"end_line":27,"end_character":48},"in_reply_to":"ff0f0b1f_cad99357","updated":"2017-05-22 15:41:44.000000000","message":"I think this is fine as is.  Lets not iterate endlessly here.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"7543f6949468bb2dfbfa63f540353f0e96197c2e","unresolved":false,"context_lines":[{"line_number":32,"context_line":"   policies provided by each project. This will require cross-project"},{"line_number":33,"context_line":"   communication to ensure the roles make sense across project boundaries."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The third item in the list above allows operators to more easily accomplish the"},{"line_number":36,"context_line":"following use-cases:"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"* Grant users read-only access to projects"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_d66a51eb","line":35,"updated":"2017-05-22 18:39:17.000000000","message":"#1 is key to the per-project admin case and #2 can facilitate the others as well as #3, so s/third item in the//","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"42cd059709580387aae96173166bc32ceff15266","unresolved":false,"context_lines":[{"line_number":32,"context_line":"   policies provided by each project. This will require cross-project"},{"line_number":33,"context_line":"   communication to ensure the roles make sense across project boundaries."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The third item in the list above allows operators to more easily accomplish the"},{"line_number":36,"context_line":"following use-cases:"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"* Grant users read-only access to projects"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_4ad40ae9","line":35,"in_reply_to":"ff0f0b1f_d66a51eb","updated":"2017-05-24 15:21:53.000000000","message":"Done","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"7543f6949468bb2dfbfa63f540353f0e96197c2e","unresolved":false,"context_lines":[{"line_number":32,"context_line":"   policies provided by each project. This will require cross-project"},{"line_number":33,"context_line":"   communication to ensure the roles make sense across project boundaries."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The third item in the list above allows operators to more easily accomplish the"},{"line_number":36,"context_line":"following use-cases:"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"* Grant users read-only access to projects"},{"line_number":39,"context_line":"* Grant users administrator permissions on a per-project basis"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_f652f53a","line":36,"range":{"start_line":35,"start_character":76,"end_line":36,"end_character":19},"updated":"2017-05-22 18:39:17.000000000","message":"s/the following use-cases/use-cases such as/","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"42cd059709580387aae96173166bc32ceff15266","unresolved":false,"context_lines":[{"line_number":33,"context_line":"   communication to ensure the roles make sense across project boundaries."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The third item in the list above allows operators to more easily accomplish the"},{"line_number":36,"context_line":"following use-cases:"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"* Grant users read-only access to projects"},{"line_number":39,"context_line":"* Grant users administrator permissions on a per-project basis"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_ea33de60","line":36,"in_reply_to":"ff0f0b1f_f652f53a","updated":"2017-05-24 15:21:53.000000000","message":"Done","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"7d13a8d042ddce0a9218f955caa727f7b7931428","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Grant users read-only access to projects"},{"line_number":39,"context_line":"* Grant users administrator permissions on a per-project basis"},{"line_number":40,"context_line":"* Grant users access to one particular service for a given project"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Future Goals"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_f47f95dd","line":41,"updated":"2017-05-22 15:41:44.000000000","message":"Change the last to \"Grant users access to a subset of the resources for a particular project.\"  THe service level boundary is only one way that this is done, and not the dominant one.  For example, don\u0027t let a uiser create or edit networks, but they still need to call Neutron to connect ports.  \n\nYou can leave the above line in as is, but if you do so, add my line as well.  A thoughtful merge of the two is appropriate, too.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"42cd059709580387aae96173166bc32ceff15266","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Grant users read-only access to projects"},{"line_number":39,"context_line":"* Grant users administrator permissions on a per-project basis"},{"line_number":40,"context_line":"* Grant users access to one particular service for a given project"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Future Goals"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_4a708a08","line":41,"in_reply_to":"ff0f0b1f_18a237fe","updated":"2017-05-24 15:21:53.000000000","message":"Done","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"42cd059709580387aae96173166bc32ceff15266","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Grant users read-only access to projects"},{"line_number":39,"context_line":"* Grant users administrator permissions on a per-project basis"},{"line_number":40,"context_line":"* Grant users access to one particular service for a given project"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Future Goals"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_2a655646","line":41,"in_reply_to":"ff0f0b1f_f47f95dd","updated":"2017-05-24 15:21:53.000000000","message":"Done","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"7543f6949468bb2dfbfa63f540353f0e96197c2e","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Grant users read-only access to projects"},{"line_number":39,"context_line":"* Grant users administrator permissions on a per-project basis"},{"line_number":40,"context_line":"* Grant users access to one particular service for a given project"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Future Goals"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_18a237fe","line":41,"in_reply_to":"ff0f0b1f_f47f95dd","updated":"2017-05-22 18:39:17.000000000","message":"better say \"resource types\", otherwise it reads as resource instances.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"4d1ff08afeb4a190ab19d268ba1fbc93fb3fcb41","unresolved":false,"context_lines":[{"line_number":48,"context_line":"goals listed in the previous section (i.e. you must crawl before you can walk,"},{"line_number":49,"context_line":"and walk before you can run)."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"1. It should be possible to delegate fine-grained access of a resource to"},{"line_number":52,"context_line":"   another user or system."},{"line_number":53,"context_line":"2. It should be possible to build custom policies that can take into account"},{"line_number":54,"context_line":"   users, resources, and scopes. This could result in policy being fed"},{"line_number":55,"context_line":"   different assertions on specific resources. For example, having a policy"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_58ffa033","line":52,"range":{"start_line":51,"start_character":3,"end_line":52,"end_character":26},"updated":"2017-05-22 11:14:58.000000000","message":"isn\u0027t this already included in the section above by 3 and its specific use-cases?","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"42cd059709580387aae96173166bc32ceff15266","unresolved":false,"context_lines":[{"line_number":49,"context_line":"and walk before you can run)."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"1. It should be possible to delegate fine-grained access of a resource to"},{"line_number":52,"context_line":"   another user or system."},{"line_number":53,"context_line":"2. It should be possible to build custom policies that can take into account"},{"line_number":54,"context_line":"   users, resources, and scopes. This could result in policy being fed"},{"line_number":55,"context_line":"   different assertions on specific resources. For example, having a policy"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_4ade4ada","line":52,"in_reply_to":"ff0f0b1f_58ffa033","updated":"2017-05-24 15:21:53.000000000","message":"I was more thinking about long term being about to grant access to specific resources in a project (i.e. I\u0027m going on vacation so I want to give you the ability to reboot my instance, but *only* my instance).","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"7d13a8d042ddce0a9218f955caa727f7b7931428","unresolved":false,"context_lines":[{"line_number":48,"context_line":"goals listed in the previous section (i.e. you must crawl before you can walk,"},{"line_number":49,"context_line":"and walk before you can run)."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"1. It should be possible to delegate fine-grained access of a resource to"},{"line_number":52,"context_line":"   another user or system."},{"line_number":53,"context_line":"2. It should be possible to build custom policies that can take into account"},{"line_number":54,"context_line":"   users, resources, and scopes. This could result in policy being fed"},{"line_number":55,"context_line":"   different assertions on specific resources. For example, having a policy"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_946e192d","line":52,"range":{"start_line":51,"start_character":3,"end_line":52,"end_character":26},"in_reply_to":"ff0f0b1f_58ffa033","updated":"2017-05-22 15:41:44.000000000","message":"Nope.  This is beyond the default roles.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"4d1ff08afeb4a190ab19d268ba1fbc93fb3fcb41","unresolved":false,"context_lines":[{"line_number":56,"context_line":"   that says a specific user can access my instance only on specific days and"},{"line_number":57,"context_line":"   only if they have specific assertions available in the SAML document they"},{"line_number":58,"context_line":"   used to authenticate."},{"line_number":59,"context_line":"3. It should be possible to determine what operations are available in a"},{"line_number":60,"context_line":"   deployment while taking role assignments into consideration. This needs to"},{"line_number":61,"context_line":"   be done in such a way that doesn\u0027t duplicate information across OpenStack"},{"line_number":62,"context_line":"   services or increase maintenance overhead for operators."},{"line_number":63,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_98bbf870","line":60,"range":{"start_line":59,"start_character":3,"end_line":60,"end_character":62},"updated":"2017-05-22 11:14:58.000000000","message":"we should be possible to do the other way around too, what roles are needed while taking an operation into consideration","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"42cd059709580387aae96173166bc32ceff15266","unresolved":false,"context_lines":[{"line_number":57,"context_line":"   only if they have specific assertions available in the SAML document they"},{"line_number":58,"context_line":"   used to authenticate."},{"line_number":59,"context_line":"3. It should be possible to determine what operations are available in a"},{"line_number":60,"context_line":"   deployment while taking role assignments into consideration. This needs to"},{"line_number":61,"context_line":"   be done in such a way that doesn\u0027t duplicate information across OpenStack"},{"line_number":62,"context_line":"   services or increase maintenance overhead for operators."},{"line_number":63,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_0a9bb217","line":60,"in_reply_to":"ff0f0b1f_54e2c1a1","updated":"2017-05-24 15:21:53.000000000","message":"This ties back to the operation -\u003e role and role -\u003e operation inspection process of the NIST RBAC document.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"7d13a8d042ddce0a9218f955caa727f7b7931428","unresolved":false,"context_lines":[{"line_number":56,"context_line":"   that says a specific user can access my instance only on specific days and"},{"line_number":57,"context_line":"   only if they have specific assertions available in the SAML document they"},{"line_number":58,"context_line":"   used to authenticate."},{"line_number":59,"context_line":"3. It should be possible to determine what operations are available in a"},{"line_number":60,"context_line":"   deployment while taking role assignments into consideration. This needs to"},{"line_number":61,"context_line":"   be done in such a way that doesn\u0027t duplicate information across OpenStack"},{"line_number":62,"context_line":"   services or increase maintenance overhead for operators."},{"line_number":63,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_54e2c1a1","line":60,"range":{"start_line":59,"start_character":3,"end_line":60,"end_character":62},"in_reply_to":"ff0f0b1f_98bbf870","updated":"2017-05-22 15:41:44.000000000","message":"Yes, and while it really is the opposite of what is stated here, one assumes a list of the known roles, the other a list of the know operations.  Both should be explicitly listed.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"4d1ff08afeb4a190ab19d268ba1fbc93fb3fcb41","unresolved":false,"context_lines":[{"line_number":74,"context_line":"made several attempts to address these issues (linked below in the References"},{"line_number":75,"context_line":"section), but having the implementation spread across OpenStack makes it"},{"line_number":76,"context_line":"impossible for a single project to propose and fix these issues without"},{"line_number":77,"context_line":"cross-project buy-in."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Cross-Project Resolution"},{"line_number":80,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_eaa217ae","line":77,"updated":"2017-05-22 11:14:58.000000000","message":"great explanation","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"4d1ff08afeb4a190ab19d268ba1fbc93fb3fcb41","unresolved":false,"context_lines":[{"line_number":93,"context_line":"These tools weren\u0027t available when previous solutions were proposed. Now that"},{"line_number":94,"context_line":"we can use them as a community, they are a natural fit for solving complex,"},{"line_number":95,"context_line":"distributed problems like policy."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"References"},{"line_number":98,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":99,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_8a9b9b64","line":96,"updated":"2017-05-22 11:14:58.000000000","message":"What is the roadmap, i.e is there an order (prioritization) to reach the goals outlined in this document?","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"7d13a8d042ddce0a9218f955caa727f7b7931428","unresolved":false,"context_lines":[{"line_number":93,"context_line":"These tools weren\u0027t available when previous solutions were proposed. Now that"},{"line_number":94,"context_line":"we can use them as a community, they are a natural fit for solving complex,"},{"line_number":95,"context_line":"distributed problems like policy."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"References"},{"line_number":98,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":99,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_9405f948","line":96,"in_reply_to":"ff0f0b1f_8a9b9b64","updated":"2017-05-22 15:41:44.000000000","message":"Beyond the scope of this document, I think.  The road map will change more quickly than the overgoals.  Lets keep them separate.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"7543f6949468bb2dfbfa63f540353f0e96197c2e","unresolved":false,"context_lines":[{"line_number":93,"context_line":"These tools weren\u0027t available when previous solutions were proposed. Now that"},{"line_number":94,"context_line":"we can use them as a community, they are a natural fit for solving complex,"},{"line_number":95,"context_line":"distributed problems like policy."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"References"},{"line_number":98,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":99,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_98f767d4","line":96,"in_reply_to":"ff0f0b1f_9405f948","updated":"2017-05-22 18:39:17.000000000","message":"this document is already laid out in priority order.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"42cd059709580387aae96173166bc32ceff15266","unresolved":false,"context_lines":[{"line_number":93,"context_line":"These tools weren\u0027t available when previous solutions were proposed. Now that"},{"line_number":94,"context_line":"we can use them as a community, they are a natural fit for solving complex,"},{"line_number":95,"context_line":"distributed problems like policy."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"References"},{"line_number":98,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":99,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"ff0f0b1f_4aa52a46","line":96,"in_reply_to":"ff0f0b1f_98f767d4","updated":"2017-05-24 15:21:53.000000000","message":"Correct. My goal was to use this document as an overall \"primer\" on our policy and isolating different problem areas. Ideally, it would be great for subsequent specs to go into detail about the implementation and possibly get worked in parallel.","commit_id":"1b31d6d92c663b125223c6abdfebbe15ff2efd50"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"39a8d48a2f76a82133988b554bd91bf2abd9921f","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"* Grant users read-only access to projects"},{"line_number":38,"context_line":"* Grant users administrator permissions on a per-project basis"},{"line_number":39,"context_line":"* Grant users access to a subset of resource types for a particular project"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Future Goals"},{"line_number":42,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":12,"id":"df140735_81f55059","line":39,"range":{"start_line":39,"start_character":26,"end_line":39,"end_character":50},"updated":"2017-06-06 11:10:12.000000000","message":"Does this mean to a subset of services (e.g neutron) or subset of resources within services (e.g just routers) ?","commit_id":"f2efedd8e440505b85a727e108122f4bdb70d1e1"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"531d9e76b79ebc1e136afd1c2b7b9a40e8f12aa0","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"* Grant users read-only access to projects"},{"line_number":38,"context_line":"* Grant users administrator permissions on a per-project basis"},{"line_number":39,"context_line":"* Grant users access to a subset of resource types for a particular project"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Future Goals"},{"line_number":42,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f436f4f_9cf03bff","line":39,"range":{"start_line":39,"start_character":26,"end_line":39,"end_character":50},"in_reply_to":"df140735_81f55059","updated":"2017-08-15 01:21:35.000000000","message":"He explicitly used the term Project as that is how OpenStack distinguishes between them. But then we use Service in the Catalog, which leads to these discussions.  But here it is talking policy for project/service, being able to distinguish between, say, Nodes and VMs in Nova.","commit_id":"f2efedd8e440505b85a727e108122f4bdb70d1e1"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"0dbeba54fc963b94829409a10e5c509504aa0ad2","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"* Grant users read-only access to projects"},{"line_number":38,"context_line":"* Grant users administrator permissions on a per-project basis"},{"line_number":39,"context_line":"* Grant users access to a subset of resource types for a particular project"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Future Goals"},{"line_number":42,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":12,"id":"df140735_386eaec8","line":39,"in_reply_to":"df140735_81f55059","updated":"2017-06-06 15:14:47.000000000","message":"The latter. If policies, roles, and scope are fixed, then it become easier to fix things like the `project_admin`. For example, you have an admin-like role you want to grant to someone but you don\u0027t want to give them the ability to do everything.\n\nMaybe a better example of this would be having a user_admin role to manage users.","commit_id":"f2efedd8e440505b85a727e108122f4bdb70d1e1"},{"author":{"_account_id":15054,"name":"wangxiyuan","email":"wangxiyuan1007@gmail.com","username":"wangxiyuan"},"change_message_id":"202f048f7c2a1a8840b81649b0424bb4985ce362","unresolved":false,"context_lines":[{"line_number":86,"context_line":"or both. These tools require cross-project communication, buy-in, and"},{"line_number":87,"context_line":"commitment."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"For example, one community goal might be to define a set of default roles and"},{"line_number":90,"context_line":"another to implement them consistently across services. Once a project tests"},{"line_number":91,"context_line":"and implements the standardized default set, they can `assert:basic-rbac` as a"},{"line_number":92,"context_line":"project tag."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"These tools weren\u0027t available when previous solutions were proposed. Now that"},{"line_number":95,"context_line":"we can use them as a community, they are a natural fit for solving complex,"}],"source_content_type":"text/x-rst","patch_set":13,"id":"1f485f77_e82f7485","line":92,"range":{"start_line":89,"start_character":0,"end_line":92,"end_character":12},"updated":"2017-11-17 02:33:47.000000000","message":"++. I\u0027d like to know when will we start this job. Is it on the plan list?","commit_id":"4c36cefc8dfb7644e58d722d11ad9b37922e3d55"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e97169e948f1e03d31a4fe16586d316e0e194b82","unresolved":false,"context_lines":[{"line_number":86,"context_line":"or both. These tools require cross-project communication, buy-in, and"},{"line_number":87,"context_line":"commitment."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"For example, one community goal might be to define a set of default roles and"},{"line_number":90,"context_line":"another to implement them consistently across services. Once a project tests"},{"line_number":91,"context_line":"and implements the standardized default set, they can `assert:basic-rbac` as a"},{"line_number":92,"context_line":"project tag."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"These tools weren\u0027t available when previous solutions were proposed. Now that"},{"line_number":95,"context_line":"we can use them as a community, they are a natural fit for solving complex,"}],"source_content_type":"text/x-rst","patch_set":13,"id":"ff82abbf_572b00ea","line":92,"range":{"start_line":89,"start_character":0,"end_line":92,"end_character":12},"in_reply_to":"1f485f77_e82f7485","updated":"2017-11-22 15:59:51.000000000","message":"Ideally, this is something we should be able to start working on for Rocky. I don\u0027t have this documented in a specification, but I do have a card detailing the work [0].\n\n[0] https://trello.com/c/C1INH5AI/7-define-default-roles","commit_id":"4c36cefc8dfb7644e58d722d11ad9b37922e3d55"}]}
