)]}'
{"doc/source/template_guide/environment.rst":[{"author":{"_account_id":4328,"name":"Steven Hardy","email":"steven.hardy@suse.com","username":"shardy"},"change_message_id":"83bd8f28e719b31076e3fd2694d1be040a84ce2f","unresolved":false,"context_lines":[{"line_number":58,"context_line":"engine starts up, which is the time when these files are read.  The"},{"line_number":59,"context_line":"other way for a provider to extend the global environment is through"},{"line_number":60,"context_line":"heat engine plugins that define \"available_resource\" and/or"},{"line_number":61,"context_line":"\"constraint\" mappings."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"If the \"my_env.yaml\" file from the example above had been put in the"},{"line_number":64,"context_line":"\"environment_dir\" then the user\u0027s command line could be this:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"AAAAWH%2F96Mk%3D","line":61,"updated":"2014-04-01 09:10:17.000000000","message":"I don\u0027t believe the bit about available_resource or constraint mappings belongs here - that is part of the python plugin API, not really anything to do with the environment concept, so IMO we should probably document that separately to avoid confusion between the two separate (but related) interfaces.\n\nWe currently have a wiki guide on the plugin interface functionality, but probably need that refactoring into the official docs. Randall started that, but it needs completing - perhaps you can work with him to get that patch revived?\n\nhttps://review.openstack.org/#/c/43962/\n\nhttps://wiki.openstack.org/wiki/Heat/Plugins","commit_id":"7f6243f1719e53ccfd8b43e2351a7beb4c6e5640"},{"author":{"_account_id":8328,"name":"Mike Spreitzer","email":"mspreitz@us.ibm.com","username":"mspreitz"},"change_message_id":"8cf3103eb8f5f800ba8cde62c11f853ac14f9fe3","unresolved":false,"context_lines":[{"line_number":58,"context_line":"engine starts up, which is the time when these files are read.  The"},{"line_number":59,"context_line":"other way for a provider to extend the global environment is through"},{"line_number":60,"context_line":"heat engine plugins that define \"available_resource\" and/or"},{"line_number":61,"context_line":"\"constraint\" mappings."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"If the \"my_env.yaml\" file from the example above had been put in the"},{"line_number":64,"context_line":"\"environment_dir\" then the user\u0027s command line could be this:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"AAAAWH%2F9Ugo%3D","line":61,"in_reply_to":"AAAAWH%2F96Mk%3D","updated":"2014-04-07 05:22:59.000000000","message":"Yes, I\u0027ll be happy to work with Randall on reviving that patch.\n\nGood point, the plug-in feature is not the same as the environment feature.  They both affect the interpretation of templates, and so both should get some mention somewhere in the template-guide.  Since plugins are not an environment issue, we need some other place in the Template Guide to mention them.  Where would you recommend?\n\nI imagine that what the end-users need to know about resource plugins is something along the following lines.  The provider might have made additional resource types available beyond those documented here.  Heat\u0027s resource-type-list operation will reveal them, and the resource-type-show and resource-template operations expose a given resource type\u0027s formal description.  The cloud provider is the source to ask for additional information about a resource type that is not documented here.","commit_id":"7f6243f1719e53ccfd8b43e2351a7beb4c6e5640"},{"author":{"_account_id":4328,"name":"Steven Hardy","email":"steven.hardy@suse.com","username":"shardy"},"change_message_id":"dcb861ff6f7cc40b1e99d19c4c8496ca2aec8ccf","unresolved":false,"context_lines":[{"line_number":58,"context_line":"engine starts up, which is the time when these files are read.  The"},{"line_number":59,"context_line":"other way for a provider to extend the global environment is through"},{"line_number":60,"context_line":"heat engine plugins that define \"available_resource\" and/or"},{"line_number":61,"context_line":"\"constraint\" mappings."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"If the \"my_env.yaml\" file from the example above had been put in the"},{"line_number":64,"context_line":"\"environment_dir\" then the user\u0027s command line could be this:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"AAAAW3%2F%2F68o%3D","line":61,"in_reply_to":"AAAAWH%2F9Ugo%3D","updated":"2014-04-09 13:34:49.000000000","message":"I think we need a top-level section called \"Available Resource Types\" or something, which explains that the available resources can be viewed via heat resource-type-list, that the content of the list is determined by a combination of the resource plugins and cloud-provider/global environment (linking here).  \n\nIt can also mention, as you have in patchset 2, that types may be made available by cloud providers which are not documented in this guide, and probably also that the interface schema for all resources is available via resource-type-show.","commit_id":"7f6243f1719e53ccfd8b43e2351a7beb4c6e5640"},{"author":{"_account_id":4328,"name":"Steven Hardy","email":"steven.hardy@suse.com","username":"shardy"},"change_message_id":"9f34f5289160471149e960f6198f3ae8f83c90ab","unresolved":false,"context_lines":[{"line_number":22,"context_line":"implementation and the parameters passed to Heat."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"To fully understand the runtime behavior you also have to consider"},{"line_number":25,"context_line":"what plug-ins the cloud provider has installed."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"------"},{"line_number":28,"context_line":"Format"}],"source_content_type":"text/x-rst","patch_set":2,"id":"AAAAW3%2F%2F660%3D","line":25,"updated":"2014-04-09 13:39:27.000000000","message":"As mentioned in my comment in patchset 1, I think we need a top-level section which describes how to get the list of available resources, the interface schema, and a (very brief) summary of how the types are defined.\n\nI won\u0027t object to this patch, but perhaps we can consider moving this sentence when such a top-level section is implemented?  IMO, similar to my earlier comment, talking about resource plugins here is just confusing, hence the need for a top-level overview section.","commit_id":"c9bfbbc2235ceee0509fa9a926f7285ad51ef3f1"},{"author":{"_account_id":8328,"name":"Mike Spreitzer","email":"mspreitz@us.ibm.com","username":"mspreitz"},"change_message_id":"54efad9aef4c80a6e167ebf0435ab89b4188d674","unresolved":false,"context_lines":[{"line_number":22,"context_line":"implementation and the parameters passed to Heat."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"To fully understand the runtime behavior you also have to consider"},{"line_number":25,"context_line":"what plug-ins the cloud provider has installed."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"------"},{"line_number":28,"context_line":"Format"}],"source_content_type":"text/x-rst","patch_set":2,"id":"AAAAW3%2F%2F1ew%3D","line":25,"in_reply_to":"AAAAW3%2F%2F660%3D","updated":"2014-04-10 03:27:31.000000000","message":"Ah, I missed your second comment on the 1st patch set.  Yes, that sounds like a good idea to me.","commit_id":"c9bfbbc2235ceee0509fa9a926f7285ad51ef3f1"},{"author":{"_account_id":4328,"name":"Steven Hardy","email":"steven.hardy@suse.com","username":"shardy"},"change_message_id":"9f34f5289160471149e960f6198f3ae8f83c90ab","unresolved":false,"context_lines":[{"line_number":58,"context_line":"the \"[DEFAULT]\" section) of \"/etc/heat/heat.conf\".  The default for"},{"line_number":59,"context_line":"that directory is \"/etc/heat/environment.d\".  Its contents are"},{"line_number":60,"context_line":"combined in whatever order the shell delivers them when the heat"},{"line_number":61,"context_line":"engine starts up, which is the time when these files are read."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"If the \"my_env.yaml\" file from the example above had been put in the"},{"line_number":64,"context_line":"\"environment_dir\" then the user\u0027s command line could be this:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"AAAAW3%2F%2F66E%3D","line":61,"updated":"2014-04-09 13:39:27.000000000","message":"It is a little odd that we have such detail specific to deployers (users can\u0027t see any of these files) here, but I guess here is Ok until we have a deployment guide and can separate the user and deployer orientated docs.","commit_id":"c9bfbbc2235ceee0509fa9a926f7285ad51ef3f1"},{"author":{"_account_id":8328,"name":"Mike Spreitzer","email":"mspreitz@us.ibm.com","username":"mspreitz"},"change_message_id":"55727bd9004a77147fba4a73fbfc1b077669ee34","unresolved":false,"context_lines":[{"line_number":58,"context_line":"the \"[DEFAULT]\" section) of \"/etc/heat/heat.conf\".  The default for"},{"line_number":59,"context_line":"that directory is \"/etc/heat/environment.d\".  Its contents are"},{"line_number":60,"context_line":"combined in whatever order the shell delivers them when the heat"},{"line_number":61,"context_line":"engine starts up, which is the time when these files are read."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"If the \"my_env.yaml\" file from the example above had been put in the"},{"line_number":64,"context_line":"\"environment_dir\" then the user\u0027s command line could be this:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"AAAAW3%2F%2Fx0Y%3D","line":61,"in_reply_to":"AAAAW3%2F%2F0V0%3D","updated":"2014-04-10 13:27:03.000000000","message":"I agree on the overall re-org.  It should start with generalities, and include something about CFN in parallel with something about HOT; the HOT should come first; the section about CFN needs to say little more than \"see Amazon\u0027s doc, Heat supports only a subset, see the supported resource types listed below, each has notes on which AWS properties are not supported\".","commit_id":"c9bfbbc2235ceee0509fa9a926f7285ad51ef3f1"},{"author":{"_account_id":4328,"name":"Steven Hardy","email":"steven.hardy@suse.com","username":"shardy"},"change_message_id":"453351811d2e8cd5e161e565ef792e02b67e4e02","unresolved":false,"context_lines":[{"line_number":58,"context_line":"the \"[DEFAULT]\" section) of \"/etc/heat/heat.conf\".  The default for"},{"line_number":59,"context_line":"that directory is \"/etc/heat/environment.d\".  Its contents are"},{"line_number":60,"context_line":"combined in whatever order the shell delivers them when the heat"},{"line_number":61,"context_line":"engine starts up, which is the time when these files are read."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"If the \"my_env.yaml\" file from the example above had been put in the"},{"line_number":64,"context_line":"\"environment_dir\" then the user\u0027s command line could be this:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"AAAAW3%2F%2FyA4%3D","line":61,"in_reply_to":"AAAAW3%2F%2F0V0%3D","updated":"2014-04-10 13:07:35.000000000","message":"Thomas: +1, sounds like a good idea","commit_id":"c9bfbbc2235ceee0509fa9a926f7285ad51ef3f1"},{"author":{"_account_id":7193,"name":"Thomas Spatzier","email":"thomas.spatzier@icloud.com","username":"thomasspatzier"},"change_message_id":"3e29a4db4aa25b119d9b75b9891e945a0a1ec299","unresolved":false,"context_lines":[{"line_number":58,"context_line":"the \"[DEFAULT]\" section) of \"/etc/heat/heat.conf\".  The default for"},{"line_number":59,"context_line":"that directory is \"/etc/heat/environment.d\".  Its contents are"},{"line_number":60,"context_line":"combined in whatever order the shell delivers them when the heat"},{"line_number":61,"context_line":"engine starts up, which is the time when these files are read."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"If the \"my_env.yaml\" file from the example above had been put in the"},{"line_number":64,"context_line":"\"environment_dir\" then the user\u0027s command line could be this:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"AAAAW3%2F%2F0V0%3D","line":61,"in_reply_to":"AAAAW3%2F%2F1fY%3D","updated":"2014-04-10 08:09:53.000000000","message":"I think the overall Template Guide structure needs some enhancement in general. Currently, when you look at it the user gets swamped with a long list of resources types, CFN functions and then at the very bottom you find the HOT template guide.\n\nIf we want to promote HOT as the preferred language starting from Icehouse (that\u0027s what I read in the release notes draft during the IRC meeting on Wednesday), we should change this structure. I\u0027m happy to give it a try if there are objections.","commit_id":"c9bfbbc2235ceee0509fa9a926f7285ad51ef3f1"},{"author":{"_account_id":8328,"name":"Mike Spreitzer","email":"mspreitz@us.ibm.com","username":"mspreitz"},"change_message_id":"54efad9aef4c80a6e167ebf0435ab89b4188d674","unresolved":false,"context_lines":[{"line_number":58,"context_line":"the \"[DEFAULT]\" section) of \"/etc/heat/heat.conf\".  The default for"},{"line_number":59,"context_line":"that directory is \"/etc/heat/environment.d\".  Its contents are"},{"line_number":60,"context_line":"combined in whatever order the shell delivers them when the heat"},{"line_number":61,"context_line":"engine starts up, which is the time when these files are read."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"If the \"my_env.yaml\" file from the example above had been put in the"},{"line_number":64,"context_line":"\"environment_dir\" then the user\u0027s command line could be this:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"AAAAW3%2F%2F1fY%3D","line":61,"in_reply_to":"AAAAW3%2F%2F66E%3D","updated":"2014-04-10 03:27:31.000000000","message":"Right.  At the moment the Template Guide appears as part of the Python developer documentation, and also carries the weight of informing cloud providers and users as well as developers.","commit_id":"c9bfbbc2235ceee0509fa9a926f7285ad51ef3f1"}]}