tripleo-heat-templates/puppet/extraconfig/pre_deploy
Giulio Fidente 1971e7b049 Passes NodeDataLookup to ceph-ansible workflow
Per-node customizations were only dumped as hieradata, so the
ceph-ansible workflow could not consume them.
This change passes the structure to the mistral workflow so that it
can consume the data and populate the inventory accordingly.

Change-Id: Ie7a9f10f0c821b8c642494a4d3933b2901f39d40
Depends-On: Ia23825aea938f6f9bcf536e35cad562a1b96c93b
Closes-Bug: #1736707
2017-12-13 14:38:02 +01:00
..
compute Change template names to queens 2017-11-23 10:15:32 +01:00
controller Change template names to queens 2017-11-23 10:15:32 +01:00
default.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
per_node.yaml Passes NodeDataLookup to ceph-ansible workflow 2017-12-13 14:38:02 +01:00
README Wire in Controller pre-deployment extraconfig 2015-07-06 10:56:11 -04:00

This tree contains additional configuration which happens "pre deployment",
e.g before the OpenStack services themselves are configured but after the
nodes themselves have been provisioned and initially configured.

Typically for puppet deployments these additional configs will put in place
hieradata which is then consumed by the subsequent puppet configuration
which occurs during the post-deployment phase.

If you need to specify multiple configs, you can chain them together in a
template, see the multiple.yaml example:

  OS::TripleO::ControllerExtraConfigPre: puppet/extraconfig/pre_deploy/controller/multiple.yaml