)]}'
{"doc/source/quotas.rst":[{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"bdd77e158b183a0b1834cd9b3b33633f22d78c3d","unresolved":false,"context_lines":[{"line_number":23,"context_line":"- limits - the definition of the maximum amount of resource that"},{"line_number":24,"context_line":"  *should* be used."},{"line_number":25,"context_line":"- usage - how much is actually currently used."},{"line_number":26,"context_line":"- claims - reserved usage that is created when a new request comes in,"},{"line_number":27,"context_line":"  before the resources in question actually have been provisioned."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":".. TODO(sdague) a flow chart is probably appropriate here"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ffe62b97_3a158749","line":26,"range":{"start_line":26,"start_character":2,"end_line":26,"end_character":8},"updated":"2017-03-29 22:46:11.000000000","message":"I don\u0027t like using the word \"claims\" for quotas because in my mind, claims are a scheduling (resource tracker) thing (they are actually called Claim there). The flow server create is: quota reserve (in API), schedule to compute (scheduler), compute claim (in RT), quota commit (in compute).\n\nI\u0027d prefer using the word \"reservation\" instead of \"claim\". It\u0027s also the word used throughout the code. \n\nThough, it\u0027s soon to become obsolete with the quota counting patches I\u0027m working on (removes use of usages table and reservations table).","commit_id":"cfabd75d081f724a81781e8509cf2fc0a49e7510"}]}