From b63177470fb546d69fc84c4564e6fc065e7c527d Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Thu, 24 Mar 2016 09:47:38 -0400 Subject: [PATCH] Clarify the ``use_neutron`` option upgrade notes. Change-Id: Id86021c684c98a8cc7ff81655f64c857a5115420 --- .../notes/rm_volume_manager-78fed5be43d285b3.yaml | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/releasenotes/notes/rm_volume_manager-78fed5be43d285b3.yaml b/releasenotes/notes/rm_volume_manager-78fed5be43d285b3.yaml index 8f3e4927c7df..2d6659f3a6b1 100644 --- a/releasenotes/notes/rm_volume_manager-78fed5be43d285b3.yaml +++ b/releasenotes/notes/rm_volume_manager-78fed5be43d285b3.yaml @@ -1,11 +1,16 @@ --- upgrade: - - A new ``use_neutron`` option is introduced which replaces the - obtuse ``network_api_class`` option. This defaults to 'False' to - match existing defaults, however if ``network_api_class`` is set - to the known Neutron value Neutron networking will still be used - as before. + - A new ``use_neutron`` option is introduced for configuring Nova to + use Neutron for its network backend. This replaces the deprecated + ``network_api_class`` and ``security_group_api`` options, which are + confusing to use and error prone. The default for this new value + is ``False`` to match existing defaults, however if + ``network_api_class`` and/or ``security_group_api`` are set to + known Neutron values, Neutron networking will still be used as + before. Installations are encourged to set this config option soon + after upgrade as the legacy options will be removed by the Newton + release. deprecations: