OpenStack Identity (keystone)

RFE: Use Alembic for database migrations

Bug #1816107 reported by Lance Bragstad
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Triaged
Wishlist
Unassigned

Bug Description

Move from SQLALChemy-migrate to Alembic as the tool for maintaining SQL Repos.

Tags: rfe sql upgrades
Revision history for this message
Lance Bragstad (lbragstad) wrote :

Specification review: https://review.openstack.org/#/c/131531/
Specification doc: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/alembic.html

tags: added: sql
tags: added: upgrades
Changed in keystone:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Lance Bragstad (lbragstad) wrote :

Patches that work towards this initiative:

alembic initial support: https://review.openstack.org/150057
Do not add new 'db' command and subcommands for it: https://review.openstack.org/177219
Target Alembic for Liberty: https://review.openstack.org/177220
Use migration_cli for db migrations: https://review.openstack.org/147548

Lance Bragstad (lbragstad)
tags: added: rfe
Revision history for this message
Vishakha Agarwal (vishakha.agarwal) wrote :

Now we have two commands that are related to migrations -- db_sync to migrate and db_version to show the current version. It works OK with sqlalchemy-migrate, but not with Alembic that we will be using. What needs to be done is to create a set of commands - "db upgrade/downgrade/stamp/revision/version". It will comply with alembic commands and with oslo.db migration_cli interface.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.