Forge Home

heat

Puppet module for OpenStack Heat

14,469 downloads

9,430 latest version

3.1 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 5.2.0 (latest)
  • 5.1.0
  • 5.0.0
released Oct 2nd 2015
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet 3.x
  • , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'stackforge-heat', '5.2.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add stackforge-heat
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install stackforge-heat --version 5.2.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

stackforge/heat — version 5.2.0 Oct 2nd 2015

puppet-heat

5.2.0 - 2014.2 - Juno

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
  8. Release Notes - Notes on the most recent updates to the module

Overview

The heat module is part of Stackforge, an effort by the OpenStack infrastructure team to provice continuous integration testing and code review for OpenStack and OpenStack community projects not 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

example% puppet module install puppetlabs/heat

Beginning with heat

Implementation

puppet-heat

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

Limitations

None

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

5.2.0

  • Add an ability to manage use_stderr parameter
  • Remove deprecated parameter stack_user_domain

5.1.0

  • Switch to TLSv1
  • spec: pin rspec-puppet to 1.0.1
  • Implement Keystone domain creation
  • Run dbsync when engine is upgraded
  • db: Added postgresql backend using openstacklib helper
  • Rework delegated roles
  • Pin puppetlabs-concat to 1.2.1 in fixtures
  • change default MySQL collate to utf8_general_ci
  • added option to configure flavor in heat.conf
  • Fix ipv6 support
  • Update .gitreview file for project rename

5.0.0

  • Stable Juno release
  • Added heat::policy to control policy.json
  • Deprecated the sql_connection parameter for database_connection parameter
  • Adds parameters to configure deferred authentication method in heat::engine in accordance with new Juno defaults
  • Bumped stdlib dependency to >=4.0.0
  • Added parameters to control whether to configure users
  • Added manage_service parameters to various classes to control whether the service was managed, as well as added enabled parameters where not already present
  • Added the ability to override the keystone service name in keystone::auth
  • Migrated the heat::db::mysql class to use openstacklib::db::mysql and deprecated the mysql_module parameter

4.2.0

  • Added ability to hide secret type parameters from logs
  • Fixed database resource relationships
  • Added class for extended logging options
  • Fixed ssl parameter requirements when using kombu and rabbit

4.1.0

  • Added SSL endpoint support.

4.0.0

  • Stable Icehouse release.
  • Added SSL parameter for RabbitMQ.
  • Added support for puppetlabs-mysql 2.2 and greater.
  • Added option to define RabbitMQ queues as durable.
  • Fixed outdated DB connection parameter.
  • Fixed Keystone auth_uri parameter.

3.1.0

  • Fixed postgresql connection string.
  • Allow log_dir to be set to false to disable file logging.
  • Added support for database idle timeout.
  • Aligned Keystone auth_uri with other OpenStack services.
  • Fixed the EC2 auth token settings.
  • Fixed rabbit_virtual_host configuration.

3.0.0

  • Initial release of the puppet-heat module.

License

Apache License 2.0

Copyright 2012 eNovance licensing@enovance.com and Authors

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Contact

techs@enovance.com