)]}'
{"resolutions/20170320-resolution-platform-applications.rst":[{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"3907747623a8f5b13f118d172acdf30862f395e9","unresolved":false,"context_lines":[{"line_number":10,"context_line":"  To produce a ubiquitous Open Source Cloud Computing platform that is"},{"line_number":11,"context_line":"  easy to use, simple to implement, interoperable between deployments,"},{"line_number":12,"context_line":"  works well at all scales, and meets the needs of users and operators"},{"line_number":13,"context_line":"  of both public and private clouds."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The special needs of platform (PaaS) applications"},{"line_number":16,"context_line":"-------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_8a8e0b2c","line":13,"updated":"2017-03-22 14:12:41.000000000","message":"DRY: I would avoid quoting as the mission wording may change in the future. Point to https://governance.openstack.org/tc/reference/charter.html instead ?","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"4ee52da5d8278c80a8316526fcd262903ab31c8a","unresolved":false,"context_lines":[{"line_number":15,"context_line":"The special needs of platform (PaaS) applications"},{"line_number":16,"context_line":"-------------------------------------------------"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"OpenStack aims to acheive its mission by providing an open source"},{"line_number":19,"context_line":"implementation of an openly designed and implemented API which allows"},{"line_number":20,"context_line":"users to provision and manage a variety of compute, storage and"},{"line_number":21,"context_line":"networking resource. We refer to these core services as the OpenStack"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_b0dc68e5","line":18,"updated":"2017-03-20 23:07:51.000000000","message":"achieve","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"744c11c40fdbc9727e1646c033a596db8964498e","unresolved":false,"context_lines":[{"line_number":15,"context_line":"The special needs of platform (PaaS) applications"},{"line_number":16,"context_line":"-------------------------------------------------"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"OpenStack aims to acheive its mission by providing an open source"},{"line_number":19,"context_line":"implementation of an openly designed and implemented API which allows"},{"line_number":20,"context_line":"users to provision and manage a variety of compute, storage and"},{"line_number":21,"context_line":"networking resource. We refer to these core services as the OpenStack"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_5b2a757f","line":18,"in_reply_to":"1a1ced50_b0dc68e5","updated":"2017-03-20 23:10:53.000000000","message":"thx, will fix.","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":2506,"name":"devdatta-kulkarni","email":"kulkarni.devdatta@gmail.com","username":"devdatta-kulkarni"},"change_message_id":"be88ce9399d669777e4e1e279f4f1d82f1b3a7ca","unresolved":false,"context_lines":[{"line_number":30,"context_line":"lock-in."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Another class of applications on the OpenStack cloud are PaaS"},{"line_number":33,"context_line":"applications that building on the core compute, storage and networking"},{"line_number":34,"context_line":"components, and provide higher level services which in turn expose"},{"line_number":35,"context_line":"open API\u0027s. Several OpenStack projects themselves are PaaS"},{"line_number":36,"context_line":"applications; Designate, Manila, Octavia, Sahara, Trove, and Sahara are"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_14c35039","line":33,"updated":"2017-03-21 14:39:13.000000000","message":"build","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":2506,"name":"devdatta-kulkarni","email":"kulkarni.devdatta@gmail.com","username":"devdatta-kulkarni"},"change_message_id":"be88ce9399d669777e4e1e279f4f1d82f1b3a7ca","unresolved":false,"context_lines":[{"line_number":33,"context_line":"applications that building on the core compute, storage and networking"},{"line_number":34,"context_line":"components, and provide higher level services which in turn expose"},{"line_number":35,"context_line":"open API\u0027s. Several OpenStack projects themselves are PaaS"},{"line_number":36,"context_line":"applications; Designate, Manila, Octavia, Sahara, Trove, and Sahara are"},{"line_number":37,"context_line":"some examples of these projects."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Cloud native applications and PaaS applications have different"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_f4f79488","line":36,"updated":"2017-03-21 14:39:13.000000000","message":"Sahara repeated.\n\nOne more is Solum.","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"3907747623a8f5b13f118d172acdf30862f395e9","unresolved":false,"context_lines":[{"line_number":33,"context_line":"applications that building on the core compute, storage and networking"},{"line_number":34,"context_line":"components, and provide higher level services which in turn expose"},{"line_number":35,"context_line":"open API\u0027s. Several OpenStack projects themselves are PaaS"},{"line_number":36,"context_line":"applications; Designate, Manila, Octavia, Sahara, Trove, and Sahara are"},{"line_number":37,"context_line":"some examples of these projects."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Cloud native applications and PaaS applications have different"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_ea05bf45","line":36,"in_reply_to":"1a1ced50_cedbe44d","updated":"2017-03-22 14:12:41.000000000","message":"Agreed, Designate is much more low-level. I\u0027d argue that Octavia is also base infrastructure rather than PaaS. Freezer, however, is missing. Any reason why you don\u0027t mention Magnum, Murano, Zun and Mistral ? Those are all PaaS-like.","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"1dc37335ca2fa150cf1147d95a4fe12299d39607","unresolved":false,"context_lines":[{"line_number":33,"context_line":"applications that building on the core compute, storage and networking"},{"line_number":34,"context_line":"components, and provide higher level services which in turn expose"},{"line_number":35,"context_line":"open API\u0027s. Several OpenStack projects themselves are PaaS"},{"line_number":36,"context_line":"applications; Designate, Manila, Octavia, Sahara, Trove, and Sahara are"},{"line_number":37,"context_line":"some examples of these projects."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Cloud native applications and PaaS applications have different"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_cedbe44d","line":36,"in_reply_to":"1a1ced50_f4f79488","updated":"2017-03-21 16:04:13.000000000","message":"Just to be difficult, I would say that designate is a lower level service, that is used by other services, and users.\n\nDesignate works quite well all on its own :)\n\nTraditionally, Designate has been deployed as a service in the cloud, but that is more to do with a couple of vendors internal team structures than a technical reason.","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"4ee52da5d8278c80a8316526fcd262903ab31c8a","unresolved":false,"context_lines":[{"line_number":66,"context_line":"special requirements of PaaS applications, and further recognize the"},{"line_number":67,"context_line":"importance of prioritizing those capabilities for delivery. It is only"},{"line_number":68,"context_line":"through this process that OpenStack, as a whole, will be able to"},{"line_number":69,"context_line":"deliver on its stated mission."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Furthermore, the Technical Committee recommends that all PaaS"},{"line_number":72,"context_line":"application projects that need specific capabilities of the underlying"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_504ed496","line":69,"updated":"2017-03-20 23:07:51.000000000","message":"This is tricky. Presumably all the projects are already obliged, simply by existing as projects, to recognize all users and use cases. Is what\u0027s really being requested here is to redress historical failings to address these problems and to adjust to give feature requirements from with the openstack community some kind of pass to a greater level of attention?\n\nThat sounds weird. It suggests there is a bush here which is being beaten around and not addressed directly.","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"744c11c40fdbc9727e1646c033a596db8964498e","unresolved":false,"context_lines":[{"line_number":66,"context_line":"special requirements of PaaS applications, and further recognize the"},{"line_number":67,"context_line":"importance of prioritizing those capabilities for delivery. It is only"},{"line_number":68,"context_line":"through this process that OpenStack, as a whole, will be able to"},{"line_number":69,"context_line":"deliver on its stated mission."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Furthermore, the Technical Committee recommends that all PaaS"},{"line_number":72,"context_line":"application projects that need specific capabilities of the underlying"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_1b1abd6e","line":69,"in_reply_to":"1a1ced50_504ed496","updated":"2017-03-20 23:10:53.000000000","message":"Thanks Chris. I don\u0027t think I\u0027m trying to beat around a bush, rather word the resolution in a way that is consistent with the TC\u0027s view that it is an advisory body that will not stipulate specific actions by projects, and that projects have the autonomy to do what they think is best.\n\nAt least, that is the intent. Whether this verbiage achieves that or not, I am not sure.","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"},{"author":{"_account_id":2506,"name":"devdatta-kulkarni","email":"kulkarni.devdatta@gmail.com","username":"devdatta-kulkarni"},"change_message_id":"be88ce9399d669777e4e1e279f4f1d82f1b3a7ca","unresolved":false,"context_lines":[{"line_number":71,"context_line":"Furthermore, the Technical Committee recommends that all PaaS"},{"line_number":72,"context_line":"application projects that need specific capabilities of the underlying"},{"line_number":73,"context_line":"Infrastructure Services identify these requirements and reference this"},{"line_number":74,"context_line":"resolution of the Technical Committee in their requests."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a1ced50_b4d43cbd","line":74,"updated":"2017-03-21 14:39:13.000000000","message":"+1\n\nHow might such requirements be tracked? We might need some kind of a cross-project artifact to track this probably.","commit_id":"9731abd94433d90b22513ac333382e68a9f4513e"}]}