From ccc66127600ec1fcc8d9b86ee37a4d59fd00b90b Mon Sep 17 00:00:00 2001 From: Jiri Stransky Date: Thu, 21 Apr 2016 11:17:13 +0200 Subject: [PATCH] Fixed parameter name for ControllerExtraConfig Includes a note how to migrate deployments which made use of `controllerExtraConfig`. Change-Id: I326097dd0d6f2339c3fec561f5386d8370b4f596 --- doc/source/advanced_deployment/node_config.rst | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/doc/source/advanced_deployment/node_config.rst b/doc/source/advanced_deployment/node_config.rst index 372d1271..2eeb0990 100644 --- a/doc/source/advanced_deployment/node_config.rst +++ b/doc/source/advanced_deployment/node_config.rst @@ -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