Stein Series Release Notes

7.0.0

Prelude

Added new tool freezer-manager-status upgrade check.

Currently freezer-api v1 is the default api version to be used in different freezer components. Freezer-api v1 doesn’t support multi-tenancy and will be a blocker to support sqlalchemy. Freezer-api v2 was already implement and was being use as experimental. Freezer api v1 will be disabled by default in gate jobs

Currently freezer-api supports only elasticsearch as database engine. Elasticsearch is adding complexity in deploying and running freezer, the need and planning to move to sqlalchemy has been a moving target since Pike. Now freezer-api should be able to support sqlalchemy, it’s still under development, so not fully supported yet. There is work in progress to unify the database api so freezer can support more than one database driver at the same time.

New Features

  • Completely support sqlalchemy driver for freezer-api. The previous version only implemented part one. In this patch, sqlalchemy driver has been completely implemented for freezer-api. See links in detail: https://storyboard.openstack.org/#!/story/2004132 The configuration example is as follows: [database] connection = mysql+pymysql://root:stack@127.0.0.1/freezer?charset=utf8 [storage] backend = sqlalchemy driver = sqlalchemy

  • New framework for freezer-manager-status upgrade check command is added. This framework allows adding various checks which can be run before a Freezer API upgrade to ensure if the upgrade can be performed safely.

  • Fixed some minor bugs in freezer-api v2. Set freezer-api version 2 to stable and use it as the current version. The default behaviour of freezer now is to support multi-tenancy! All tempest tests are running against freezer api v2

  • Freezer support for sqlalchemy in development. freezer-manage fully supports sqlalchemy database now!

Known Issues

  • No Backward compitibility support!

  • No Backward compitibility support! sqlalchemy will be only supported for freezer api version 2

Upgrade Notes

  • Operator can now use new CLI tool freezer-manager-status upgrade check to check if Freezer API deployment can be safely upgraded from N-1 to N release.

Deprecation Notes

  • Freezer api version 1 is deprecated and will be out of support end of Rocky release, to be removed in future releases!.

Critical Issues

  • All Freezer mappings needs to be upgraded to reflect project_id. Now smooth upgrade facility is provided!

  • Freezer api version 1 is broken and won’t be supported!

Bug Fixes

  • Delete Backups using freezer-api v2

  • Fixed remove mappings in freezer-manage as elasticsearch removed this feature, so now we have to delete the index not individual mappings!