heat-templates/hot/software-config
Jiri Stransky 45dd5c8fc8 Ensure Puppet can run even on PoC net setups
For `puppet apply` to run successfully, outputs of `hostname -f` and
`facter fqdn` must match. In a properly configured network environment
the outputs should always match, in PoC environment they might not. This
patch overrides the FQDN fact to the result of `hostname -f`, which will
make `puppet apply` succeed even in PoC environments where DNS is not
configured properly.

Change-Id: I0d63fb0b862f984a196ac01345c74b4e5378e8a8
Partial-Bug: #1447497
2015-04-27 10:32:27 +02:00
..
boot-config Some minor changes to container boot-config 2015-04-22 09:48:15 +05:30
elements Ensure Puppet can run even on PoC net setups 2015-04-27 10:32:27 +02:00
example-templates Some minor changes to container boot-config 2015-04-22 09:48:15 +05:30
heat-container-agent Some minor changes to container boot-config 2015-04-22 09:48:15 +05:30
test-image Build selinux-permissive test images 2015-03-17 08:53:59 +13:00
README.rst Elements for building a heat test image 2015-03-04 10:21:03 +13:00

README.rst

HOT software configuration hooks and examples

The Heat software configuration resources can be combined with a server agent and hooks to configure software on servers using a variety of techniques.

Contained here are the following directories:

boot-config

This directory has environment files which each declare a resource type Heat::InstallConfigAgent.

This can be used by server user_data when booting a pristine image to install the agent required to use software deployment resources in templates.

elements

This contains diskimage-builder elements which will install the hooks for different configuration tools onto a custom-built image.

example-templates

This contains example heat templates which demonstrate how the software config resources and the hooks work together to perform software configuration.

test-image

This contains diskimage-builder elements which will install the distro packages required for a base test image.