2025.2 Series Release Notes

16.0.0-3

Bug Fixes

  • Fixes an issue where the amount of instances in an instance reservationcould not be updated when the lease is active.LP#2138386

16.0.0

New Features

  • A new module,blazar.wsgi, has been added as a place to gather WSGIapplication objects. This is intended to ease deployment by providing aconsistent location for these objects. For example, if using uWSGI theninstead of:

    [uwsgi]wsgi-file=/bin/blazar-api-wsgi

    You can now use:

    [uwsgi]module=blazar.wsgi.api:application

    This also simplifies deployment with other WSGI servers that expect modulepaths such as gunicorn.

Upgrade Notes

  • Python 3.8 and 3.9 support has been dropped. The minimum version of Pythonnow supported is Python 3.10.

  • The WSGI scriptblazar-api-wsgi has been removed. Deployment toolingshould instead reference the Python module path for the wsgi module inBlazar,blazar.wsgi.api:application if their chosen WSGI serversupports this (gunicorn, uWSGI, etc.) or implement a .wsgi scriptthemselves if not (mod_wsgi).

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 policyconfiguration, there is no way for a regular user to see lease IDs ofanother project. However, operators that are running the ResourceAvailability Calendar may have overridden this policy, and so may bevulnerable without this fix.LP#2120655

15.0.0

Bug Fixes

  • Fixes functionality of host randomization feature.LP#2099927