Bug 1955696

Summary: [RFE] Migrate database migrations from sqlalchemy-migrate to alembic
Product: Red Hat OpenStack Reporter: Stephen Finucane <stephenfin>
Component: openstack-novaAssignee: Stephen Finucane <stephenfin>
Status: CLOSED DEFERRED QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: alifshit, dasmith, egallen, eglynn, jhakimra, kchamart, sbauza, sgordon, smooney, vromanso
Target Milestone: Upstream M3Keywords: FutureFeature, Patch, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-14 18:50:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version: Xena
Embargoed:

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.
Comment 3 Artom Lifshitz 2023-04-14 18:50:12 UTC 
Tracked in https://issues.redhat.com/browse/OSPRH-64