[openstack-dev] [Solum] Some initial code copying for db/migration

Michael Still mikal at stillhq.com
Fri Nov 1 21:50:18 UTC 2013

On Sat, Nov 2, 2013 at 3:30 AM, Russell Bryant <rbryant at redhat.com> wrote:

> I also would not use migrate.  sqlalchemy-migrate is a dead upstream and
> we (OpenStack) have had to inherit it.  For new projects, you should use
> alembic.  That's actively developed and maintained.  Other OpenStack
> projects are either already using it, or making plans to move to it.

This is something I wanted to dig into at the summit in fact, mostly
because I'm not sure I agree... Sure migrate is now an openstack
project, but so is olso and we're happy to use that. So I don't think
it being abandoned by the original author is a strong argument.

Its not clear to me what alembic gives us that we actually want...
Sure, we could have a non-linear stream of migrations, but we already
do a terrible job of having a simple linear stream. I don't think
adding complexity is going to make the world any better to be honest.

These are the kind of issues I wanted to discuss in the nova db summit
session if people are able to come to that.


Rackspace Australia

More information about the OpenStack-dev mailing list