Wallaby Series Release Notes


Bug Fixes

  • Allows users of multiple Keystone domains to create leases; previously only users and projects in the default domain could use Blazar.

  • Fixes failure to update reservations when the resource_type parameter is not provided in the API request. For more details, see bug 1957761.

  • Fixes result of the List Allocations API for reservations with multiple physical hosts. For more details, see bug 1958307.


New Features

  • A filter-based usage enforcement framework is introduced in this release. Enforcement filters allow operators to define lease constraints. The first filter introduced in this release restricts maximum lease duration.

Upgrade Notes

  • The default value of the [oslo_policy]/policy_file configuration option has been changed from policy.json to policy.yaml. Operators using customized or previously generated static policy JSON files (which are not needed by default) should generate new policy files or convert them to YAML format. Use the oslopolicy-convert-json-to-yaml tool to convert a policy file from JSON to YAML in a backward-compatible way.

Deprecation Notes

  • Use of JSON-formatted policy files was deprecated by the oslo.policy library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby cycle with an anticipated future removal of support by oslo.policy. As such operators will need to convert to YAML-formatted policy files. Please see the upgrade notes for details on migration of any custom policy files.

Bug Fixes

  • Fixes database migrations with Alembic 1.5.0 or greater. For more details, see bug 1912502.