0e850373a8
In order to be able to take an action after all the packages of the module have been installed/updated or all the services have been started/restarted, we set a 'heat-package' and 'heat-service' tag for each package and service of this module. At the moment, there is a generic openstack tag that is not specific enough if one wants to take action upon a single module change. Use case : If an action needs to be taken after all the packages have been installed or updated : Package <| tag == 'heat-package' |> -> X Change-Id: I38a6b422054dbf0fceacf6b7e329dbb3cb0fa9cb
puppet-heat
6.0.0 - 2015.1 - Kilo
Table of Contents
- 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
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
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
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.