Current Series Release Notes

29.0.1-75

New Features

  • A new module, nova.wsgi, has been added as a place to gather WSGI application objects. This is intended to ease deployment by providing a consistent location for these objects. For example, if using uWSGI then instead of:

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

    You can now use:

    [uwsgi]
    module = nova.wsgi.osapi_compute:application
    

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

  • With the libvirt driver and libvirt version 7.3.0 or newer, mediated devices for vGPUs are now persisted across reboots of a compute host.

    Note

    After a compute host reboots, if you have a GPU that supports SR-IOV, then the virtual functions for the GPU must be enabled again before instances will be able to use their vGPUs. Please see https://docs.openstack.org/nova/latest/admin/virtual-gpu.html for more information.

  • This release removes the limit of the number of tenants that can be specified for an aggregate and honored by the AggregateMultitenancyIsolation filter. It now respects multiple keys prefixed by filter_tenant_id like the request filter implementation. You can use filter_tenant_id as a prefix to set an infinite number of properties for tenant IDs on the aggregate. This change has been implemented in a manner that preserves backward compatibility. Existing configurations using filter_tenant_id will continue to function as expected.

Bug Fixes

  • Nova now ensures that an instance cannot move between availability zones when the host of the instance is added or removed to an aggregate that is part of another availability zone. Moving from or to the default availability zone is also rejected.

    This resolves bug 1907775 where after such move the instance become stuck in between availability zones.

  • Bug #2002606: Previously, server rescue in stable device mode had a dependency on the original image used to create or rebuild the server. If the original image was deleted from Glance, the server could not be rescued. The issue has been fixed by falling back to the instance image metadata if the original image is not found in Glance.

  • Introduced a new compute configuration option sharing_providers_max_uuids_per_request and applied a fix to handle the “Request-Too-Long” error that can occur when querying the placement API with a large number of aggregate UUIDs.