openstack
/
nova
Code Issues Proposed changes

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
This commit is contained in:
Matt Riedemann 2018-06-18 16:56:24 -04:00
parent 530c24596a
commit ae4285c837
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
releasenotes/notes/placement-database-2e087f379273535d.yaml
View File

@ -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.