e4c4c4068e
The recently added cinder-netapp extraconfig contains some additional hieradata which needs to be applied during the initial pre-deployment phase, e.g in controller-puppet.yaml (before the manifests are applied) so wire in a new OS::TripleO::ControllerExtraConfigPre provider resource which allows passing in a nested stack (empty by default) which contains any required "pre deployment" extraconfig, such as applying this hieradata. Some changes were required to the cinder-netapp extraconfig and environment such that now the hieradata is actually applied, and the parameter_defaults specified will be correctly mapped into the StructuredDeployment. Change-Id: I8838a71db9447466cc84283b0b257bdb70353ffd
13 lines
624 B
Plaintext
13 lines
624 B
Plaintext
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
|