Switch DB migrations from SQLAlchemy-migrate to Alembic

Registered by Venkatesh Sampath

Some work has already been started on moving from SQLAlchemy-migration to Alembic on other projects like ceilometer and nova and their blueprints can be located through the following links:

https://blueprints.launchpad.net/nova/+spec/convert-to-alembic

https://blueprints.launchpad.net/ceilometer/+spec/convert-to-alembic

Even though the above blueprints have enough info on this. Some of the notable points to plan to move from sqlalchemy-migration to alembic are:

1) sqlalchemy-migration project is no longer maintained and doesn't accept bug fixed any more.
For more info on the activity of the project, please visit:
http://code.google.com/p/sqlalchemy-migrate/
https://www.ohloh.net/p/sqlalchemy-migrate/commits/summary

2) does not support SQLAlchemy 0.8.x (but seems like some patches are available but not sure if it addresses all compatibility issues)

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Venkatesh Sampath
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

The nova blueprint seems stalled, and from a bit of searching I wasn't entirely sure if ceilometer had fully switched to alembic at this point? I'd kind of prefer for glance to not lead in this effort, just to reduce risk and the number of simultaneous changes. However, it could make a lot of sense to start in glance if the overall community is sure that we want to switch to alembic.
Based on this, I'd like to abandon this blueprint for now. But please share with me any information you have about broader community consensus on alembic, because I'm sure there are important parts of the conversation I've missed. Thanks!
markwash abandoned 2014-02-18

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.