From dc6cb06021fbfb3d5884fe95f7eef081f349e794 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Tue, 24 Jul 2018 15:08:57 -0400 Subject: [PATCH] doc: remove rocky-specific nova-scheduler min placement version 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 --- doc/source/user/placement.rst | 5 ----- 1 file changed, 5 deletions(-) diff --git a/doc/source/user/placement.rst b/doc/source/user/placement.rst index fd0151a17c..bc714a6227 100644 --- a/doc/source/user/placement.rst +++ b/doc/source/user/placement.rst @@ -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