openstack/nova
Code Issues Proposed changes

doc: Upgrade placement first

Browse Source 
It has long been *recommended* that the placement service be upgraded
before nova services, but scenarios where it isn't have never really
been explored or tested.  Following (yet another) discussion on the
topic [1] it was decided that we are best served by *requiring* that
placement be updated first.  This simplifies our test/support matrix,
and the code we write to consume placement.  It also makes the operator
experience cleaner by giving them a clear and unambiguous script to
follow.

This change set rewords the upgrade document accordingly.

[1] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-03-26.log.html#t2018-03-26T17:35:11

Change-Id: I97215e94efdd8c05045872fb9ba7d2089dc6efb8
This commit is contained in:
Eric Fried 2018-03-26 14:37:30 -05:00
parent cd15c3d6ec
commit 7f1b338bce
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/user/upgrade.rst
View File

@ -80,9 +80,8 @@ same time.
#. During maintenance window:
* Several nova services rely on the external placement service, and while
efforts are made for the nova code to work with older versions of the
placement API, it is generally best to upgrade placement before any nova
* Several nova services rely on the external placement service being at the
latest level. Therefore, you must upgrade placement before any nova
services. See the
:ref:`placement upgrade notes <placement-upgrade-notes>` for more
details on upgrading the placement service.