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
19 lines
406 B
YAML
19 lines
406 B
YAML
heat_template_version: 2014-10-16
|
|
description: 'Extra Pre-Deployment Config, multiple'
|
|
parameters:
|
|
server:
|
|
type: string
|
|
|
|
resources:
|
|
|
|
CinderNetappConfig:
|
|
type: cinder-netapp.yaml
|
|
properties:
|
|
server: {get_param: server}
|
|
|
|
# Note depends_on may be used for serialization if ordering is important
|
|
OtherConfig:
|
|
type: other.yaml
|
|
properties:
|
|
server: {get_param: server}
|