diff options
author | Steven Hardy <shardy@redhat.com> | 2015-07-15 11:04:13 -0400 |
---|---|---|
committer | Steven Hardy <shardy@redhat.com> | 2015-07-15 16:33:57 +0100 |
commit | 71e9426f195cf3c17fc11adf17f14d41caa7cf30 (patch) | |
tree | b7637c312bb16215ffa4894def70b50382936c5c /examples/scale1.yaml | |
parent | 1ce0f9db531a40e0c3915906a24c002d8ed3eae6 (diff) |
Enable hieradata ExtraConfig overrides for Controller
Wires in the ControllerExtraConfig and ExtraConfig parameters so
that they may be used to specify overrides of the default hieradata.
Note if this is used to override values specified via parameters
rather than hard-coded values in puppet/hieradata caution should
be used as the overridden values will always take precendence
regardless of the parameter input, unless the parameter is provided
directly to the Deployment resource applying the manifiest (e.g
not the pattern currently employed in most of t-h-t)
Also note that ControllerExtraConfig takes precedence over the
deployment-wide ExtraConfig.
For example, here's how you would pass a value which disables the
heat-api-cfn service on all controllers. This would be put into an
environment file, then passed to the heat stack-create via an extra
-e option:
parameters:
controllerExtraConfig:
heat::api_cfn::enabled: false
Note the parameter capitalization is different in the top-level
overcloud-without-mergepy template for some reason.
Change-Id: I6d6e3e78460308134d95c01892bb242aba70e9ca
Diffstat (limited to 'examples/scale1.yaml')
0 files changed, 0 insertions, 0 deletions