+1
This new proposal [1] looks like a very positive change on top of [2]. Simpler both to read and write.
One minor suggestion is to consider using a special character (eg $) rather than reserved keywords. As I understand it the keywords are only interpreted when they exactly match the value of a key in a map, so it is already unlikely to be problematic. However I think it would be more familiar and clear if we instead used the rule that any item (key or value) which _starts_ with a $ is interpreted specially. What those rules are is TBD but you could for instance write functions -- as either `$get_param('xxx')` or `$get_param: xxx` -- as well as allow accessing a parameter directly `$xxx `.
Very excited to see where this goes. Best Alex [1] https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config-WIP [2] https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config On 11/11/2013 16:57, Thomas Spatzier wrote:
Hi all, I have just posted the following wiki page to reflect a refined proposal for HOT software configuration based on discussions at the design summit last week. Angus also put a sample up in an etherpad last week, but we did not have enough time to go thru it in the design session. My write-up is based on Angus' sample, actually a refinement, and on discussions we had in breaks, plus it is trying to reflect all the good input from ML discussions and Steve Baker's initial proposal. https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config-WIP Please review and provide feedback. Regards, Thomas _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
