Another Look at an OpenStack Heat Template2 May 2014
In an earlier post, I provided an introduction to OpenStack Heat, and provided an example Heat template that launched two instances with a logical network and a logical router. Here I am going to provide another view of a Heat template that does the same thing, but uses YAML and the HOT format instead of JSON and the CFN format.
Here’s the full template (click here if the code box below isn’t showing up):
I won’t walk through the whole template again, but rather just talk briefly about a couple of the differences between this YAML-encoded template and the earlier JSON-encoded template:
You’ll note the syntax is much simpler. JSON can trip you up on commas and such if you’re not careful; YAML is simpler and cleaner.
You’ll note the built-in functions are different, as I pointed out in my first Heat post. Instead of using
Refto refer to an object defined elsewhere in the template, HOT uses
Aside from these differences, you’ll note that the resource types and properties match between the two; this is because resource types are separate and independent from the template format.
Feel free to post any questions, corrections, or clarifications in the comments below. Thanks for reading!Tags: Automation · Interoperability · Linux · Networking · OSS · OpenStack · Virtualization Previous Post: An Introduction to OpenStack Heat Next Post: Technology Short Take #41