Fix release notes formatting
We use double ticks to format config options, driver FQNs etc. in few release notes to improve readability. This patch updates the remaining release notes to follow the same convention. Change-Id: Ied4e5e02cc781405206edc2322567e5e5e3e170f
This commit is contained in:
Vipin Balachandran
parent
50f607dc54
commit
383c37e0d8
@ -1,6 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- dell_server_os option added to the Dell SC driver.
|
||||
- Config option ``dell_server_os`` added to the Dell SC driver.
|
||||
This option allows the selection of the server type
|
||||
used when creating a server on the Dell DSM during
|
||||
initialize connection. This is only used if the
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
features:
|
||||
- Added a new config option `scheduler_weight_handler`. This is a global
|
||||
- Added a new config option ``scheduler_weight_handler``. This is a global
|
||||
option which specifies how the scheduler should choose from a listed of
|
||||
weighted pools. By default the existing weigher is used which always
|
||||
chooses the highest weight.
|
||||
- Added a new weight handler `StochasticHostWeightHandler`. This weight
|
||||
- Added a new weight handler ``StochasticHostWeightHandler``. This weight
|
||||
handler chooses pools randomly, where the random probabilities are
|
||||
proportional to the weights, so higher weighted pools are chosen more
|
||||
frequently, but not all the time. This weight handler spreads new
|
||||
|
||||
@ -3,5 +3,6 @@ features:
|
||||
- Updating the Datera Elastic DataFabric Storage Driver
|
||||
to version 2.1. This adds ACL support, Multipath
|
||||
support and basic IP pool support.
|
||||
- Changes config option default for datera_num_replicas
|
||||
upgrade:
|
||||
- Changes config option default for ``datera_num_replicas``
|
||||
from 1 to 3
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- Support for use of 'fc_southbound_protocol'
|
||||
- Support for use of ``fc_southbound_protocol``
|
||||
configuration setting in the Brocade FC SAN
|
||||
lookup service.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
---
|
||||
upgrade:
|
||||
- The 'backup_service_inithost_offload' configuration
|
||||
option now defaults to 'True' instead of 'False'.
|
||||
- The ``backup_service_inithost_offload`` configuration
|
||||
option now defaults to ``True`` instead of ``False``.
|
||||
|
||||
@ -8,5 +8,5 @@ upgrade:
|
||||
not be able to utilize this new driver since they still
|
||||
function on v1 of the Datera DataFabric API
|
||||
deprecations:
|
||||
- datera_api_token -- this has been replaced by
|
||||
san_login and san_password
|
||||
- Config option ``datera_api_token`` has been replaced by
|
||||
options ``san_login`` and ``san_password``
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
upgrade:
|
||||
- Any Volume Drivers configured in the DEFAULT config stanza should be moved
|
||||
to their own stanza and enabled via the enabled_backends config option.
|
||||
The older style of config with DEFAULT is deprecated and will be
|
||||
- Any Volume Drivers configured in the ``DEFAULT`` config stanza should be moved
|
||||
to their own stanza and enabled via the ``enabled_backends`` config option.
|
||||
The older style of config with ``DEFAULT`` is deprecated and will be
|
||||
removed in future releases.
|
||||
deprecations:
|
||||
- Configuring Volume Drivers in the DEFAULT config stanza is not going to be
|
||||
- Configuring Volume Drivers in the ``DEFAULT`` config stanza is not going to be
|
||||
maintained and will be removed in the next release. All backends should use
|
||||
the enabled_backends config option with separate stanza's for each.
|
||||
the ``enabled_backends`` config option with separate stanza's for each.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
upgrade:
|
||||
- The Scality driver has been marked as unsupported and is
|
||||
now deprecated. enable_unsupported_drivers will need to
|
||||
be set to True in cinder.conf to continue to use it.
|
||||
now deprecated. ``enable_unsupported_drivers`` will need to
|
||||
be set to ``True`` in cinder.conf to continue to use it.
|
||||
deprecations:
|
||||
- The Scality driver has been marked as unsupported and is
|
||||
now deprecated. enable_unsupported_drivers will need to
|
||||
be set to True in cinder.conf to continue to use it. If
|
||||
now deprecated. ``enable_unsupported_drivers`` will need to
|
||||
be set to ``True`` in cinder.conf to continue to use it. If
|
||||
its support status does not change it will be removed in
|
||||
the next release.
|
||||
|
||||
@ -4,5 +4,5 @@ features:
|
||||
to the NetApp cDOT drivers (iSCSI, FC, NFS).
|
||||
upgrade:
|
||||
- While configuring NetApp cDOT back ends, new configuration options
|
||||
('replication_device' and 'netapp_replication_aggregate_map') must be
|
||||
(``replication_device`` and ``netapp_replication_aggregate_map``) must be
|
||||
added in order to use the host-level failover feature.
|
||||
|
||||
@ -3,7 +3,7 @@ issues:
|
||||
- When running Nova Compute and Cinder Volume or Backup services on the same
|
||||
host they must use a shared lock directory to avoid rare race conditions
|
||||
that can cause volume operation failures (primarily attach/detach of
|
||||
volumes). This is done by setting the "lock_path" to the same directory
|
||||
in the "oslo_concurrency" section of nova.conf and cinder.conf. This issue
|
||||
volumes). This is done by setting the ``lock_path`` to the same directory
|
||||
in the ``oslo_concurrency`` section of nova.conf and cinder.conf. This issue
|
||||
affects all previous releases utilizing os-brick and shared operations
|
||||
on hosts between Nova Compute and Cinder data services.
|
||||
@ -1,4 +1,4 @@
|
||||
---
|
||||
features:
|
||||
- Add get_manageable_volumes and get_manageable_snapshots implementations for
|
||||
- Add ``get_manageable_volumes`` and ``get_manageable_snapshots`` implementations for
|
||||
Pure Storage Volume Drivers.
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
upgrade:
|
||||
- The ISERTgtAdm target was deprecated in the Kilo release.
|
||||
It has now been removed. You should now just use
|
||||
LVMVolumeDriver and specify iscsi_helper for the target
|
||||
LVMVolumeDriver and specify ``iscsi_helper`` for the target
|
||||
driver you wish to use. In order to enable iser, please
|
||||
set iscsi_protocol=iser with lioadm or tgtadm target
|
||||
set ``iscsi_protocol=iser`` with lioadm or tgtadm target
|
||||
helpers.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
upgrade:
|
||||
- EMC ScaleIO driver now uses the config option
|
||||
san_thin_provision to determine the default
|
||||
``san_thin_provision`` to determine the default
|
||||
provisioning type.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
---
|
||||
features:
|
||||
- Added support for scaling QoS in the ScaleIO driver.
|
||||
The new QoS keys are maxIOPSperGB and maxBWSperGB.
|
||||
The new QoS keys are ``maxIOPSperGB`` and ``maxBWSperGB``.
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
features:
|
||||
- Added support for oversubscription in thin provisioning in the
|
||||
ScaleIO driver.
|
||||
Volumes should have extra_specs with the key provisioning:type with value
|
||||
equals to either 'thick' or 'thin'.
|
||||
max_oversubscription_ratio can be defined by the global config or for
|
||||
ScaleIO specific with the config option sio_max_over_subscription_ratio.
|
||||
Volumes should have extra_specs with the key ``provisioning:type`` with value
|
||||
equals to either ``thick`` or ``thin``.
|
||||
``max_oversubscription_ratio`` can be defined by the global config or for
|
||||
ScaleIO specific with the config option ``sio_max_over_subscription_ratio``.
|
||||
The maximum oversubscription ratio supported at the moment is 10.0.
|
||||
@ -12,4 +12,4 @@ upgrade:
|
||||
deprecations:
|
||||
- All barbican and keymgr config options in Cinder are
|
||||
now deprecated. All of these options are moved to
|
||||
the key_manager section for the Castellan library.
|
||||
the ``key_manager`` section for the Castellan library.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
---
|
||||
upgrade:
|
||||
- The VMware VMDK driver supports a new config option 'vmware_host_port'
|
||||
- The VMware VMDK driver supports a new config option ``vmware_host_port``
|
||||
to specify the port number to connect to vCenter server.
|
||||
@ -1,4 +1,4 @@
|
||||
---
|
||||
fixes:
|
||||
- Added support for images with vmware_adaptertype set to
|
||||
paraVirtual in the VMDK driver.
|
||||
- Added support for images with ``vmware_adaptertype`` set to
|
||||
``paraVirtual`` in the VMDK driver.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user