summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorZuul <zuul@review.opendev.org>2023-04-17 01:08:26 +0000
committerGerrit Code Review <review@openstack.org>2023-04-17 01:08:26 +0000
commit01ffb6df85ad895bfe94cc46a3be958dbd266a7a (patch)
tree9342b5e777137d0c628c398b5f8e42fda6310341 /doc
parenta5245da25c0f55cffd59b254581bc05237d9c93d (diff)
parentfd39e4b4be9ddb18b96d5f8086955b91232f25e9 (diff)
downloadnova-01ffb6df85ad895bfe94cc46a3be958dbd266a7a.tar.gz
Merge "db: Remove legacy migrations"
Diffstat (limited to 'doc')
-rw-r--r--doc/source/reference/database-migrations.rst12
1 files changed, 8 insertions, 4 deletions
diff --git a/doc/source/reference/database-migrations.rst b/doc/source/reference/database-migrations.rst
index add7597e93..ea2b9050d9 100644
--- a/doc/source/reference/database-migrations.rst
+++ b/doc/source/reference/database-migrations.rst
@@ -24,6 +24,10 @@ Schema migrations
The database migration engine was changed from ``sqlalchemy-migrate`` to
``alembic``.
+.. versionchanged:: 27.0.0 (Antelope)
+
+ The legacy ``sqlalchemy-migrate``-based database migrations were removed.
+
The `alembic`__ database migration tool is used to manage schema migrations in
nova. The migration files and related metadata can be found in
``nova/db/api/migrations`` (for the API database) and
@@ -36,10 +40,10 @@ respectively.
.. note::
- There are also legacy migrations provided in the ``legacy_migrations``
- subdirectory for both the API and main databases. These are provided to
- facilitate upgrades from pre-Xena (24.0.0) deployments and will be removed
- in a future release. They should not be modified or extended.
+ There were also legacy migrations provided in the ``legacy_migrations``
+ subdirectory for both the API and main databases. These were provided to
+ facilitate upgrades from pre-Xena (24.0.0) deployments. They were removed
+ in the 27.0.0 (Antelope) release.
The best reference for alembic is the `alembic documentation`__, but a small
example is provided here. You can create the migration either manually or