openstack/nova
Code Issues Proposed changes

doc: remove rocky-specific nova-scheduler min placement version

Browse Source 
Per change I97215e94efdd8c05045872fb9ba7d2089dc6efb8, nova
does not perform version discovery or try to deal with backlevel
placement versions, and the upgrade docs say that placement needs
to be upgraded before upgrading any nova services. Because of
this assertion, we can remove the per-release nova-scheduler-specific
note in the placement upgrade notes for Rocky because while it's
accurate for the nova-scheduler service, it might not be accurate
for the nova-api, nova-conductor or nova-compute services which
also use placement. So the best guidance is to just globally say
that placement must be upgraded before *any* nova services, which
our upgrade doc already says.

Change-Id: I8bf6ab049f15ad24a5fbf0557bd0cd8652101901
This commit is contained in:
Matt Riedemann 2018-07-24 15:08:57 -04:00
parent 5486f17883
commit dc6cb06021
1 changed files with 0 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -292,11 +292,6 @@ Queens (17.0.0)
Rocky (18.0.0)
~~~~~~~~~~~~~~
* The minimum Placement API microversion required by the *nova-scheduler*
service is ``1.25`` in order to
`perform granular allocation candidate requests`_.
This means you must upgrade the placement service before upgrading any
*nova-scheduler* services to Rocky.
* The ``nova-api`` service now requires the ``[placement]`` section to be
configured in nova.conf if you are using a separate config file just for
that service. This is because the ``nova-api`` service now needs to talk