Add docker_puppet_tasks initialization on primary node
authorDan Prince <dprince@redhat.com>
Sun, 29 Jan 2017 13:01:46 +0000 (08:01 -0500)
committerDan Prince <dprince@redhat.com>
Wed, 15 Feb 2017 18:09:59 +0000 (13:09 -0500)
commit84626c82cc54a0b1de595cbac06336045947dc4a
treea290af3c02f2f14eb451319aace0d5d903df2374
parentad2ea290bed17bff9b53ac225d3604ed642ee8bc
Add docker_puppet_tasks initialization on primary node

This patch adds a new (optional) section to the docker post.j2.yaml
that collects any 'docker_puppet_tasks' data from enabled
services and applies it on the primary role node (the
first node in the primary (first) role).

The use case for this is although we are generally only using
puppet for configuration there are several exceptions that we
desire to make use of today for parity with baremetal. This
includes things like database creation and keystone endpoint
initialization which we rely on configuration via hiera variables
controlled by the puppet services.

Change-Id: Ic14ef48f26de761b0d0eabd0e1c0eae52d90e68a
docker/docker-puppet.py
docker/post.j2.yaml
docker/services/README.rst
docker/services/services.yaml