From acbec41a690150382957651240d5bb427433cc90 Mon Sep 17 00:00:00 2001 From: shaofeng_cheng Date: Thu, 4 May 2017 10:22:04 +0800 Subject: [PATCH] Replace newton to release_name in upgrade.rst Replace newton to release_name to avoid such updates for each new release. Change-Id: I9f580fb00eabff90e7581af10b323592c22737c3 --- doc/source/upgrade.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/upgrade.rst b/doc/source/upgrade.rst index 46dad7bddbed..0eb0ef056380 100644 --- a/doc/source/upgrade.rst +++ b/doc/source/upgrade.rst @@ -86,7 +86,7 @@ same time. ``[upgrade_levels]compute=auto`` in nova.conf. It is safest to start nova-conductor first and nova-api last. Note that you may use a static alias name instead of ``auto``, such as - ``[upgrade_levels]compute=newton``. Also note that this step is + ``[upgrade_levels]compute=``. Also note that this step is only required if compute services are not upgraded in lock-step with the control services. @@ -107,7 +107,7 @@ same time. starts, it automatically detects which version of the compute RPC protocol to use, and it can decide if it is safe to do any online data migrations. Note, if you used a static value for the upgrade_level, such as - ``[upgrade_levels]compute=newton``, you must update nova.conf to remove + ``[upgrade_levels]compute=``, you must update nova.conf to remove that configuration value and do a full service restart. * Now all the services are upgraded and signaled, the system is able to use