2025.1 Series Release Notes

6.3.0

Upgrade Notes

  • Support for Python 3.8 has been removed. Now the minimum python version supported is 3.9 .

6.2.0

New Features

  • The new enable_by_files healthcheck plugin has been added. This plugin will help to check whether specified file paths in [healthcheck] enable_by_file_paths are present or not.

6.1.0

New Features

  • The new [healthcheck] ignore_proxied_requests option has been added. When this option is set to true, the healthcheck middleware ignores requests with any of the following headers, which indicates that the requests came through a reverse proxy or a load balancer.

    • x-forwarded

    • x-forwarded-proto

    • x-forwarded-host

    • x-forwarded-for

    • x-forwarded-prefix

6.0.0

New Features

  • The new [healthcheck] allowed_source_ranges parameter has been added. This parameter defines a list of network ranges from which access to /healthcheck endpoint is allowed.

Upgrade Notes

  • The olso.middleware package has been removed. This package was earlier deprecated to be replaced by the oslo_middleware package.

Deprecation Notes

  • The SSL middleware has been removed. It was deprecated in favor of the HTTPProxyToWSGI middleware.

4.4.0

New Features

  • Adds a basic http auth middleware as an alternative to noauth in standalone environments. This middleware uses a password file which supports the Apache htpasswd syntax. This file is read for every request, so no service restart is required when changes are made. The only password digest supported is bcrypt, and the bcrypt python library is used for password checks since it supports $2y$ prefixed bcrypt passwords as generated by the Apache htpasswd utility.

4.0.0

Upgrade Notes

  • Support for Python 2.7 has been dropped. The minimum version of Python now supported is Python 3.6.

3.38.1

Other Notes

  • Log when max_request_body_size is exceeded.

3.27.0

New Features

  • This adds a new compat_headers class attribute to the RequestId middleware. That allows projects like Nova that have API contracts on alternative request-id headers to adopt the oslo RequestId middleware but still retain their API contract.

  • This adds support for global_request_id to the RequestId middleware. An inbound header of X-OpenStack-Request-ID is accepted as long as it is of the format req-$uuid, and made available to oslo.context. This will allow for cross project request id tracking.

3.20.0

Other Notes

  • Switch to reno for managing release notes.