Ask Your Question

Question about nested Heat templates

asked 2014-09-22 12:04:19 -0500

mdoakes42 gravatar image

We have a requirement to create many different types of systems with different software and configuration requirements. (IE. On one server might have postgres and apache....on another postgres, and on another postgres and websphere). We have about 25 different types of software (postgres, apache, websphere, etc...) that we want to deploy in many different combinations.

I'm looking for a best practice in how to accomplish this. We are looking at the python-client for heat but open to API, command line or any other method. Essentially we would have a "base" template and then we would like to "add" software/configurations to the server.

As an example --create server --Add postgres --Add apache

--Create server --add postgres --add websphere

Rather then create and "hard-code" templates, is it possible to dynamically create the template or use "nested templates" so that essentially We would have a single template for each software piece --template for postgres --template for apache --template for websphere.

And we just import these into a "base" template depending on what we want to include.

Another option could be possibly a single "large" template with everything and use parameters to turn off|on the software component?

Would it also be best to use "puppet" for each of these software additions and what would be the best approach in doing this.

Essentially, I'm looking for a best practice in deploying software to VM's created via openstack with many different software components and configurations.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-09-23 22:51:35 -0500

Qiming gravatar image

It seems that you are combining multiple questions into a single post. Just some pointers I hope helpful for you:

  1. template resource, which can be used for abstracting your own template as resource types: Check Here
  2. software config and software deployment which can be used for in-instance configuration management.

  3. SoftwareConfig Doc

  4. SoftwareDeployment Doc

  5. Sample templates - make sure you read the READEME.rst files.

There are other projects such as Solum and Murano which may worth reading as well.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-09-22 12:04:19 -0500

Seen: 591 times

Last updated: Sep 23 '14