Bug 1955696 - [RFE] Migrate database migrations from sqlalchemy-migrate to alembic
Summary: [RFE] Migrate database migrations from sqlalchemy-migrate to alembic
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: nova-maint
QA Contact: nova-maint
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-30 16:52 UTC by Stephen Finucane
Modified: 2021-04-30 17:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version: Xena


Attachments (Terms of Use)

Description Stephen Finucane 2021-04-30 16:52:36 UTC
Description of problem:

nova's database migrations are implemented using sqlalchemy-migrate, a defunct and unmaintained library. alembic is the anointed successor that is developed and supported by the sqlalchemy community. The Network (neutron) and Image (glance) services already migrated to alembic some time ago. It is now time for Compute (nova) to do the same. Doing so will reduce some tech debt in the project and bring usability improvements to operators, who can use the same tooling to run database migrations across multiple projects. This RFE tracks the work to migrate the migrations, providing a way for both existing deployments and new deployments to start using alembic for all migrations going forward.


Note You need to log in before you can comment on or make changes to this bug.