)]}'
{"specs/keystone/ongoing/richer-policy-by-default.rst":[{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"dec611042296103a2a63416ee6eda689e404819e","unresolved":false,"context_lines":[{"line_number":13,"context_line":"Operators have complained about the lack of granularity in default policy files"},{"line_number":14,"context_line":"for several releases. We should propose a standard set of default roles that we"},{"line_number":15,"context_line":"can start moving towards. Operators can continue to override policy using their"},{"line_number":16,"context_line":"``policy.json`` files, but we should be able to provide reasonable RBAC"},{"line_number":17,"context_line":"defaults out of the box."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Problem Description"},{"line_number":20,"context_line":"\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":"fa31d9ce_237668a4","line":17,"range":{"start_line":16,"start_character":22,"end_line":17,"end_character":24},"updated":"2017-02-13 21:08:06.000000000","message":"++","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"dec611042296103a2a63416ee6eda689e404819e","unresolved":false,"context_lines":[{"line_number":24,"context_line":"and more complex deployments, it has also outgrown its dated RBAC model. The"},{"line_number":25,"context_line":"lack of granularity in our default policy forces operators to craft their own"},{"line_number":26,"context_line":"policy by hand, which is not only hard to do, but also causes inconsistencies"},{"line_number":27,"context_line":"in interoperability across deployments."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"With the ability to define policy defaults in code, we should be able to move"},{"line_number":30,"context_line":"our defaults to something more reasonable and granular."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_e3b7f037","line":27,"range":{"start_line":27,"start_character":3,"end_line":27,"end_character":19},"updated":"2017-02-13 21:08:06.000000000","message":"Not clear about this part, maybe an example.","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"508ce387296452c354074825192a8fd139d6a302","unresolved":false,"context_lines":[{"line_number":24,"context_line":"and more complex deployments, it has also outgrown its dated RBAC model. The"},{"line_number":25,"context_line":"lack of granularity in our default policy forces operators to craft their own"},{"line_number":26,"context_line":"policy by hand, which is not only hard to do, but also causes inconsistencies"},{"line_number":27,"context_line":"in interoperability across deployments."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"With the ability to define policy defaults in code, we should be able to move"},{"line_number":30,"context_line":"our defaults to something more reasonable and granular."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_91055e12","line":27,"in_reply_to":"fa31d9ce_e3b7f037","updated":"2017-02-15 04:29:54.000000000","message":"Done","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"dec611042296103a2a63416ee6eda689e404819e","unresolved":false,"context_lines":[{"line_number":47,"context_line":"* Domain member (DM): has all the ability of the Domain observer, but they can"},{"line_number":48,"context_line":"  create projects, groups, users, and roles within that domain. They can also"},{"line_number":49,"context_line":"  manage role assignments between projects users and groups within the domain."},{"line_number":50,"context_line":"* Operator observer (OO): has the ability to list services, endpoints and"},{"line_number":51,"context_line":"  regions. Users with this role cannot make any changes to the service catalog."},{"line_number":52,"context_line":"* Operator member (OM): has all the abilities of the Operator observer in"},{"line_number":53,"context_line":"  addition to being able to manage services, endpoints, and regions."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_6356a0cf","line":50,"range":{"start_line":50,"start_character":2,"end_line":50,"end_character":24},"updated":"2017-02-13 21:08:06.000000000","message":"Use case for this role?","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"508ce387296452c354074825192a8fd139d6a302","unresolved":false,"context_lines":[{"line_number":47,"context_line":"* Domain member (DM): has all the ability of the Domain observer, but they can"},{"line_number":48,"context_line":"  create projects, groups, users, and roles within that domain. They can also"},{"line_number":49,"context_line":"  manage role assignments between projects users and groups within the domain."},{"line_number":50,"context_line":"* Operator observer (OO): has the ability to list services, endpoints and"},{"line_number":51,"context_line":"  regions. Users with this role cannot make any changes to the service catalog."},{"line_number":52,"context_line":"* Operator member (OM): has all the abilities of the Operator observer in"},{"line_number":53,"context_line":"  addition to being able to manage services, endpoints, and regions."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_91539e16","line":50,"in_reply_to":"fa31d9ce_6356a0cf","updated":"2017-02-15 04:29:54.000000000","message":"Done","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"dec611042296103a2a63416ee6eda689e404819e","unresolved":false,"context_lines":[{"line_number":49,"context_line":"  manage role assignments between projects users and groups within the domain."},{"line_number":50,"context_line":"* Operator observer (OO): has the ability to list services, endpoints and"},{"line_number":51,"context_line":"  regions. Users with this role cannot make any changes to the service catalog."},{"line_number":52,"context_line":"* Operator member (OM): has all the abilities of the Operator observer in"},{"line_number":53,"context_line":"  addition to being able to manage services, endpoints, and regions."},{"line_number":54,"context_line":"* Keystone Administrator (KA): has the ability to manage anything within the"},{"line_number":55,"context_line":"  identity system."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_03688486","line":52,"range":{"start_line":52,"start_character":2,"end_line":52,"end_character":22},"updated":"2017-02-13 21:08:06.000000000","message":"Use case for this role?","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"508ce387296452c354074825192a8fd139d6a302","unresolved":false,"context_lines":[{"line_number":49,"context_line":"  manage role assignments between projects users and groups within the domain."},{"line_number":50,"context_line":"* Operator observer (OO): has the ability to list services, endpoints and"},{"line_number":51,"context_line":"  regions. Users with this role cannot make any changes to the service catalog."},{"line_number":52,"context_line":"* Operator member (OM): has all the abilities of the Operator observer in"},{"line_number":53,"context_line":"  addition to being able to manage services, endpoints, and regions."},{"line_number":54,"context_line":"* Keystone Administrator (KA): has the ability to manage anything within the"},{"line_number":55,"context_line":"  identity system."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_b156e203","line":52,"in_reply_to":"fa31d9ce_03688486","updated":"2017-02-15 04:29:54.000000000","message":"Done","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"dec611042296103a2a63416ee6eda689e404819e","unresolved":false,"context_lines":[{"line_number":51,"context_line":"  regions. Users with this role cannot make any changes to the service catalog."},{"line_number":52,"context_line":"* Operator member (OM): has all the abilities of the Operator observer in"},{"line_number":53,"context_line":"  addition to being able to manage services, endpoints, and regions."},{"line_number":54,"context_line":"* Keystone Administrator (KA): has the ability to manage anything within the"},{"line_number":55,"context_line":"  identity system."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_c3c3cc87","line":54,"range":{"start_line":54,"start_character":2,"end_line":54,"end_character":29},"updated":"2017-02-13 21:08:06.000000000","message":"Use case as to why this role is needed. And I\u0027d prefer it not be named Keystone Admin, maybe Identity Administrator.","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"508ce387296452c354074825192a8fd139d6a302","unresolved":false,"context_lines":[{"line_number":51,"context_line":"  regions. Users with this role cannot make any changes to the service catalog."},{"line_number":52,"context_line":"* Operator member (OM): has all the abilities of the Operator observer in"},{"line_number":53,"context_line":"  addition to being able to manage services, endpoints, and regions."},{"line_number":54,"context_line":"* Keystone Administrator (KA): has the ability to manage anything within the"},{"line_number":55,"context_line":"  identity system."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_d1599636","line":54,"in_reply_to":"fa31d9ce_c3c3cc87","updated":"2017-02-15 04:29:54.000000000","message":"Done, I kept the name the same to match what Nova is currently doing.","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"dec611042296103a2a63416ee6eda689e404819e","unresolved":false,"context_lines":[{"line_number":62,"context_line":"Security Impact"},{"line_number":63,"context_line":"---------------"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"This would effectively improve security by coupling operations according to"},{"line_number":66,"context_line":"how destructive they are in nature. This also makes it easier for new"},{"line_number":67,"context_line":"deployments to achieve the principal of least operation by providing roles that"},{"line_number":68,"context_line":"only give users what they need and nothing more."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_638060f8","line":65,"range":{"start_line":65,"start_character":11,"end_line":65,"end_character":22},"updated":"2017-02-13 21:08:06.000000000","message":"nit: \u0027eventually\u0027 as the other services would have to utilize the new roles first before we would see significant benefits.","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"508ce387296452c354074825192a8fd139d6a302","unresolved":false,"context_lines":[{"line_number":62,"context_line":"Security Impact"},{"line_number":63,"context_line":"---------------"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"This would effectively improve security by coupling operations according to"},{"line_number":66,"context_line":"how destructive they are in nature. This also makes it easier for new"},{"line_number":67,"context_line":"deployments to achieve the principal of least operation by providing roles that"},{"line_number":68,"context_line":"only give users what they need and nothing more."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa31d9ce_917abe86","line":65,"in_reply_to":"fa31d9ce_638060f8","updated":"2017-02-15 04:29:54.000000000","message":"Done","commit_id":"00a66ef83eba7d35f1b6f0f6c50a69c4264c823f"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"f7d6bb2064cf51d5b3f94a1c0f613f6dd56858cd","unresolved":false,"context_lines":[{"line_number":34,"context_line":"With the ability to define policy defaults in code, we should be able to move"},{"line_number":35,"context_line":"our defaults to something more reasonable and granular."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Proposed Change"},{"line_number":38,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"We should provide the following roles by default in our policy:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"da36d5c6_61cb7173","line":37,"range":{"start_line":37,"start_character":0,"end_line":37,"end_character":15},"updated":"2017-02-18 17:08:05.000000000","message":"this can clearly take advantage of implied roles, maybe cite the feature?","commit_id":"05371b67d1703c864386b1b74fe1c915dc67e15e"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"f7d6bb2064cf51d5b3f94a1c0f613f6dd56858cd","unresolved":false,"context_lines":[{"line_number":61,"context_line":"* Keystone Administrator (KA): has the ability to manage anything within the"},{"line_number":62,"context_line":"  identity system. This would effectively be the cloud administrator who is in"},{"line_number":63,"context_line":"  control of the entire deployment."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Alternatives"},{"line_number":66,"context_line":"------------"},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"da36d5c6_41ce6d84","line":64,"updated":"2017-02-18 17:08:05.000000000","message":"why not use \"admin\" instead of \"member\"? The control of resources (create, update, delete) sounds like \"admin\" to me.","commit_id":"05371b67d1703c864386b1b74fe1c915dc67e15e"}]}
