Fixed parameter name for ControllerExtraConfig

Includes a note how to migrate deployments which made use of
`controllerExtraConfig`.

Change-Id: I326097dd0d6f2339c3fec561f5386d8370b4f596
This commit is contained in:
Jiri Stransky 2016-04-21 11:17:13 +02:00
parent 76b603f6fa
commit ccc6612760

View File

@ -33,11 +33,22 @@ The parameters available are:
* `ExtraConfig`: Apply the data to all nodes, e.g all roles
* `NovaComputeExtraConfig`: Apply the data only to Compute nodes
* `controllerExtraConfig`: Apply the data only to Controller nodes *(note the inconsistent capitalization...)*
* `ControllerExtraConfig`: Apply the data only to Controller nodes
* `BlockStorageExtraConfig`: Apply the data only to BlockStorage nodes
* `ObjectStorageExtraConfig`: Apply the data only to ObjectStorage nodes
* `CephStorageExtraConfig`: Apply the data only to CephStorage nodes
.. note::
Previously the parameter for Controller nodes was named
`controllerExtraConfig` (note the inconsistent capitalization). If
you are updating a deployment which used the old parameter, all
values previously passed to `controllerExtraConfig` should be
passed to `ControllerExtraConfig` instead, and
`controllerExtraConfig: {}` should be explicitly set in
`parameter_defaults`, to ensure that values from the old parameter
will not be used anymore.
.. note::
Passing data via the ExtraConfig parameters will override any statically