c5d10cd9fc
The new hiera hook in I21639f6aadabf9e49f40d1bb0b1d0edcfc4dbc5e was added to most of the tripleo-heat-templates in Ibe7e2044e200e2c947223286fdf4fd5bcf98c2e1 The new hook is installed by default if you use tripleo-common Ia1864933235152b7e899c4442534879f8e22240d and will be installed as part of the Newton to Ocata upgrades workflow in I0c7a32194c0069b63a501a913c17907b47c9cc16 In order to use the new hiera data as part of the upgrade we need to remove the old hieradata which will break anyone still defining and using it. This change updates the remaining vendor plugin manifests to use the new hiera hook. The pre-requisite is that the new hook is installed on their overcloud (as above it comes if you follow the N..O upgrade) Change-Id: Ic95154734cb21e6b941c7f1569295b413963831d |
||
|---|---|---|
| .. | ||
| compute | ||
| controller | ||
| default.yaml | ||
| per_node.yaml | ||
| README | ||
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