- Overview - What is the heat module?
- Module Description - What does the module do?
- Setup - The basics of getting started with heat
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Release notes for the project
- Repository - The project source code repository
The heat module is part of OpenStack, an effort by the OpenStack infrastructure team to provide 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.
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
puppet module install openstack/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':
default_transport_url => 'rabbit://heat:[email protected]:5672/heat',
database_connection => 'mysql+pymysql://heat:[email protected]/heat?charset=utf8',
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>
None
Developer documentation for the entire puppet-openstack project.