History

Steve Baker d10069ac13 docker-cmd hook handle empty config file

Early in a server boot the file /var/run/heat-config/heat-config may
exist but be empty. This causes a stack trace to be raised in this
script.

This change detects a json parse error and exits gracefully.

Change-Id: I29d731098659bfbf10a2caf80c2cfc49de5df4cc
Closes-Bug: #1648249

2016-12-13 09:57:52 +13:00

boot-config

Break out inlined boot config files

2016-09-01 10:15:31 +12:00

elements

docker-cmd hook handle empty config file

2016-12-13 09:57:52 +13:00

example-templates

Add example to configure ca certificates with userdata

2016-11-24 14:42:33 +08:00

heat-container-agent

Apply tripleo-image-elements fixes to agent configs

2016-05-19 14:26:25 -05:00

test-image

Wrong usage of "a/an"

2015-12-31 01:15:24 +08: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.