2024.1 Series Release Notes

17.0.0

Upgrade Notes

• The database migration engine has changed from sqlalchemy-migrate to alembic. For most deployments, this should have minimal to no impact and the switch should be mostly transparent. The main user-facing impact is the change in schema versioning. While sqlalchemy-migrate used a linear, integer-based versioning scheme, which required placeholder migrations to allow for potential migration backports, alembic uses a distributed version control-like schema where a migration’s ancestor is encoded in the file and branches are possible. The alembic migration files therefore use a arbitrary UUID-like naming scheme and the masakari-manage db_sync command now expects such an version when manually specifying the version that should be applied. For example:

  $ masakari-manage db sync c6214ca60943
  

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