Bug 890189
| Summary: | Better support for database schema migrations | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Perry Myers <pmyers> |
| Component: | RFEs | Assignee: | David Ripton <dripton> |
| Status: | CLOSED WONTFIX | QA Contact: | Yaniv Kaul <ykaul> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.0 (Folsom) | CC: | apevec, jkt, markmc, nobody |
| Target Milestone: | beta | ||
| Target Release: | 3.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-05-22 18:24:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Perry Myers
2012-12-25 15:52:35 UTC
upstream post pointing to design summit session: http://lists.openstack.org/pipermail/openstack-dev/2012-November/003096.html https://etherpad.openstack.org/nova-backportable-db-migrations where conclusion seems to was "Alembic didn't make it better, it just had different issues." Assigning to David since he's working on migration to Alembic upstream. As Alan noted, there is some resistance upstream to switching Nova from sqlalchemy-migrate to Alembic. If we resolve the politics then I think it's a pretty easy technical change -- I have code that mostly automates converting the migration scripts in https://review.openstack.org/15196 There is a blueprint for backportable db migrations. https://blueprints.launchpad.net/nova/+spec/backportable-db-migrations But the current solution is to leave gaps in the linear migrate numbers, rather than to switch to Alembic, which supports more dynamic migration ordering. Quantum is using Alembic now. Commit dbf0b22abb5a55e3. Requires alembic >= 0.4.1. Fedora 17 currently ships python-alembic 0.3.0 This is a WONTFIX for now, as upstream seems satisfied with sqlalchemy-migrate and things seem to work well enough. If it flares up again in the future we can make a new bug. |