heat-agents/heat-config-docker-cmd
Steve Baker 4d34592f4a Ensure unique container names
When a container already exists with the desired name, the container
name has a random suffix attached to it so that it can still be run.
This ensures containers are always created regardless of other running
containers.

Since the name may not be as expected, the exec action needs an extra
lookup to attempt to discover the actual name, falling back to the
requested name if the lookup fails.

Since there is a container_name label set with the desired
name, the next patch in this series modifies 50-heat-config-docker-cmd
to rename containers to their desired name when possible.

Change-Id: Ibd97f52811f653295559d000487d2c50a7c67ece
2017-02-20 14:24:55 -05:00
..
install.d Ensure unique container names 2017-02-20 14:24:55 -05:00
os-refresh-config/configure.d Delete containers based on labels, not state files 2017-02-20 14:24:50 -05:00
README.rst Move elements at the top level 2017-01-04 16:57:10 +01:00
element-deps Move elements at the top level 2017-01-04 16:57:10 +01:00

README.rst

A hook which uses the docker command to deploy containers.

The hook currently supports specifying containers in the docker-compose v1 format. The intention is for this hook to also support the kubernetes pod format.

A dedicated os-refresh-config script will remove running containers if a deployment is removed or changed, then the docker-cmd hook will run any containers in new or updated deployments.