2024.2 Series Release Notes¶
14.0.0-5¶
Security Issues¶
Fixes a bug where any user could update/delete a lease from any project, provided that they had the lease ID. When using the default policy configuration, there is no way for a regular user to see lease IDs of another project. However, operators that are running the Resource Availability Calendar may have overridden this policy, and so may be vulnerable without this fix. LP#2120655
Bug Fixes¶
Fixes functionality of host randomization feature. LP#2099927
14.0.0¶
New Features¶
Add a new resource type
flavor:instance
to reserve instances based on existing flavors. This is implemented by a new plugin namedflavor.instance.plugin
. Note that this feature is available as a preview but is not yet complete. See documentation for more details.
Upgrade Notes¶
Instance reservations will no longer create a server group when the
affinity
parameter is not set. This means that instances can be deployed on any host. To achieve the old behaviour, you must now explicity set--affinity=false
. LP#2071832
Bug Fixes¶
Allow multiple Blazar API services to run against a single Blazar manager service.
Instance reservations will no longer create a server group when the
affinity
parameter is not set. This means that instances can be deployed on any host. LP#2071832