)]}'
{"doc/source/user/usage.rst":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"f2b0d4e1d910901f16544c70cb5eb93ef5ee2139","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This library is meant to aid service developers performing usage checks for"},{"line_number":14,"context_line":"resources managed by their service. It does this by clearly defining what is"},{"line_number":15,"context_line":"being claim, where resources are being claimed, and encapsulating enforcement"},{"line_number":16,"context_line":"logic behind easy-to-use utilities. The following subsections introduce common"},{"line_number":17,"context_line":"terms and concepts useful for communicating within the context of usage"},{"line_number":18,"context_line":"enforcement for distributed systems."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_7f53df16","line":15,"range":{"start_line":15,"start_character":6,"end_line":15,"end_character":11},"updated":"2018-09-07 18:46:59.000000000","message":"claimed*","commit_id":"3686a086649dbf823e16839ff91fe6401f53c422"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"f2b0d4e1d910901f16544c70cb5eb93ef5ee2139","unresolved":false,"context_lines":[{"line_number":38,"context_line":"centralized in a shared service. The later is the pattern implied by the usage"},{"line_number":39,"context_line":"of this library. The justification for decoupling resource limits from"},{"line_number":40,"context_line":"individual services is to make it easier to provide a consistent experience for"},{"line_number":41,"context_line":"users or operators setting and enforcing limits, regardless of the resource."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Claim"},{"line_number":44,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_ff5fef0b","line":41,"updated":"2018-09-07 18:46:59.000000000","message":"And also because projects and users live within the shared service and not the service that owns resources.","commit_id":"3686a086649dbf823e16839ff91fe6401f53c422"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"f2b0d4e1d910901f16544c70cb5eb93ef5ee2139","unresolved":false,"context_lines":[{"line_number":57,"context_line":"Enforcement"},{"line_number":58,"context_line":"-----------"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Enforcement is the process of collection usage data, limit information, and"},{"line_number":61,"context_line":"claims in order to make a decision about whether a user should be able to"},{"line_number":62,"context_line":"obtain more resources."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_bfe9771a","line":60,"range":{"start_line":60,"start_character":30,"end_line":60,"end_character":40},"updated":"2018-09-07 18:46:59.000000000","message":"collecting*","commit_id":"3686a086649dbf823e16839ff91fe6401f53c422"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"04ac8dc65fe62820d3262f8bad83d6a557046268","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This library is meant to aid service developers performing usage checks for"},{"line_number":14,"context_line":"resources managed by their service. It does this by clearly defining what is"},{"line_number":15,"context_line":"being claim, where resources are being claimed, and encapsulating enforcement"},{"line_number":16,"context_line":"logic behind easy-to-use utilities. The following subsections introduce common"},{"line_number":17,"context_line":"terms and concepts useful for communicating within the context of usage"},{"line_number":18,"context_line":"enforcement for distributed systems."}],"source_content_type":"text/x-rst","patch_set":4,"id":"3f79a3b5_ab731db4","line":15,"range":{"start_line":15,"start_character":6,"end_line":15,"end_character":11},"updated":"2018-09-12 21:33:40.000000000","message":"claimed","commit_id":"8c906f6b11588ba84ff3330df5db82d25b15b274"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"04ac8dc65fe62820d3262f8bad83d6a557046268","unresolved":false,"context_lines":[{"line_number":35,"context_line":""},{"line_number":36,"context_line":"With respect to OpenStack, the service which owns a particular resource may"},{"line_number":37,"context_line":"also own that resource\u0027s limit. Conversely, limit information may be"},{"line_number":38,"context_line":"centralized in a shared service. The later is the pattern implied by the usage"},{"line_number":39,"context_line":"of this library. The justification for decoupling resource limits from"},{"line_number":40,"context_line":"individual services is to make it easier to provide a consistent experience for"},{"line_number":41,"context_line":"users or operators setting and enforcing limits, regardless of the resource."}],"source_content_type":"text/x-rst","patch_set":4,"id":"3f79a3b5_4b904997","line":38,"range":{"start_line":38,"start_character":37,"end_line":38,"end_character":42},"updated":"2018-09-12 21:33:40.000000000","message":"latter","commit_id":"8c906f6b11588ba84ff3330df5db82d25b15b274"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"04ac8dc65fe62820d3262f8bad83d6a557046268","unresolved":false,"context_lines":[{"line_number":43,"context_line":"Claim"},{"line_number":44,"context_line":"-----"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A claim represent the quantity of resources being asked for by someone. Claims"},{"line_number":47,"context_line":"are constrained by the relationship between resource usage and limits."},{"line_number":48,"context_line":"Successful claims are aggregated into usage."},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3f79a3b5_6bf0a5fe","line":46,"range":{"start_line":46,"start_character":8,"end_line":46,"end_character":17},"updated":"2018-09-12 21:33:40.000000000","message":"represents","commit_id":"8c906f6b11588ba84ff3330df5db82d25b15b274"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"6e86a096449c60a24ee96ffd52927f57736166f1","unresolved":false,"context_lines":[{"line_number":17,"context_line":"terms and concepts useful for communicating within the context of usage"},{"line_number":18,"context_line":"enforcement for distributed systems."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Usage"},{"line_number":21,"context_line":"-----"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Usage is the real-time allocation of resources belonging to someone or"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_92c38d58","line":20,"updated":"2018-09-18 14:14:27.000000000","message":"This is a nitpick, but wanted to note that as I was reading this I got confused between the Usage header here, which refers to quota usage, and the Usage header above, which refers to how to use the library. Would be nice if one or the other was changed - maybe the main title should be \"How to Use oslo.limit\" or something.","commit_id":"00a86a8e6e47dc406612e0d934ba499f0f7e887b"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"8e85a2c911e23003040e075f76333823d527638a","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This library is meant to aid service developers performing usage checks for"},{"line_number":14,"context_line":"resources managed by their service. It does this by clearly defining what is"},{"line_number":15,"context_line":"being claim, where resources are being claimed, and encapsulating enforcement"},{"line_number":16,"context_line":"logic behind easy-to-use utilities. The following subsections introduce common"},{"line_number":17,"context_line":"terms and concepts useful for communicating within the context of usage"},{"line_number":18,"context_line":"enforcement for distributed systems."}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f79a3b5_58e921e1","line":15,"range":{"start_line":15,"start_character":6,"end_line":15,"end_character":11},"updated":"2018-09-24 20:43:52.000000000","message":"*claimed","commit_id":"e575be7d5e71dda326a0e5686d825ecc5e6a5fcd"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"8e85a2c911e23003040e075f76333823d527638a","unresolved":false,"context_lines":[{"line_number":17,"context_line":"terms and concepts useful for communicating within the context of usage"},{"line_number":18,"context_line":"enforcement for distributed systems."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Usage"},{"line_number":21,"context_line":"-----"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Usage is the real-time allocation of resources belonging to someone or"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f79a3b5_587921c3","line":20,"updated":"2018-09-24 20:43:52.000000000","message":"To Colleen\u0027s point, I would mildly prefer to change this one (Resource Usage?) if we disambiguate the duplicate headers. Only because \"Usage\" is a standard top-level header in the Oslo docs. That\u0027s a _very_ mild preference though.","commit_id":"e575be7d5e71dda326a0e5686d825ecc5e6a5fcd"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"4cf010a3c3c0ba3a638a0260e0cf23e9170a2886","unresolved":false,"context_lines":[{"line_number":17,"context_line":"terms and concepts useful for communicating within the context of usage"},{"line_number":18,"context_line":"enforcement for distributed systems."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Usage"},{"line_number":21,"context_line":"-----"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Usage is the real-time allocation of resources belonging to someone or"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f79a3b5_fb7fc766","line":20,"in_reply_to":"3f79a3b5_587921c3","updated":"2018-09-24 20:58:44.000000000","message":"Okay, I take that back. \"Using oslo.whatever\" is the standard top-level heading. Usage is the standard cookiecutter header for this, but it\u0027s hardly universal. Also, it looks like we should update the cookiecutter docs layout to match the split between user and operator docs that we did in the other repos.\n\nhttps://raw.githubusercontent.com/openstack-dev/oslo-cookiecutter/master/oslo.%7B%7Bcookiecutter.module_name%7D%7D/doc/source/usage.rst","commit_id":"e575be7d5e71dda326a0e5686d825ecc5e6a5fcd"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"8e85a2c911e23003040e075f76333823d527638a","unresolved":false,"context_lines":[{"line_number":35,"context_line":""},{"line_number":36,"context_line":"With respect to OpenStack, the service which owns a particular resource may"},{"line_number":37,"context_line":"also own that resource\u0027s limit. Conversely, limit information may be"},{"line_number":38,"context_line":"centralized in a shared service. The later is the pattern implied by the usage"},{"line_number":39,"context_line":"of this library. The justification for decoupling resource limits from"},{"line_number":40,"context_line":"individual services is to make it easier to provide a consistent experience for"},{"line_number":41,"context_line":"users or operators setting and enforcing limits, regardless of the resource."}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f79a3b5_78f5fd83","line":38,"range":{"start_line":38,"start_character":37,"end_line":38,"end_character":42},"updated":"2018-09-24 20:43:52.000000000","message":"*latter","commit_id":"e575be7d5e71dda326a0e5686d825ecc5e6a5fcd"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"8e85a2c911e23003040e075f76333823d527638a","unresolved":false,"context_lines":[{"line_number":43,"context_line":"Claim"},{"line_number":44,"context_line":"-----"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A claim represent the quantity of resources being asked for by someone. Claims"},{"line_number":47,"context_line":"are constrained by the relationship between resource usage and limits."},{"line_number":48,"context_line":"Successful claims are aggregated into usage."},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f79a3b5_38ef85b2","line":46,"range":{"start_line":46,"start_character":8,"end_line":46,"end_character":17},"updated":"2018-09-24 20:43:52.000000000","message":"*represents","commit_id":"e575be7d5e71dda326a0e5686d825ecc5e6a5fcd"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"8e85a2c911e23003040e075f76333823d527638a","unresolved":false,"context_lines":[{"line_number":50,"context_line":"Within the OpenStack ecosystem, claims can be made against specific targets"},{"line_number":51,"context_line":"depending on the resource. For instance, a user may request two additional"},{"line_number":52,"context_line":"servers for her project. This resulting claim might be two instances, the total"},{"line_number":53,"context_line":"number of cores between both instance, the total memory consumed by both"},{"line_number":54,"context_line":"instances, or all three. The claim is also targeted to a specific project,"},{"line_number":55,"context_line":"which affects how this library asks for usage information."},{"line_number":56,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f79a3b5_982019fb","line":53,"range":{"start_line":53,"start_character":29,"end_line":53,"end_character":37},"updated":"2018-09-24 20:43:52.000000000","message":"*instances","commit_id":"e575be7d5e71dda326a0e5686d825ecc5e6a5fcd"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"8e85a2c911e23003040e075f76333823d527638a","unresolved":false,"context_lines":[{"line_number":57,"context_line":"Enforcement"},{"line_number":58,"context_line":"-----------"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Enforcement is the process of collection usage data, limit information, and"},{"line_number":61,"context_line":"claims in order to make a decision about whether a user should be able to"},{"line_number":62,"context_line":"obtain more resources."}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f79a3b5_581a81c6","line":60,"range":{"start_line":60,"start_character":30,"end_line":60,"end_character":40},"updated":"2018-09-24 20:43:52.000000000","message":"*collecting","commit_id":"e575be7d5e71dda326a0e5686d825ecc5e6a5fcd"}]}
