openstack
/
operations-guide
Code Issues Proposed changes

Correct misleading documentation about upgrade levels. 

Documentation suggest that upgrade level shoud be locked
to new version of service (X+1) while this option
is designed to be a version level cap to prevent new service
version send RPC API messages that older versions may not
understand. This feature is described in nova's documentation:

https: //github.com/openstack/nova/blob/master/nova/conf/upgrade_levels.py#L35
Change-Id: Icee7bf2b3b9cb4b5f0e0c1f767b1d982db7a7566
This commit is contained in:
Rafal Ramocki 2021-09-07 09:57:50 +02:00
parent 6f2404505f
commit 4c9aadb133
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/ops-upgrades.rst
View File

@ -154,12 +154,12 @@ For example:
.. code-block:: ini
[upgrade_levels]
compute=X+1
conductor=X+1
scheduler=X+1
compute=X
conductor=X
scheduler=X
will keep the RPC version locked across the specified services to the
RPC version used in X+1. As all instances of a particular service are
RPC version used in X. As all instances of a particular service are
upgraded to the newer version, the corresponding line can be removed
from ``nova.conf``.