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.
Emilien Macchi 9567116722 release: prepare 7.0.0 (liberty) 3 years ago
examples Add Puppet 4.x lint checks 4 years ago
lib/puppet Reflect provider change in puppet-openstacklib 3 years ago
manifests Merge "Add rabbit_ha_queues option" 3 years ago
spec release: prepare 7.0.0 (liberty) 3 years ago
.gitignore Try to use zuul-cloner to prepare fixtures 3 years ago
.gitreview Update .gitreview file for project rename 4 years ago
CHANGELOG.md release: prepare 7.0.0 (liberty) 3 years ago
Gemfile Try to use zuul-cloner to prepare fixtures 3 years ago
LICENSE Synchronize LICENSE file with OpenStack projects 4 years ago
README.md release: prepare 7.0.0 (liberty) 3 years ago
Rakefile release: prepare 7.0.0 (liberty) 3 years ago
metadata.json release: prepare 7.0.0 (liberty) 3 years ago

README.md

puppet-heat

7.0.0 - 2015.2 - Liberty

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

Overview

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.

Setup

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         => '127.0.0.1',
  database_connection => 'mysql://heat:a_big_secret@127.0.0.1/heat?charset=utf8',
  identity_uri        => 'http://127.0.0.1:35357/',
  keystone_password   => 'a_big_secret',
}

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

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

class { '::heat::api_cloudwatch': }

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

Implementation

puppet-heat

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

Types

heat_config

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/verbose' :
  value => true,
}

This will write verbose=true in the [DEFAULT] section.

name

Section/setting name to manage from heat.conf

value

The value of the setting to be defined.

secret

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

ensure_absent_val

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

Limitations

None

Beaker-Rspec

This module has beaker-rspec tests

To run:

shell bundle install bundle exec rspec spec/acceptance

Development

Developer documentation for the entire puppet-openstack project.

Contributors