)]}'
{"specs/keystone/rocky/strict-two-level-enforcement-model.rst":[{"author":{"_account_id":15054,"name":"wangxiyuan","email":"wangxiyuan1007@gmail.com","username":"wangxiyuan"},"change_message_id":"2a0d88e99964b0a9e35069f120dae516dd22d1d5","unresolved":false,"context_lines":[{"line_number":363,"context_line":""},{"line_number":364,"context_line":"If keystone is configured to use the ``strict-two-level`` enforcement model and"},{"line_number":365,"context_line":"current project structure within keystone violates the two-level project"},{"line_number":366,"context_line":"constraint, keystone should fail to start. To aid operators, we can develop a"},{"line_number":367,"context_line":"``keystone-manage`` command, to check the hierarchical structure of the"},{"line_number":368,"context_line":"projects in the deployment and warn operators if keystone is going to fail to"},{"line_number":369,"context_line":"start. This gives operators the ability to check and fix their project"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_432000f8","line":366,"range":{"start_line":366,"start_character":12,"end_line":366,"end_character":41},"updated":"2018-06-08 02:36:54.000000000","message":"Colleen\u0027s comment should be addressed as well. i.e. what keystone will do to refuse to start?\nMay be something like: keystone will scan the database to get the project depth, and then compare it with \"max_project_tree_depth\" and the specified limit model. If the depth is broken, then refuse to start.","commit_id":"6d5265c1bc49376c6b33e775ac9c33e5c375d766"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a1b4fe898b3ce1b57fdaf465296e2f2ebe85edca","unresolved":false,"context_lines":[{"line_number":363,"context_line":""},{"line_number":364,"context_line":"If keystone is configured to use the ``strict-two-level`` enforcement model and"},{"line_number":365,"context_line":"current project structure within keystone violates the two-level project"},{"line_number":366,"context_line":"constraint, keystone should fail to start. To aid operators, we can develop a"},{"line_number":367,"context_line":"``keystone-manage`` command, to check the hierarchical structure of the"},{"line_number":368,"context_line":"projects in the deployment and warn operators if keystone is going to fail to"},{"line_number":369,"context_line":"start. This gives operators the ability to check and fix their project"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_7d7030db","line":366,"range":{"start_line":366,"start_character":12,"end_line":366,"end_character":41},"in_reply_to":"5f7c97a3_1807d2cb","updated":"2018-06-08 13:52:57.000000000","message":"Done","commit_id":"6d5265c1bc49376c6b33e775ac9c33e5c375d766"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"c6957e059f50893f5cb9adef97c18be68787bb27","unresolved":false,"context_lines":[{"line_number":363,"context_line":""},{"line_number":364,"context_line":"If keystone is configured to use the ``strict-two-level`` enforcement model and"},{"line_number":365,"context_line":"current project structure within keystone violates the two-level project"},{"line_number":366,"context_line":"constraint, keystone should fail to start. To aid operators, we can develop a"},{"line_number":367,"context_line":"``keystone-manage`` command, to check the hierarchical structure of the"},{"line_number":368,"context_line":"projects in the deployment and warn operators if keystone is going to fail to"},{"line_number":369,"context_line":"start. This gives operators the ability to check and fix their project"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_1807d2cb","line":366,"range":{"start_line":366,"start_character":12,"end_line":366,"end_character":41},"in_reply_to":"5f7c97a3_432000f8","updated":"2018-06-08 07:18:48.000000000","message":"++\n\nIt just needs to be as simple as enforcing that setting [limit]/model\u003dstrict-two-level requires also setting [DEFAULT]/max_project_tree_depth\u003d2.","commit_id":"6d5265c1bc49376c6b33e775ac9c33e5c375d766"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"c6957e059f50893f5cb9adef97c18be68787bb27","unresolved":false,"context_lines":[{"line_number":582,"context_line":""},{"line_number":583,"context_line":"Client-side caching is going to be a very specific case that needs to be"},{"line_number":584,"context_line":"handled carefully because cache invalidation strategies are going to be"},{"line_number":585,"context_line":"distributed across services. One possible mitigation would be for client-side"},{"line_number":586,"context_line":"caching and keystone to share the same cache instance, making it easier to"},{"line_number":587,"context_line":"perform cache invalidation. Conversely, this raises the operational bar for"},{"line_number":588,"context_line":"administrators and requires assumptions about underlying infrastructure."},{"line_number":589,"context_line":""},{"line_number":590,"context_line":"Until we know we can make those types of assumptions or find an alternative"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_9844421b","line":587,"range":{"start_line":585,"start_character":28,"end_line":587,"end_character":27},"updated":"2018-06-08 07:18:48.000000000","message":"I think there are a lot of deployment types where this would not be suitable, for instance if the client-side service is in a different region from the keystone instance.","commit_id":"6d5265c1bc49376c6b33e775ac9c33e5c375d766"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a1b4fe898b3ce1b57fdaf465296e2f2ebe85edca","unresolved":false,"context_lines":[{"line_number":582,"context_line":""},{"line_number":583,"context_line":"Client-side caching is going to be a very specific case that needs to be"},{"line_number":584,"context_line":"handled carefully because cache invalidation strategies are going to be"},{"line_number":585,"context_line":"distributed across services. One possible mitigation would be for client-side"},{"line_number":586,"context_line":"caching and keystone to share the same cache instance, making it easier to"},{"line_number":587,"context_line":"perform cache invalidation. Conversely, this raises the operational bar for"},{"line_number":588,"context_line":"administrators and requires assumptions about underlying infrastructure."},{"line_number":589,"context_line":""},{"line_number":590,"context_line":"Until we know we can make those types of assumptions or find an alternative"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_fd32000f","line":587,"range":{"start_line":585,"start_character":28,"end_line":587,"end_character":27},"in_reply_to":"5f7c97a3_9844421b","updated":"2018-06-08 13:52:57.000000000","message":"Right - I can omit it if it implies too much about what we think the solution is.","commit_id":"6d5265c1bc49376c6b33e775ac9c33e5c375d766"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"5fff1a89e99a45db989332e9b80481f645e2ab94","unresolved":false,"context_lines":[{"line_number":366,"context_line":"constraint, keystone should fail to start. On start-up, keystone will scan the"},{"line_number":367,"context_line":"database to ensure that all projects don\u0027t exceed two levels of hierarchy and"},{"line_number":368,"context_line":"that ``keystone.conf [DEFAULT] max_project_tree_depth \u003d 2``. If either"},{"line_number":369,"context_line":"condition fails, then keystone will refuse to start."},{"line_number":370,"context_line":""},{"line_number":371,"context_line":"To aid operators, we can develop a ``keystone-manage`` command, to check the"},{"line_number":372,"context_line":"hierarchical structure of the projects in the deployment and warn operators if"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5f7c97a3_2eb83b0f","line":369,"range":{"start_line":369,"start_character":22,"end_line":369,"end_character":52},"updated":"2018-06-08 15:54:51.000000000","message":"Suggest we clearly state Keystone will state where the issue(s) are so they can be corrected. Not just \"fail to start\"","commit_id":"bc7e093ba7144a1bcce037c9d8192fc74509eddd"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"b7a211668dbdfd111e32ce74dab91f71cc269482","unresolved":false,"context_lines":[{"line_number":366,"context_line":"constraint, keystone should fail to start. On start-up, keystone will scan the"},{"line_number":367,"context_line":"database to ensure that all projects don\u0027t exceed two levels of hierarchy and"},{"line_number":368,"context_line":"that ``keystone.conf [DEFAULT] max_project_tree_depth \u003d 2``. If either"},{"line_number":369,"context_line":"condition fails, then keystone will refuse to start."},{"line_number":370,"context_line":""},{"line_number":371,"context_line":"To aid operators, we can develop a ``keystone-manage`` command, to check the"},{"line_number":372,"context_line":"hierarchical structure of the projects in the deployment and warn operators if"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5f7c97a3_8e9aaf10","line":369,"range":{"start_line":369,"start_character":22,"end_line":369,"end_character":52},"in_reply_to":"5f7c97a3_2eb83b0f","updated":"2018-06-08 16:25:57.000000000","message":"Done","commit_id":"bc7e093ba7144a1bcce037c9d8192fc74509eddd"}]}
