Clarify the enable_cinder option description

Currently it implies that we support booting from volumes in the undercloud,
which is not the case yet. Change the option description accordingly.

Change-Id: Ie2d92f3e5e4301375290a66553e2afb3cec6da80
Closes-Bug: #1692522
This commit is contained in:
Dmitry Tantsur 2017-05-22 14:53:06 +02:00
parent d050dbcb6d
commit 4755b13f47
3 changed files with 9 additions and 4 deletions

View File

@ -312,8 +312,8 @@ _opts = [
),
cfg.BoolOpt('enable_cinder',
default=False,
help=('Whether to install the Volume service to be boot '
'overcloud nodes from remote volumes.')),
help=('Whether to install the Volume service. It is not '
'currently used in the undercloud.')),
cfg.BoolOpt('enable_legacy_ceilometer_api',
default=False,
help=('Whether to enable legacy ceilometer api '

View File

@ -0,0 +1,5 @@
---
fixes:
- |
The description of the ``enable_cinder`` option was fixed to not imply
that booting from Cinder volumes is implemented in the undercloud.

View File

@ -163,8 +163,8 @@
# (boolean value)
#enable_validations = true
# Whether to install the Volume service to be boot overcloud nodes
# from remote volumes. (boolean value)
# Whether to install the Volume service. It is not currently used in
# the undercloud. (boolean value)
#enable_cinder = false
# Whether to enable legacy ceilometer api in the Undercloud. Note: