Upgrade Notes¶

• The database migration engine has changed fromsqlalchemy-migrate toalembic. For most deployments, this should have minimal to no impactand the switch should be mostly transparent. The main user-facing impact isthe change in schema versioning. While sqlalchemy-migrate used a linear,integer-based versioning scheme, which required placeholder migrations toallow for potential migration backports, alembic uses a distributed versioncontrol-like schema where a migration’s ancestor is encoded in the file andbranches are possible. The alembic migration files therefore use aarbitrary UUID-like naming scheme and themasakari-managedb_synccommand now expects such an version when manually specifying the versionthat should be applied. For example:

  $ masakari-manage db sync c6214ca60943

  Attempting to specify an sqlalchemy-migrate-based version will result in anerror.