Go to file
Steve Baker b011cd466f Software config hook to provision using puppet
Deployment input values are mapped to facter variables by setting
FACTER_<input name> shell environment variables.
Manifests can write output values to $heat_outputs_path.{output_name}
These output values will be signalled back to heat, making these
values available to the stack, and placing that deployment resource in a
COMPLETE state.

The example template demonstrates deploying a single config with more
that one deployment resource, each with different input values.

Closes-Bug: #1279067

Change-Id: I28057eaa478b0a480f09604c177a72f3c45d7c53
2014-04-29 09:40:08 +12:00
2014-03-27 21:35:59 +01:00
2013-04-25 17:08:46 +00:00
2013-04-27 13:51:55 +01:00

Heat Templates

Heat is a service to orchestrate multiple composite cloud applications using templates

This repository provides:

  • Example templates which demonstrate core Heat functionality
  • Related image-building templates
  • Template-related scripts and conversion tools
Description
OpenStack Orchestration (Heat) Templates
Readme 5.2 MiB
Languages
PowerShell 79%
Shell 13.4%
Python 5.8%
Dockerfile 0.9%
JavaScript 0.5%
Other 0.4%