)]}'
{"doc/source/admin/identity-unified-limits.rst":[{"author":{"_account_id":15054,"name":"wangxiyuan","email":"wangxiyuan1007@gmail.com","username":"wangxiyuan"},"change_message_id":"4e536c3b40d33fb3c34938b7b3e897e9545d6e8f","unresolved":false,"context_lines":[{"line_number":133,"context_line":"models if you\u0027re planning on switching from one model to another in a"},{"line_number":134,"context_line":"deployment."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Keystone exposes a ``GET /limits-model`` endpoint that returns the enforcement"},{"line_number":137,"context_line":"model selected by the deployment. This allows limit information to be"},{"line_number":138,"context_line":"discoverable and perserves interoperability between OpenStack deployments with"},{"line_number":139,"context_line":"different enforcement models."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f93b717_8e4d873f","line":136,"range":{"start_line":136,"start_character":19,"end_line":136,"end_character":41},"updated":"2018-02-01 02:02:27.000000000","message":"Since switch the enforcement models may result in backwards incompatible changes, I suppose the limits model will be controlled by a new config option rather than setting dynamicly? So I wonder what information will be returned by this API. Only the name of the model? or something like we talked before: https://review.openstack.org/#/c/455709/17/specs/keystone/queens/limits-api.rst@694, a hierarchical limit tree?\n\nMaybe we still have to think more. but As you write at L141, I think it\u0027s ok for this doc. We can update it in the future if needed IMO","commit_id":"51d22a8767cda18ea487d066cd937f4939e4a3e3"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"0ec6a805779316afac958fe9ef97c1f724697ff8","unresolved":false,"context_lines":[{"line_number":133,"context_line":"models if you\u0027re planning on switching from one model to another in a"},{"line_number":134,"context_line":"deployment."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Keystone exposes a ``GET /limits-model`` endpoint that returns the enforcement"},{"line_number":137,"context_line":"model selected by the deployment. This allows limit information to be"},{"line_number":138,"context_line":"discoverable and perserves interoperability between OpenStack deployments with"},{"line_number":139,"context_line":"different enforcement models."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f93b717_3c06da21","line":136,"range":{"start_line":136,"start_character":19,"end_line":136,"end_character":41},"in_reply_to":"5f93b717_8e4d873f","updated":"2018-02-01 17:22:20.000000000","message":"Yeah - I agree. We going to have to talk about this and see what makes sense from a usability perspective. Since the only supported model is \u0027flat\u0027, I think we have some time to figure out what this API should look like.\n\nThis will be a prerequisite to introducing another model though.","commit_id":"51d22a8767cda18ea487d066cd937f4939e4a3e3"}]}