From ae4285c837a65c2ebd918b68fefc720d79b15eb9 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Mon, 18 Jun 2018 16:56:24 -0400 Subject: [PATCH] Clarify placement DB schema migration This just clarifies in the release note for the optional placement database that the database itself is not created when running "nova-manage api_db sync", but rather the database schema is created. This is important since a non-trivial number of people over the years have thought that the db sync commands actually create a database, which they do not. Change-Id: Ie6c3a5dc61a288935829276cc72f7f7563e20420 --- releasenotes/notes/placement-database-2e087f379273535d.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/releasenotes/notes/placement-database-2e087f379273535d.yaml b/releasenotes/notes/placement-database-2e087f379273535d.yaml index a3b081a935dd..41798f6fdce4 100644 --- a/releasenotes/notes/placement-database-2e087f379273535d.yaml +++ b/releasenotes/notes/placement-database-2e087f379273535d.yaml @@ -9,8 +9,9 @@ features: ``placement_database`` configuration group will be used to configure a separate placement database, including using ``connection`` to identify the target database. That database will have a schema that is a replica of all - the tables used in the API database. The new database will be created and - synchronized when the ``nova-manage api_db sync`` command is run. + the tables used in the API database. The new database schema will be + created and synchronized when the ``nova-manage api_db sync`` command is + run. When the ``placement_database.connection`` setting is omitted the existing settings for the ``api_database`` will be used for hosting placement data.