)]}'
{"reference/programs.yaml":[{"author":{"_account_id":8328,"name":"Mike Spreitzer","email":"mspreitz@us.ibm.com","username":"mspreitz"},"change_message_id":"d8db25fdbc848cf3a850ef712b2f782a81dd272e","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1abeadc6_38d99df3","line":115,"updated":"2014-08-28 05:17:28.000000000","message":"This should be clarified to say that the infrastructure in question is virtual infrastructure created by OpenStack, not the underlying infrastructure on which OpenStack runs.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":3098,"name":"Jeff Peeler","email":"jpeeler@redhat.com","username":"jpeeler-z"},"change_message_id":"22cae3f37e35b910ec1fc96420d772f330e6003a","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1abeadc6_d3705ea6","line":115,"updated":"2014-08-28 21:38:56.000000000","message":"With all this talk of overscoping, can\u0027t the \"and applications\" just be removed?","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":7193,"name":"Thomas Spatzier","email":"thomas.spatzier@icloud.com","username":"thomasspatzier"},"change_message_id":"6fd3ee5f689ab47710d77c2f20f82f0e7bd37e99","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_95ff1f01","line":115,"in_reply_to":"1abeadc6_4252b935","updated":"2014-09-01 13:35:46.000000000","message":"Hm, with software config that we added in Icehouse, we actually took a step towards apps, and even the most famous example template (WordPress) is an app rather than just its infrastructure.\n\nWould a slight tweak like \"infrastructure for applications\" (i.e. \u0027for\u0027 instead of \u0027and\u0027) make sense? I.e. users are not building infrastructure just for the fun of it ...\n\nThat would not totally exclude applications, so gives us some freedom. And the line between infra and apps is blurred; some will call a software component part of the application, others will call it infrastructure for an application, depending on who you talk to.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":4715,"name":"Angus Salkeld","email":"asalkeld@redhat.com","username":"asalkeld"},"change_message_id":"24fa743bd9590073e8c7b262b01dc2f894f6f82c","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1abeadc6_4252b935","line":115,"in_reply_to":"1abeadc6_d3705ea6","updated":"2014-08-28 23:28:01.000000000","message":"+1 Jeff, just drop apps for now.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"47c71c9e50ec06ac6d657e4fb5fb8c76e88cd909","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_f2d9e4f3","line":115,"in_reply_to":"fa98f980_10502b0a","updated":"2014-09-03 18:06:31.000000000","message":"@MikeS\u0027 use of \"model-driven management\" has a good feel. Here\u0027s an attempt to use it as well:\n\n\"To create a human- and machine-accessible service that gracefully integrates with other technologies to support model-driven management of OpenStack resources and the applications they deliver.\"","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":8328,"name":"Mike Spreitzer","email":"mspreitz@us.ibm.com","username":"mspreitz"},"change_message_id":"bab9c1719714cf2966d02619dafe3650fb6d2f71","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_10502b0a","line":115,"in_reply_to":"fa98f980_2a8141fb","updated":"2014-09-03 14:07:49.000000000","message":"The word \"topology\" has different meanings in different contexts.  A mathematician would be very confused by the suggested mission statement.  Even within the restricted domain of computing, there are several existing systems in which \"topology\" is a technical term that is specific to that system.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"eeca27910ba3e1cb236515adb4d0bf8799ef63c8","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_52fe7e6c","line":115,"in_reply_to":"fa98f980_4c442574","updated":"2014-09-09 20:58:32.000000000","message":"I didn\u0027t realize how much of a differentiator that was for us. I\u0027ll drop it back in. \n\n\"To create a human- and machine-accessible service that gracefully integrates with other technologies to support model-driven management of OpenStack resources and the applications they deliver.\"","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"805d30b0a80a1c7ae9556ace4d06d3ed56e24727","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_9d57af25","line":115,"in_reply_to":"fa98f980_538e21d1","updated":"2014-09-04 12:40:17.000000000","message":"\"ultimately ... every OpenStack integrated project changes the way folks interact with their infrastructure, and exposes an API which enables direct and indirect user interaction.\" - @shardy\n\nGood point, maybe we can drop \"human- and machine-accessible\" since it\u0027s common to all OpenStack services.\n\n\"To create a service that gracefully integrates with other technologies to support model-driven management of OpenStack resources and the applications they deliver.\"","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"8b74d38e4b6a3902dd5f0465da0ce33f7eb0bb7b","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_2a8141fb","line":115,"in_reply_to":"fa98f980_6e69088b","updated":"2014-09-03 12:11:24.000000000","message":"It would be more appropriate even if we define like this:\n\nTo manage the lifecycle of Topology made with openstack infrastructure resources and applications artifacts.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":4328,"name":"Steven Hardy","email":"steven.hardy@suse.com","username":"shardy"},"change_message_id":"4f3ea7c8a1eab5de4ef2f62d4e09effbb0ba7515","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_538e21d1","line":115,"in_reply_to":"fa98f980_81bcb2dd","updated":"2014-09-04 08:20:05.000000000","message":"@Ryan: +1, that sounds good to me.  \n\nFWIW I don\u0027t have any problem with the service part - I know Zane said that\u0027s not our mission, but ultimately, in practice, it actually is - every OpenStack integrated project changes the way folks interact with their infrastructure, and all of them expose an API which enables direct and indirect user interaction.  \n\nTherefore explicit acknowledgement that we\u0027re working to provide a service which does a thing, consistent with and well-integrated with other OpenStack services does no harm IMO, and possibly provides clarification that we\u0027re not primarily aiming to provide e.g libraries which do a thing like oslo or whatever.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":8328,"name":"Mike Spreitzer","email":"mspreitz@us.ibm.com","username":"mspreitz"},"change_message_id":"9bbe417ecad6dd9f7d35914d6cdd8a91ef9af7a6","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_6e69088b","line":115,"in_reply_to":"fa98f980_95ff1f01","updated":"2014-09-01 14:25:41.000000000","message":"I agree that we have a concern with helping users manage their applications as well as their virtual infrastructure.  However, just to make things even blurrier, I think our main concern is graceful integration with other software-management technologies like puppet, chef, and bash; we do not really have a desire to re-invent those wheels.\n\nFollowing is a rewording that attempts to take all the above into consideration.\n\nTo support model-driven management of virtual infrastructure and the applications delivered on it, including graceful integration with other technologies for managing applications.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"bb5f475cbda3707904a2a3de9c9c7abc06ebd06c","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_dec35f36","line":115,"in_reply_to":"fa98f980_9d57af25","updated":"2014-09-09 18:29:49.000000000","message":"The \u0027human- and machine-readable\" part was introduced as a reaction to the fact that other model-driven management tools (*cough*TOSCA*cough*) were designed to be purely machine-readable. The fact that _people_ can actually write templates is a big part of our mission. I really like where this is heading, though.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":7193,"name":"Thomas Spatzier","email":"thomas.spatzier@icloud.com","username":"thomasspatzier"},"change_message_id":"8c5e97d3410ca30f5c12126fe950a14abe2f9580","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_4c442574","line":115,"in_reply_to":"fa98f980_dec35f36","updated":"2014-09-09 19:56:40.000000000","message":"Ha, we are working on the issues in TOSCA, Zane ;-)\n\nBut seriously: I agree that the \u0027human- and machine-readable\u0027 part makes sense.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":7193,"name":"Thomas Spatzier","email":"thomas.spatzier@icloud.com","username":"thomasspatzier"},"change_message_id":"123477981f9477e5550a57592eb96e540bb5f1d6","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_81bcb2dd","line":115,"in_reply_to":"fa98f980_f2d9e4f3","updated":"2014-09-04 07:01:47.000000000","message":"@Ryan: I like your proposal.","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"},{"author":{"_account_id":8328,"name":"Mike Spreitzer","email":"mspreitz@us.ibm.com","username":"mspreitz"},"change_message_id":"fbc091002ab236d49b48e686e0092c92d630688a","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  codename: Heat"},{"line_number":113,"context_line":"  mission: \u003e"},{"line_number":114,"context_line":"    To create a human- and machine-accessible service for managing the entire"},{"line_number":115,"context_line":"    lifecycle of infrastructure and applications within OpenStack clouds."},{"line_number":116,"context_line":"  ptl: Zane Bitter (zaneb)"},{"line_number":117,"context_line":"  url: https://wiki.openstack.org/wiki/Heat"},{"line_number":118,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa98f980_2db4ed33","line":115,"in_reply_to":"fa98f980_f2d9e4f3","updated":"2014-09-03 18:15:34.000000000","message":"I deliberately avoided the \"create a service\" part because of Zane\u0027s first comment (up in the comments section, not here in line).","commit_id":"033d2f9a7799cdddacae450d56c8d9c2b577c755"}]}