summaryrefslogtreecommitdiff
path: root/doc/source/contributor/database-migrations.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/source/contributor/database-migrations.rst')
-rw-r--r--doc/source/contributor/database-migrations.rst11
1 files changed, 9 insertions, 2 deletions
diff --git a/doc/source/contributor/database-migrations.rst b/doc/source/contributor/database-migrations.rst
index f8e8a7a5e..3827ea8e6 100644
--- a/doc/source/contributor/database-migrations.rst
+++ b/doc/source/contributor/database-migrations.rst
@@ -17,10 +17,17 @@
Database Migrations
===================
+.. note::
+
+ The framework being used is currently being migrated from
+ SQLAlchemy-Migrate to Alembic, meaning this information will change in the
+ near-term.
+
Starting with Newton, keystone supports upgrading both with and without
downtime. In order to support this, there are three separate migration
-repositories (all under ``keystone/common/sql/``) that match the three phases
-of an upgrade (schema expansion, data migration, and schema contraction):
+repositories (all under ``keystone/common/sql/legacy_migrations``) that match
+the three phases of an upgrade (schema expansion, data migration, and schema
+contraction):
``expand_repo``
For additive schema modifications and triggers to ensure data is kept in