From 3abd5f5797737b54c10ea85d4b833aff054d1bee Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Wed, 16 May 2018 14:28:26 -0400 Subject: [PATCH] Update placement upgrade docs for nova-api dependency on placement Change If507e23f0b7e5fa417041c3870d77786498f741d makes nova-api dependent on placement for deleting an instance when the nova-compute service on which that instance is running is down, also known as "local delete". Change I7b8622b178d5043ed1556d7bdceaf60f47e5ac80 makes nova-api dependent on placement for deleting a nova-compute service record. Both changes are idempotent if nova-api isn't configured to use placement, but warnings will show up in the logs. This change updates the upgrade docs to mention the new dependency. Change-Id: I941a8f4b321e4c90a45f7d9fccb74489fae0d62d Related-Bug: #1679750 Related-Bug: #1756179 --- doc/source/user/placement.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/source/user/placement.rst b/doc/source/user/placement.rst index 835e103471ae..a865d11afa63 100644 --- a/doc/source/user/placement.rst +++ b/doc/source/user/placement.rst @@ -288,6 +288,15 @@ Rocky (18.0.0) `filter allocation candidates by aggregate membership`_. 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 + to the placement service in order to (1) delete resource provider allocations + when deleting an instance and the ``nova-compute`` service on which that + instance is running is down and (2) delete a ``nova-compute`` service record + via the ``DELETE /os-services/{service_id}`` API. This change is idempotent + if ``[placement]`` is not configured in ``nova-api`` but it will result in + new warnings in the logs until configured. REST API ========