Stein Series Release Notes¶
Fixes database migrations with Alembic 1.5.0 or greater. For more details, see bug 1912502.
Updates the on_start failure handlers to look up the freepool aggregate by ID, not by name, when moving hosts back to the freepool. Fixes issue where hosts wind up without any aggregate during lease start failure. For more details, see bug 1847821.
Fixes host creation in the presence of availability zones with no hosts. For more details, see bug 1880646.
Fixes placement operations in multi-region deployments.
Added new tool
blazar-status upgrade check.
New framework for
blazar-status upgrade checkcommand is added. This framework allows adding various checks which can be run before a Blazar upgrade to ensure if the upgrade can be performed safely.
Added a new resource plugin supporting floating IPs. This plugin enables users to reserve floating IPs from Neutron. To try the plugin, add
[manager]/pluginsconfiguration option in
blazar.conf. For the API schema, see details of the APIs in the Lease API reference and Floating IP API reference.
Note that this feature is available as a preview but is not yet complete. The Blazar CLI does not yet support it, documentation is incomplete, and the Update Lease API is not implemented. Floating IP reservation will be fully completed in the next release.
For instance reservation, the reservation parameter
Noneand defaults to
affinity = True
Blazar picks up the same host for the instances for the reservation. Using the reservation flavor, users don’t need to set additional specs such as “server_group” to schedule the instances to the host.
affinity = False
Blazar picks up different hosts for the instances for the reservation. Using the reservation flavor, users don’t need to set additional specs such as “server_group” to schedule to the hosts.
affinity = None(default)
The picked up hosts can be different or same.
ServerGroupAffinityFilteis not needed any more for blazar’s instance reservation.
The List Allocations API and the Get Allocation API are newly implemented. The two APIs return list of mappings between a reservable resource and reservations. Currently Blazar only supports reservation of compute resources, so the APIs return mappings of hosts with reservation IDs of physical host reservations and instance reservations. See details of the API in the API reference .
Operator can now use new CLI tool
blazar-status upgrade checkto check if Blazar deployment can be safely upgraded from N-1 to N release.
Fixes an issue wherein increasing the number of hosts of an active host reservation would fail to add newly allocated hosts to the host aggregate, preventing instances from being deployed on them.
If a host fails to be moved to a host aggregate while starting a reservation, any host previously moved into the same aggregate is now moved back to the freepool. This helps to prevent failures to start future leases allocating the same hosts.
Blazar now prevents leases from being deleted while their start_lease or end_lease events are in progress, to avoid concurrently accessing shared objects. For more details, see bug 1791741.