OpenStack Heat Puppet Module
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Takashi Kajinami 41c74eeed5 Rocky only: Remove TripleO Job 2 months ago
doc Follow the new PTI for document build 3 years ago
examples Move Heat to authtoken 5 years ago
lib/puppet Add type/provider for paste configs 6 years ago
manifests Improve restarting Apache 3 years ago
releasenotes Merge "Deprecate parameter heat_watch_server_url" 3 years ago
spec modulesync: sync and add nodepool-bionic for beaker 3 years ago
.gitignore Update .gitignore 3 years ago
.gitreview OpenDev Migration Patch 2 years ago
.zuul.yaml Rocky only: Remove TripleO Job 2 months ago Release 8.0.0 5 years ago
Gemfile Update Gemfile for stable/rocky 3 years ago
LICENSE Update LICENSE 3 years ago Remove the unnecessary _ 3 years ago
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 6 years ago
bindep.txt modulesync: sync and add nodepool-bionic for beaker 3 years ago
metadata.json Release 13.3.1 3 years ago
setup.cfg Update URLs in documents according to document migration 4 years ago Add basic structure for ReNo 5 years ago
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/rocky 3 years ago

Team and repository tags

Team and repository tags


Table of Contents

  1. Overview - What is the heat module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with heat
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Contributors - Those with commits


The heat module is part of OpenStack, an effort by the OpenStack infrastructure team to provice continuous integration testing and code review for OpenStack and OpenStack community projects as part of the core software. The module itself is used to flexibly configure and manage the orchestration service for OpenStack.

Module Description

The heat module is an attempt to make Puppet capable of managing the entirety of heat.


What the heat module affects

  • Heat, the orchestration service for OpenStack

Installing heat

puppet module install openstack/heat

Beginning with heat

To utilize the heat module's functionality you will need to declare multiple resources. The following is a modified excerpt from the openstack module. This is not an exhaustive list of all the components needed. We recommend that you consult and understand the openstack module and the core openstack documentation to assist you in understanding the available deployment options.

# enable heat resources
class { '::heat':
  rabbit_userid       => 'heat',
  rabbit_password     => 'an_even_bigger_secret',
  rabbit_host         => '',
  database_connection => 'mysql+pymysql://heat:a_big_secret@',
  identity_uri        => '',
  keystone_password   => 'a_big_secret',

class { '::heat::api': }

class { '::heat::engine':
  auth_encryption_key => '1234567890AZERTYUIOPMLKJHGFDSQ12',

class { '::heat::api_cfn': }



heat is a combination of Puppet manifests and Ruby code to deliver configuration and extra functionality through types and providers.



The heat_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/heat/heat.conf file.

heat_config { 'DEFAULT/enable_stack_adopt' :
  value => True,

This will write enable_stack_adopt=True in the [DEFAULT] section.


Section/setting name to manage from heat.conf


The value of the setting to be defined.


Whether to hide the value from Puppet logs. Defaults to false.


If value is equal to ensure_absent_val then the resource will behave as if ensure => absent was specified. Defaults to <SERVICE DEFAULT>




This module has beaker-rspec tests

To run:

bundle install
bundle exec rspec spec/acceptance


Developer documentation for the entire puppet-openstack project.


Release Notes