)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"5025a8ec50c3775b00e30513c2faa2aa98837b9f","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Lance Bragstad \u003clbragstad@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2019-02-19 19:20:32 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Describe the business value of using unified limits"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Recent threads on the openstack-discuss mailing list [0] suggest"},{"line_number":10,"context_line":"revisting the idea of formatting the help-wanted list to represent job"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9fdfeff1_ce379f4d","line":7,"range":{"start_line":7,"start_character":13,"end_line":7,"end_character":21},"updated":"2019-02-19 19:54:56.000000000","message":"I\u0027m not sure if this should be here, but I figured I would use it since it seems to be what the board suggested in 2017. Though, these benefits aren\u0027t necessarily specific to a business...","commit_id":"e64840a950adf8d4847a5ab53ca18e0e41fb998c"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"f28fce54005672d510cd1b46d1251b2bc4864af0","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Lance Bragstad \u003clbragstad@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2019-02-19 19:20:32 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Describe the business value of using unified limits"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Recent threads on the openstack-discuss mailing list [0] suggest"},{"line_number":10,"context_line":"revisting the idea of formatting the help-wanted list to represent job"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9fdfeff1_a1d8737e","line":7,"range":{"start_line":7,"start_character":13,"end_line":7,"end_character":21},"in_reply_to":"9fdfeff1_26c01950","updated":"2019-02-28 15:00:54.000000000","message":"Ack - thanks for the review, Chris.","commit_id":"e64840a950adf8d4847a5ab53ca18e0e41fb998c"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"24f966b5f4d8d5de5932fe98c4054e9d6c1ebcce","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Lance Bragstad \u003clbragstad@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2019-02-19 19:20:32 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Describe the business value of using unified limits"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Recent threads on the openstack-discuss mailing list [0] suggest"},{"line_number":10,"context_line":"revisting the idea of formatting the help-wanted list to represent job"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9fdfeff1_26c01950","line":7,"range":{"start_line":7,"start_character":13,"end_line":7,"end_character":21},"in_reply_to":"9fdfeff1_ce379f4d","updated":"2019-02-28 14:43:47.000000000","message":"I think it is good for this context","commit_id":"e64840a950adf8d4847a5ab53ca18e0e41fb998c"}],"reference/help-most-needed.rst":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"3e6029a2ffd373d2ecd8fcb3b5a41ef625fb3866","unresolved":false,"context_lines":[{"line_number":199,"context_line":"Most OpenStack services allow a resource, or a group of resources, to be"},{"line_number":200,"context_line":"accessible to end users via an API. Operators use limits to ensure users are"},{"line_number":201,"context_line":"getting the resources they pay for and need for their cloud use cases. These"},{"line_number":202,"context_line":"limits and quotas are imperative to accurate billing, settings up price"},{"line_number":203,"context_line":"structure, and ensuring resources are used evenly throughout the deployment, as"},{"line_number":204,"context_line":"operators see fit."},{"line_number":205,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_904a2059","line":202,"range":{"start_line":202,"start_character":54,"end_line":202,"end_character":62},"updated":"2019-02-19 12:04:07.000000000","message":"setting","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"3e74783bd3314e5992cd0c11ffbd5575c157fbb6","unresolved":false,"context_lines":[{"line_number":199,"context_line":"Most OpenStack services allow a resource, or a group of resources, to be"},{"line_number":200,"context_line":"accessible to end users via an API. Operators use limits to ensure users are"},{"line_number":201,"context_line":"getting the resources they pay for and need for their cloud use cases. These"},{"line_number":202,"context_line":"limits and quotas are imperative to accurate billing, settings up price"},{"line_number":203,"context_line":"structure, and ensuring resources are used evenly throughout the deployment, as"},{"line_number":204,"context_line":"operators see fit."},{"line_number":205,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_6e10f350","line":202,"range":{"start_line":202,"start_character":54,"end_line":202,"end_character":62},"in_reply_to":"9fdfeff1_904a2059","updated":"2019-02-19 19:33:45.000000000","message":"Done","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"3f0479bcf89a8be24daaca91be26a7a232be9aba","unresolved":false,"context_lines":[{"line_number":207,"context_line":"OpenStack services. Existing implementations are different across services that"},{"line_number":208,"context_line":"have support for limits and quota, leading to an inconsistent experience for"},{"line_number":209,"context_line":"deployers and handicaps the usability of the entire deployment. We need a"},{"line_number":210,"context_line":"developer, or set of developers, that are able and willing to drive this"},{"line_number":211,"context_line":"initiative."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Tasks"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_7181cb4d","line":210,"range":{"start_line":210,"start_character":32,"end_line":210,"end_character":51},"updated":"2019-02-19 01:13:11.000000000","message":"Do they have to be able out of the gate? Could they learn and evolve into supporting the work?","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"3f0479bcf89a8be24daaca91be26a7a232be9aba","unresolved":false,"context_lines":[{"line_number":207,"context_line":"OpenStack services. Existing implementations are different across services that"},{"line_number":208,"context_line":"have support for limits and quota, leading to an inconsistent experience for"},{"line_number":209,"context_line":"deployers and handicaps the usability of the entire deployment. We need a"},{"line_number":210,"context_line":"developer, or set of developers, that are able and willing to drive this"},{"line_number":211,"context_line":"initiative."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Tasks"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_71e6ab4d","line":210,"range":{"start_line":210,"start_character":0,"end_line":210,"end_character":10},"updated":"2019-02-19 01:13:11.000000000","message":"I think this should be plural instead of singular or plural. My reasoning is that if someone things that anyone can submit one person forth to make this happen, then that is both over-committing that single person to a huge number of projects, and it becomes easy for one to think \"Well, someone else will supply the person, and I shouldn\u0027t have to think about that then... Where as plural makes me think that it might be something I could help provide resources to.","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"3e74783bd3314e5992cd0c11ffbd5575c157fbb6","unresolved":false,"context_lines":[{"line_number":207,"context_line":"OpenStack services. Existing implementations are different across services that"},{"line_number":208,"context_line":"have support for limits and quota, leading to an inconsistent experience for"},{"line_number":209,"context_line":"deployers and handicaps the usability of the entire deployment. We need a"},{"line_number":210,"context_line":"developer, or set of developers, that are able and willing to drive this"},{"line_number":211,"context_line":"initiative."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Tasks"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_2eb66b40","line":210,"range":{"start_line":210,"start_character":0,"end_line":210,"end_character":10},"in_reply_to":"9fdfeff1_7059bc33","updated":"2019-02-19 19:33:45.000000000","message":"I ultimately removed this entire bit due to it feeling too much like a job description and not value (per comments from zaneb and ttx).\n\nFWIW - I was hesitant to phrase this such that the wording was _only_ plural. I didn\u0027t want to deter someone from wanting to contribute to the effort if they didn\u0027t have a team at their back, ready to help out. From an organizational perspective, some companies may be more inclined to put a single developer on an initiative they\u0027re interested, versus feeling like they have to staff an entire team for 18 months.\n\nConversely, I do see the issue with making this sole effort on a single individual. I would be open to wording this in a way that promotes communication between interested individuals, thus forming a team organically.","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"3e6029a2ffd373d2ecd8fcb3b5a41ef625fb3866","unresolved":false,"context_lines":[{"line_number":207,"context_line":"OpenStack services. Existing implementations are different across services that"},{"line_number":208,"context_line":"have support for limits and quota, leading to an inconsistent experience for"},{"line_number":209,"context_line":"deployers and handicaps the usability of the entire deployment. We need a"},{"line_number":210,"context_line":"developer, or set of developers, that are able and willing to drive this"},{"line_number":211,"context_line":"initiative."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Tasks"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_7059bc33","line":210,"range":{"start_line":210,"start_character":0,"end_line":210,"end_character":10},"in_reply_to":"9fdfeff1_71e6ab4d","updated":"2019-02-19 12:04:07.000000000","message":"I think some of that can be addressed by having another sentence after \"initiative\" that summarizes the collaborative nature of the work and the goal: These developers will work with and within the OpenStack community to create a unified system for managing resource limits.","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"3e6029a2ffd373d2ecd8fcb3b5a41ef625fb3866","unresolved":false,"context_lines":[{"line_number":220,"context_line":"* Assist project teams with implementing limit and quota enforcement logic,"},{"line_number":221,"context_line":"  keeping consistency and maintainability across projects a priority"},{"line_number":222,"context_line":"* Perform code reviews related to the unified limits implementation across"},{"line_number":223,"context_line":"  OpenStack service and shared libraries"},{"line_number":224,"context_line":"* Design and write integration tests that will eventually be a part of the"},{"line_number":225,"context_line":"  OpenStack gating system"},{"line_number":226,"context_line":"* Establish feedback loops with users and deployers and sharing that feedback"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_b078848f","line":223,"range":{"start_line":223,"start_character":12,"end_line":223,"end_character":19},"updated":"2019-02-19 12:04:07.000000000","message":"services","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"3e74783bd3314e5992cd0c11ffbd5575c157fbb6","unresolved":false,"context_lines":[{"line_number":220,"context_line":"* Assist project teams with implementing limit and quota enforcement logic,"},{"line_number":221,"context_line":"  keeping consistency and maintainability across projects a priority"},{"line_number":222,"context_line":"* Perform code reviews related to the unified limits implementation across"},{"line_number":223,"context_line":"  OpenStack service and shared libraries"},{"line_number":224,"context_line":"* Design and write integration tests that will eventually be a part of the"},{"line_number":225,"context_line":"  OpenStack gating system"},{"line_number":226,"context_line":"* Establish feedback loops with users and deployers and sharing that feedback"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_0e87e763","line":223,"range":{"start_line":223,"start_character":12,"end_line":223,"end_character":19},"in_reply_to":"9fdfeff1_b078848f","updated":"2019-02-19 19:33:45.000000000","message":"Refactored","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"3e6029a2ffd373d2ecd8fcb3b5a41ef625fb3866","unresolved":false,"context_lines":[{"line_number":221,"context_line":"  keeping consistency and maintainability across projects a priority"},{"line_number":222,"context_line":"* Perform code reviews related to the unified limits implementation across"},{"line_number":223,"context_line":"  OpenStack service and shared libraries"},{"line_number":224,"context_line":"* Design and write integration tests that will eventually be a part of the"},{"line_number":225,"context_line":"  OpenStack gating system"},{"line_number":226,"context_line":"* Establish feedback loops with users and deployers and sharing that feedback"},{"line_number":227,"context_line":"  with development teams"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_106710ed","line":224,"range":{"start_line":224,"start_character":47,"end_line":224,"end_character":57},"updated":"2019-02-19 12:04:07.000000000","message":"\u0027\u0027","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"3e74783bd3314e5992cd0c11ffbd5575c157fbb6","unresolved":false,"context_lines":[{"line_number":221,"context_line":"  keeping consistency and maintainability across projects a priority"},{"line_number":222,"context_line":"* Perform code reviews related to the unified limits implementation across"},{"line_number":223,"context_line":"  OpenStack service and shared libraries"},{"line_number":224,"context_line":"* Design and write integration tests that will eventually be a part of the"},{"line_number":225,"context_line":"  OpenStack gating system"},{"line_number":226,"context_line":"* Establish feedback loops with users and deployers and sharing that feedback"},{"line_number":227,"context_line":"  with development teams"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_6e955388","line":224,"range":{"start_line":224,"start_character":47,"end_line":224,"end_character":57},"in_reply_to":"9fdfeff1_106710ed","updated":"2019-02-19 19:33:45.000000000","message":"Refactored","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"06f3f6707d10edb37b78f53e078317ddae709deb","unresolved":false,"context_lines":[{"line_number":232,"context_line":"* Post recurring updates to public communication channels like the"},{"line_number":233,"context_line":"  openstack-discuss mailing list that share the progress of the initiative,"},{"line_number":234,"context_line":"  potential roadblocks, et cetera. (optional - but highly beneficial to users"},{"line_number":235,"context_line":"  and developers following the initiative)"},{"line_number":236,"context_line":""},{"line_number":237,"context_line":"Technical Benefits"},{"line_number":238,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_192306a9","line":235,"updated":"2019-02-14 18:32:30.000000000","message":"This could probably be elaborated on, but I just used this to kickstart a discussion.","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"06f3f6707d10edb37b78f53e078317ddae709deb","unresolved":false,"context_lines":[{"line_number":243,"context_line":"  deployers to use and more manageable for developers"},{"line_number":244,"context_line":"* Consistent experience when interacting with limits across the entire"},{"line_number":245,"context_line":"  OpenStack platform"},{"line_number":246,"context_line":"* Similar APIs lead to less complexity between client implementations"},{"line_number":247,"context_line":""},{"line_number":248,"context_line":"Contact"},{"line_number":249,"context_line":"-------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_793332f7","line":246,"updated":"2019-02-14 18:32:30.000000000","message":"Same comment here. This isn\u0027t a complete list by any means, but using it as a way to show some value to people who have the ability to delegate resources.","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"3f0479bcf89a8be24daaca91be26a7a232be9aba","unresolved":false,"context_lines":[{"line_number":243,"context_line":"  deployers to use and more manageable for developers"},{"line_number":244,"context_line":"* Consistent experience when interacting with limits across the entire"},{"line_number":245,"context_line":"  OpenStack platform"},{"line_number":246,"context_line":"* Similar APIs lead to less complexity between client implementations"},{"line_number":247,"context_line":""},{"line_number":248,"context_line":"Contact"},{"line_number":249,"context_line":"-------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_d1e0b729","line":246,"in_reply_to":"9fdfeff1_793332f7","updated":"2019-02-19 01:13:11.000000000","message":"Instead of similar, is the limits work not intended to make it a single API for limits expressions? If so, wouldn\u0027t it be a single API and reducing overall complexity of operating while providing in-depth resource management capability to operators?","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"3e74783bd3314e5992cd0c11ffbd5575c157fbb6","unresolved":false,"context_lines":[{"line_number":243,"context_line":"  deployers to use and more manageable for developers"},{"line_number":244,"context_line":"* Consistent experience when interacting with limits across the entire"},{"line_number":245,"context_line":"  OpenStack platform"},{"line_number":246,"context_line":"* Similar APIs lead to less complexity between client implementations"},{"line_number":247,"context_line":""},{"line_number":248,"context_line":"Contact"},{"line_number":249,"context_line":"-------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_eee6234b","line":246,"in_reply_to":"9fdfeff1_d1e0b729","updated":"2019-02-19 19:33:45.000000000","message":"Agreed - I attempted to reword this to be more accurate.","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"06f3f6707d10edb37b78f53e078317ddae709deb","unresolved":false,"context_lines":[{"line_number":249,"context_line":"-------"},{"line_number":250,"context_line":""},{"line_number":251,"context_line":"For questions about getting involved with this initiative, please contact"},{"line_number":252,"context_line":"the OpenStack Technical Committee."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_992e168a","line":252,"range":{"start_line":252,"start_character":4,"end_line":252,"end_character":33},"updated":"2019-02-14 18:32:30.000000000","message":"This doesn\u0027t have to be the TC. It could be anyone driving the initiative already, I suppose. If the TCs name is one it, it might make use revisit it regularly?","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"3e74783bd3314e5992cd0c11ffbd5575c157fbb6","unresolved":false,"context_lines":[{"line_number":249,"context_line":"-------"},{"line_number":250,"context_line":""},{"line_number":251,"context_line":"For questions about getting involved with this initiative, please contact"},{"line_number":252,"context_line":"the OpenStack Technical Committee."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_0eecc727","line":252,"range":{"start_line":252,"start_character":4,"end_line":252,"end_character":33},"in_reply_to":"9fdfeff1_91d46f49","updated":"2019-02-19 19:33:45.000000000","message":"Done","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"3f0479bcf89a8be24daaca91be26a7a232be9aba","unresolved":false,"context_lines":[{"line_number":249,"context_line":"-------"},{"line_number":250,"context_line":""},{"line_number":251,"context_line":"For questions about getting involved with this initiative, please contact"},{"line_number":252,"context_line":"the OpenStack Technical Committee."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fdfeff1_91d46f49","line":252,"range":{"start_line":252,"start_character":4,"end_line":252,"end_character":33},"in_reply_to":"9fdfeff1_992e168a","updated":"2019-02-19 01:13:11.000000000","message":"I think it should be the community at large. We can\u0027t make the TC the single point of contact from a bandwidth/interrupt standpoint. Also raising visibility to the community at large is key.","commit_id":"e0de05b0eed3b56f4d77403de0b3fde230e258f6"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"73ffd2d7770548628144ad9fa8dab6d7dc53a259","unresolved":false,"context_lines":[{"line_number":264,"context_line":"Contact"},{"line_number":265,"context_line":"-------"},{"line_number":266,"context_line":""},{"line_number":267,"context_line":"For questions about getting involved with this initiative, please contact reach"},{"line_number":268,"context_line":"out to the OpenStack Discuss mailing `list"},{"line_number":269,"context_line":"\u003chttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss\u003e`_."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9fdfeff1_bab29105","line":267,"updated":"2019-03-04 20:28:18.000000000","message":"\"...please contact reach out to...\" seems like a remnant of a partial edit","commit_id":"e64840a950adf8d4847a5ab53ca18e0e41fb998c"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a0a3b4a16a99dfbb14e243e5122cdd667bbef61d","unresolved":false,"context_lines":[{"line_number":264,"context_line":"Contact"},{"line_number":265,"context_line":"-------"},{"line_number":266,"context_line":""},{"line_number":267,"context_line":"For questions about getting involved with this initiative, please contact reach"},{"line_number":268,"context_line":"out to the OpenStack Discuss mailing `list"},{"line_number":269,"context_line":"\u003chttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss\u003e`_."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9fdfeff1_a06344dd","line":267,"in_reply_to":"9fdfeff1_bab29105","updated":"2019-03-04 21:50:30.000000000","message":"Done","commit_id":"e64840a950adf8d4847a5ab53ca18e0e41fb998c"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a3042dd75d026be5ffd8c70fa73fbdfc4581c94c","unresolved":false,"context_lines":[{"line_number":190,"context_line":"If you are interested in helping with community goals, contact the TC"},{"line_number":191,"context_line":"sponsor for this item (dhellmann)."},{"line_number":192,"context_line":""},{"line_number":193,"context_line":"6. Unified Limits \u0026 Quota Management"},{"line_number":194,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":195,"context_line":""},{"line_number":196,"context_line":"Description"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_677ea96c","line":193,"updated":"2019-03-08 12:43:21.000000000","message":"Just a pref not to have am ampersand in the title. But eh","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9a2ba991eae29aa78c636e2302bdad455861cd24","unresolved":false,"context_lines":[{"line_number":190,"context_line":"If you are interested in helping with community goals, contact the TC"},{"line_number":191,"context_line":"sponsor for this item (dhellmann)."},{"line_number":192,"context_line":""},{"line_number":193,"context_line":"6. Unified Limits \u0026 Quota Management"},{"line_number":194,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":195,"context_line":""},{"line_number":196,"context_line":"Description"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_e22e07f9","line":193,"in_reply_to":"5fc1f717_677ea96c","updated":"2019-03-08 14:18:19.000000000","message":"Done","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a3042dd75d026be5ffd8c70fa73fbdfc4581c94c","unresolved":false,"context_lines":[{"line_number":206,"context_line":"Currently, there isn\u0027t a unified approach to limits across OpenStack services."},{"line_number":207,"context_line":"Services that do have an API for managing resource limits share a commonality"},{"line_number":208,"context_line":"in the implementation but still suffer from inconsistencies. It is especially"},{"line_number":209,"context_line":"risky to implement limit management separately across services since the"},{"line_number":210,"context_line":"hierarchical nature of project namespaces in OpenStack can be complicated,"},{"line_number":211,"context_line":"forcing developers to solve the same hard problem over and over again. This"},{"line_number":212,"context_line":"design leaves consistency across OpenStack up to the developers from each"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_a79b31c7","line":209,"updated":"2019-03-08 12:43:21.000000000","message":"It is considered risky to implement*","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9a2ba991eae29aa78c636e2302bdad455861cd24","unresolved":false,"context_lines":[{"line_number":206,"context_line":"Currently, there isn\u0027t a unified approach to limits across OpenStack services."},{"line_number":207,"context_line":"Services that do have an API for managing resource limits share a commonality"},{"line_number":208,"context_line":"in the implementation but still suffer from inconsistencies. It is especially"},{"line_number":209,"context_line":"risky to implement limit management separately across services since the"},{"line_number":210,"context_line":"hierarchical nature of project namespaces in OpenStack can be complicated,"},{"line_number":211,"context_line":"forcing developers to solve the same hard problem over and over again. This"},{"line_number":212,"context_line":"design leaves consistency across OpenStack up to the developers from each"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_423fdb24","line":209,"in_reply_to":"5fc1f717_a79b31c7","updated":"2019-03-08 14:18:19.000000000","message":"Done","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a3042dd75d026be5ffd8c70fa73fbdfc4581c94c","unresolved":false,"context_lines":[{"line_number":208,"context_line":"in the implementation but still suffer from inconsistencies. It is especially"},{"line_number":209,"context_line":"risky to implement limit management separately across services since the"},{"line_number":210,"context_line":"hierarchical nature of project namespaces in OpenStack can be complicated,"},{"line_number":211,"context_line":"forcing developers to solve the same hard problem over and over again. This"},{"line_number":212,"context_line":"design leaves consistency across OpenStack up to the developers from each"},{"line_number":213,"context_line":"project and hoping they all implement public APIs the same way. There is work"},{"line_number":214,"context_line":"underway to consolidate the management of limits to a single service, making it"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_47aa8dd2","line":211,"updated":"2019-03-08 12:43:21.000000000","message":"can be complicated. This forces developres to solve... *(large sentence, break it down for clarity)","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9a2ba991eae29aa78c636e2302bdad455861cd24","unresolved":false,"context_lines":[{"line_number":208,"context_line":"in the implementation but still suffer from inconsistencies. It is especially"},{"line_number":209,"context_line":"risky to implement limit management separately across services since the"},{"line_number":210,"context_line":"hierarchical nature of project namespaces in OpenStack can be complicated,"},{"line_number":211,"context_line":"forcing developers to solve the same hard problem over and over again. This"},{"line_number":212,"context_line":"design leaves consistency across OpenStack up to the developers from each"},{"line_number":213,"context_line":"project and hoping they all implement public APIs the same way. There is work"},{"line_number":214,"context_line":"underway to consolidate the management of limits to a single service, making it"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_42283be1","line":211,"in_reply_to":"5fc1f717_47aa8dd2","updated":"2019-03-08 14:18:19.000000000","message":"Done","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a3042dd75d026be5ffd8c70fa73fbdfc4581c94c","unresolved":false,"context_lines":[{"line_number":209,"context_line":"risky to implement limit management separately across services since the"},{"line_number":210,"context_line":"hierarchical nature of project namespaces in OpenStack can be complicated,"},{"line_number":211,"context_line":"forcing developers to solve the same hard problem over and over again. This"},{"line_number":212,"context_line":"design leaves consistency across OpenStack up to the developers from each"},{"line_number":213,"context_line":"project and hoping they all implement public APIs the same way. There is work"},{"line_number":214,"context_line":"underway to consolidate the management of limits to a single service, making it"},{"line_number":215,"context_line":"consumable to other services in the deployment while minimizing the risk of"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_2798a1be","line":212,"range":{"start_line":212,"start_character":7,"end_line":212,"end_character":63},"updated":"2019-03-08 12:43:21.000000000","message":"leaves consistency? consistency of what? \n\n\"leaves the consistency of limits across OpenStack...\"","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9a2ba991eae29aa78c636e2302bdad455861cd24","unresolved":false,"context_lines":[{"line_number":209,"context_line":"risky to implement limit management separately across services since the"},{"line_number":210,"context_line":"hierarchical nature of project namespaces in OpenStack can be complicated,"},{"line_number":211,"context_line":"forcing developers to solve the same hard problem over and over again. This"},{"line_number":212,"context_line":"design leaves consistency across OpenStack up to the developers from each"},{"line_number":213,"context_line":"project and hoping they all implement public APIs the same way. There is work"},{"line_number":214,"context_line":"underway to consolidate the management of limits to a single service, making it"},{"line_number":215,"context_line":"consumable to other services in the deployment while minimizing the risk of"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_6223f706","line":212,"range":{"start_line":212,"start_character":7,"end_line":212,"end_character":63},"in_reply_to":"5fc1f717_2798a1be","updated":"2019-03-08 14:18:19.000000000","message":"Done","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a3042dd75d026be5ffd8c70fa73fbdfc4581c94c","unresolved":false,"context_lines":[{"line_number":232,"context_line":"Consistent Interfaces"},{"line_number":233,"context_line":"~~~~~~~~~~~~~~~~~~~~~"},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"End users and operators benefit from a consistent interface. We reduce the"},{"line_number":236,"context_line":"ability for interfaces to develop differences by using a centralized, unified"},{"line_number":237,"context_line":"limit API. End users and operators expect the same experience regardless of the"},{"line_number":238,"context_line":"resource, or which service controls that resource. Ensuring consistency reduces"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_a7e9f11a","line":235,"updated":"2019-03-08 12:43:21.000000000","message":"Switched the POV. Rephrase to \"This reduces the ability for...\"","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9a2ba991eae29aa78c636e2302bdad455861cd24","unresolved":false,"context_lines":[{"line_number":232,"context_line":"Consistent Interfaces"},{"line_number":233,"context_line":"~~~~~~~~~~~~~~~~~~~~~"},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"End users and operators benefit from a consistent interface. We reduce the"},{"line_number":236,"context_line":"ability for interfaces to develop differences by using a centralized, unified"},{"line_number":237,"context_line":"limit API. End users and operators expect the same experience regardless of the"},{"line_number":238,"context_line":"resource, or which service controls that resource. Ensuring consistency reduces"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_c2798bfc","line":235,"in_reply_to":"5fc1f717_a7e9f11a","updated":"2019-03-08 14:18:19.000000000","message":"Done","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a3042dd75d026be5ffd8c70fa73fbdfc4581c94c","unresolved":false,"context_lines":[{"line_number":247,"context_line":"This flexibility is powerful for operators in modeling how available resources"},{"line_number":248,"context_line":"should, or should not, flow between projects. For example, a deployment"},{"line_number":249,"context_line":"interested in maximizing resource utilization may choose to let free resource"},{"line_number":250,"context_line":"flow between peer projects, allowing resources to move from stable projects to"},{"line_number":251,"context_line":"ones that are more resource-intensive."},{"line_number":252,"context_line":""},{"line_number":253,"context_line":"Reduced Complexity"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_27dd0170","line":250,"updated":"2019-03-08 12:43:21.000000000","message":"projects. This allows resources...*","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9a2ba991eae29aa78c636e2302bdad455861cd24","unresolved":false,"context_lines":[{"line_number":247,"context_line":"This flexibility is powerful for operators in modeling how available resources"},{"line_number":248,"context_line":"should, or should not, flow between projects. For example, a deployment"},{"line_number":249,"context_line":"interested in maximizing resource utilization may choose to let free resource"},{"line_number":250,"context_line":"flow between peer projects, allowing resources to move from stable projects to"},{"line_number":251,"context_line":"ones that are more resource-intensive."},{"line_number":252,"context_line":""},{"line_number":253,"context_line":"Reduced Complexity"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5fc1f717_221defbc","line":250,"in_reply_to":"5fc1f717_27dd0170","updated":"2019-03-08 14:18:19.000000000","message":"Done","commit_id":"acd8c84d65da2e6c04bc31e42a1084974e339ee8"}]}