)]}'
{"specs/keystone/queens/limits-api.rst":[{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f0f76e4b4c5bf405631d8ec22857775502964b19","unresolved":false,"context_lines":[{"line_number":354,"context_line":""},{"line_number":355,"context_line":".. note::"},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"   The limits associated to a project will be validated as a flat structure."},{"line_number":358,"context_line":"   This means limits won\u0027t be enforced or validated according to the parents,"},{"line_number":359,"context_line":"   childred, or peers of the project. All limits will be independent of those"},{"line_number":360,"context_line":"   relationships. This is referred to as a \"flat\" enforcement model. Future"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_efd77bed","line":357,"range":{"start_line":357,"start_character":3,"end_line":357,"end_character":13},"updated":"2017-12-08 18:47:42.000000000","message":"Start with:\n\nThe initial implementation will only support a \"flat\" hierarchical model. In this model, the limits associated...","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"fde83545dd7873651f374870fd48dc231cb48dda","unresolved":false,"context_lines":[{"line_number":354,"context_line":""},{"line_number":355,"context_line":".. note::"},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"   The limits associated to a project will be validated as a flat structure."},{"line_number":358,"context_line":"   This means limits won\u0027t be enforced or validated according to the parents,"},{"line_number":359,"context_line":"   childred, or peers of the project. All limits will be independent of those"},{"line_number":360,"context_line":"   relationships. This is referred to as a \"flat\" enforcement model. Future"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_2a42313f","line":357,"range":{"start_line":357,"start_character":3,"end_line":357,"end_character":13},"in_reply_to":"df87a7cf_efd77bed","updated":"2017-12-08 19:04:23.000000000","message":"Done","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f0f76e4b4c5bf405631d8ec22857775502964b19","unresolved":false,"context_lines":[{"line_number":696,"context_line":"   }"},{"line_number":697,"context_line":""},{"line_number":698,"context_line":"This is allowed with flat enforcement because the hierarchy is not taken into"},{"line_number":699,"context_line":"consideration during limit validation. In the future, we may introduce a model"},{"line_number":700,"context_line":"that has the ability to validate limits with respect to project hierarchies."},{"line_number":701,"context_line":""},{"line_number":702,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_ef453bb5","line":699,"range":{"start_line":699,"start_character":57,"end_line":699,"end_character":60},"updated":"2017-12-08 18:47:42.000000000","message":"will","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"fde83545dd7873651f374870fd48dc231cb48dda","unresolved":false,"context_lines":[{"line_number":696,"context_line":"   }"},{"line_number":697,"context_line":""},{"line_number":698,"context_line":"This is allowed with flat enforcement because the hierarchy is not taken into"},{"line_number":699,"context_line":"consideration during limit validation. In the future, we may introduce a model"},{"line_number":700,"context_line":"that has the ability to validate limits with respect to project hierarchies."},{"line_number":701,"context_line":""},{"line_number":702,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_0a45ed42","line":699,"range":{"start_line":699,"start_character":57,"end_line":699,"end_character":60},"in_reply_to":"df87a7cf_ef453bb5","updated":"2017-12-08 19:04:23.000000000","message":"Done","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f0f76e4b4c5bf405631d8ec22857775502964b19","unresolved":false,"context_lines":[{"line_number":698,"context_line":"This is allowed with flat enforcement because the hierarchy is not taken into"},{"line_number":699,"context_line":"consideration during limit validation. In the future, we may introduce a model"},{"line_number":700,"context_line":"that has the ability to validate limits with respect to project hierarchies."},{"line_number":701,"context_line":""},{"line_number":702,"context_line":"Alternatives"},{"line_number":703,"context_line":"------------"},{"line_number":704,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_af15f39d","line":701,"updated":"2017-12-08 18:47:42.000000000","message":"++ this is consistent with how I understand it","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f0f76e4b4c5bf405631d8ec22857775502964b19","unresolved":false,"context_lines":[{"line_number":720,"context_line":"assume project ``alpha`` is a parent of projects ``bravo`` and ``charlie``. A"},{"line_number":721,"context_line":"flat hierarchy would allow ``bravo`` to have a limit of 10 instances while"},{"line_number":722,"context_line":"``charlie`` and ``alpha`` may only have a limit of 5 instances. From the"},{"line_number":723,"context_line":"perspective of a project hierarchy, this does not make sense. This is the first"},{"line_number":724,"context_line":"enforcement model implementation and once we build knowledge and collect"},{"line_number":725,"context_line":"usage feedback, there will be an effort to develop more sophisticated"},{"line_number":726,"context_line":"enforcement models that account for project hierarchies."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_2f29e3e4","line":723,"range":{"start_line":723,"start_character":41,"end_line":723,"end_character":60},"updated":"2017-12-08 18:47:42.000000000","message":"*may feel unintuitive.","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"fde83545dd7873651f374870fd48dc231cb48dda","unresolved":false,"context_lines":[{"line_number":720,"context_line":"assume project ``alpha`` is a parent of projects ``bravo`` and ``charlie``. A"},{"line_number":721,"context_line":"flat hierarchy would allow ``bravo`` to have a limit of 10 instances while"},{"line_number":722,"context_line":"``charlie`` and ``alpha`` may only have a limit of 5 instances. From the"},{"line_number":723,"context_line":"perspective of a project hierarchy, this does not make sense. This is the first"},{"line_number":724,"context_line":"enforcement model implementation and once we build knowledge and collect"},{"line_number":725,"context_line":"usage feedback, there will be an effort to develop more sophisticated"},{"line_number":726,"context_line":"enforcement models that account for project hierarchies."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_0a5e4d11","line":723,"range":{"start_line":723,"start_character":41,"end_line":723,"end_character":60},"in_reply_to":"df87a7cf_2f29e3e4","updated":"2017-12-08 19:04:23.000000000","message":"Done","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f0f76e4b4c5bf405631d8ec22857775502964b19","unresolved":false,"context_lines":[{"line_number":728,"context_line":"Registered limits should be considered public information and discoverable."},{"line_number":729,"context_line":"Project limits should be available to members of the project. A user with a"},{"line_number":730,"context_line":"role on project ``alpha`` should be able to list limits for the project, but"},{"line_number":731,"context_line":"not for ``bravo`` or ``charlie``. This case will become more complicated in the"},{"line_number":732,"context_line":"future when we start developing enforcement models that account for"},{"line_number":733,"context_line":"hierarchies."},{"line_number":734,"context_line":""},{"line_number":735,"context_line":"This concern was specifically mentioned in `review \u003chttps://review.openstack.org/#/c/455709/18/specs/keystone/queens/limits-api.rst,unified@650\u003e`_"},{"line_number":736,"context_line":"when discussing project hierarchies. The note was later removed as a result of"},{"line_number":737,"context_line":"flat structures in the initial implementation."},{"line_number":738,"context_line":""},{"line_number":739,"context_line":"Notifications Impact"},{"line_number":740,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_0f717f0c","line":737,"range":{"start_line":731,"start_character":34,"end_line":737,"end_character":46},"updated":"2017-12-08 18:47:42.000000000","message":"Might just give a brief summary instead of referencing an old patchset - \n\n\u0027When more complicated models are introduced, we will need a way to provide sufficient information to the user to allow them to understand why a limit update has failed or why a resource request brings them over quota without divulging too much information about related projects. This will not need to be addressed with this initial \"flat\" implementation.\u0027","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"fde83545dd7873651f374870fd48dc231cb48dda","unresolved":false,"context_lines":[{"line_number":728,"context_line":"Registered limits should be considered public information and discoverable."},{"line_number":729,"context_line":"Project limits should be available to members of the project. A user with a"},{"line_number":730,"context_line":"role on project ``alpha`` should be able to list limits for the project, but"},{"line_number":731,"context_line":"not for ``bravo`` or ``charlie``. This case will become more complicated in the"},{"line_number":732,"context_line":"future when we start developing enforcement models that account for"},{"line_number":733,"context_line":"hierarchies."},{"line_number":734,"context_line":""},{"line_number":735,"context_line":"This concern was specifically mentioned in `review \u003chttps://review.openstack.org/#/c/455709/18/specs/keystone/queens/limits-api.rst,unified@650\u003e`_"},{"line_number":736,"context_line":"when discussing project hierarchies. The note was later removed as a result of"},{"line_number":737,"context_line":"flat structures in the initial implementation."},{"line_number":738,"context_line":""},{"line_number":739,"context_line":"Notifications Impact"},{"line_number":740,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_8aa7bd0b","line":737,"range":{"start_line":731,"start_character":34,"end_line":737,"end_character":46},"in_reply_to":"df87a7cf_0f717f0c","updated":"2017-12-08 19:04:23.000000000","message":"Done","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f0f76e4b4c5bf405631d8ec22857775502964b19","unresolved":false,"context_lines":[{"line_number":752,"context_line":"Performance Impact"},{"line_number":753,"context_line":"------------------"},{"line_number":754,"context_line":""},{"line_number":755,"context_line":"The performance impact of the initial flat hierarchy design should be"},{"line_number":756,"context_line":"negligible. This will likely become more complicated once development for"},{"line_number":757,"context_line":"hierarchical enforcement models starts (e.g. calculating limits of a project"},{"line_number":758,"context_line":"with respect to its parent(s), children, and peers)."},{"line_number":759,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_cff63764","line":756,"range":{"start_line":755,"start_character":0,"end_line":756,"end_character":11},"updated":"2017-12-08 18:47:42.000000000","message":"This isn\u0027t really true. Even with a flat structure this introduces an additional network request from the service to keystone. This is why the caching notice below is important.","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"fde83545dd7873651f374870fd48dc231cb48dda","unresolved":false,"context_lines":[{"line_number":752,"context_line":"Performance Impact"},{"line_number":753,"context_line":"------------------"},{"line_number":754,"context_line":""},{"line_number":755,"context_line":"The performance impact of the initial flat hierarchy design should be"},{"line_number":756,"context_line":"negligible. This will likely become more complicated once development for"},{"line_number":757,"context_line":"hierarchical enforcement models starts (e.g. calculating limits of a project"},{"line_number":758,"context_line":"with respect to its parent(s), children, and peers)."},{"line_number":759,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_aad3a15f","line":756,"range":{"start_line":755,"start_character":0,"end_line":756,"end_character":11},"in_reply_to":"df87a7cf_cff63764","updated":"2017-12-08 19:04:23.000000000","message":"Done. I attempted to isolate the two concerns.","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f0f76e4b4c5bf405631d8ec22857775502964b19","unresolved":false,"context_lines":[{"line_number":772,"context_line":"operators, similar to how they register services in the service catalog."},{"line_number":773,"context_line":""},{"line_number":774,"context_line":"Deployments looking to offer unified limits for flat hierarchies will be able"},{"line_number":775,"context_line":"to upon completion of this implementation. Other enforcement models may be"},{"line_number":776,"context_line":"developed in the future that are more sophisticated and understand complex"},{"line_number":777,"context_line":"project hierarchies. It is important to note that switching between enforcement"},{"line_number":778,"context_line":"models will require extremely careful planning and possibly lead to API changes"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_0ff89f46","line":775,"range":{"start_line":775,"start_character":68,"end_line":775,"end_character":71},"updated":"2017-12-08 18:47:42.000000000","message":"will","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"fde83545dd7873651f374870fd48dc231cb48dda","unresolved":false,"context_lines":[{"line_number":772,"context_line":"operators, similar to how they register services in the service catalog."},{"line_number":773,"context_line":""},{"line_number":774,"context_line":"Deployments looking to offer unified limits for flat hierarchies will be able"},{"line_number":775,"context_line":"to upon completion of this implementation. Other enforcement models may be"},{"line_number":776,"context_line":"developed in the future that are more sophisticated and understand complex"},{"line_number":777,"context_line":"project hierarchies. It is important to note that switching between enforcement"},{"line_number":778,"context_line":"models will require extremely careful planning and possibly lead to API changes"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_2ac79198","line":775,"range":{"start_line":775,"start_character":68,"end_line":775,"end_character":71},"in_reply_to":"df87a7cf_0ff89f46","updated":"2017-12-08 19:04:23.000000000","message":"Done","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f0f76e4b4c5bf405631d8ec22857775502964b19","unresolved":false,"context_lines":[{"line_number":775,"context_line":"to upon completion of this implementation. Other enforcement models may be"},{"line_number":776,"context_line":"developed in the future that are more sophisticated and understand complex"},{"line_number":777,"context_line":"project hierarchies. It is important to note that switching between enforcement"},{"line_number":778,"context_line":"models will require extremely careful planning and possibly lead to API changes"},{"line_number":779,"context_line":"depending on the request being made and the new enforcement model. Deployments"},{"line_number":780,"context_line":"need to be aware of this, understand the ramifications of switching enforcement"},{"line_number":781,"context_line":"models, and the impacts it can have on existing limits."},{"line_number":782,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_6f9ccb0d","line":779,"range":{"start_line":778,"start_character":51,"end_line":779,"end_character":65},"updated":"2017-12-08 18:47:42.000000000","message":"This should be clarified earlier in the spec","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"fde83545dd7873651f374870fd48dc231cb48dda","unresolved":false,"context_lines":[{"line_number":775,"context_line":"to upon completion of this implementation. Other enforcement models may be"},{"line_number":776,"context_line":"developed in the future that are more sophisticated and understand complex"},{"line_number":777,"context_line":"project hierarchies. It is important to note that switching between enforcement"},{"line_number":778,"context_line":"models will require extremely careful planning and possibly lead to API changes"},{"line_number":779,"context_line":"depending on the request being made and the new enforcement model. Deployments"},{"line_number":780,"context_line":"need to be aware of this, understand the ramifications of switching enforcement"},{"line_number":781,"context_line":"models, and the impacts it can have on existing limits."},{"line_number":782,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_2afa31bc","line":779,"range":{"start_line":778,"start_character":51,"end_line":779,"end_character":65},"in_reply_to":"df87a7cf_6f9ccb0d","updated":"2017-12-08 19:04:23.000000000","message":"I bumped this up to the section specifically for flat hierarchy.","commit_id":"9f1013b619c9da618d59f167e69898ed6ab182be"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"162b09ba24661dc0bf66da5d4a37e331aedea5c7","unresolved":false,"context_lines":[{"line_number":648,"context_line":""},{"line_number":649,"context_line":"Flat Hierarchy Enforcement"},{"line_number":650,"context_line":"--------------------------"},{"line_number":651,"context_line":""},{"line_number":652,"context_line":"Keystone supports hierarchical multi-tenancy, where projects can be grouped"},{"line_number":653,"context_line":"into tree structures and have parents, siblings, and children. It\u0027s possible to"},{"line_number":654,"context_line":"think of various ways where a project limit interacts differently depending on"}],"source_content_type":"text/x-rst","patch_set":2,"id":"df87a7cf_0a7badbd","line":651,"updated":"2017-12-08 19:27:08.000000000","message":"This might be a good place to mention the model discovery mechanism, e.g. GET /limits-model, which would just return \"flat\" for now. This is key to allowing the introduction of new models in a deployment as we make them available and also key to preserving interoperability between deployments that have implemented different models.","commit_id":"a7b348fcddd1d9ce2d990c6723507c55892242bc"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"c255908651c08ac1c69df0bb1948ae836abeaa3a","unresolved":false,"context_lines":[{"line_number":648,"context_line":""},{"line_number":649,"context_line":"Flat Hierarchy Enforcement"},{"line_number":650,"context_line":"--------------------------"},{"line_number":651,"context_line":""},{"line_number":652,"context_line":"Keystone supports hierarchical multi-tenancy, where projects can be grouped"},{"line_number":653,"context_line":"into tree structures and have parents, siblings, and children. It\u0027s possible to"},{"line_number":654,"context_line":"think of various ways where a project limit interacts differently depending on"}],"source_content_type":"text/x-rst","patch_set":2,"id":"df87a7cf_90593036","line":651,"in_reply_to":"df87a7cf_0a7badbd","updated":"2017-12-08 20:38:02.000000000","message":"Done","commit_id":"a7b348fcddd1d9ce2d990c6723507c55892242bc"}]}
