Note de release pour les changements non déployées

4.4.1-2

New Features

• Added oslo_service._multiprocessing module providing get_spawn_context() and get_spawn_pool() utilities. These enforce the spawn start method to avoid fork-inherited lock deadlocks, as explained in: https://pythonspeed.com/articles/python-multiprocessing/

4.4.1

Upgrade Notes

• The ThreadGroup.max_threads attribute has been restored for backward compatibility. It previously disappeared during the backend refactor (commit 8c74d0718dc11ed5), which caused consumers such as Heat to fail when upgrading to oslo.service 4.4.0. The attribute now maps to thread_pool_size and emits a DeprecationWarning. Applications should migrate to thread_pool_size. The deprecated attribute may be removed in a future release.

4.4.0

Upgrade Notes

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

• The oslo.service.wsgi.Server class now includes backend compatibility checks to prevent improper usage with the threading backend. Applications using the threading backend that attempt to instantiate the WSGI Server will now receive an immediate UnsupportedBackendError exception with a clear error message.

  This is an intentional breaking change to prevent potential runtime issues and security concerns that could arise from using a component designed for eventlet in a threading environment. The fail-fast behavior ensures that applications using the threading backend are guided towards the correct deployment patterns.

  Migration Path: Users should migrate to deploying their WSGI applications using standard WSGI servers such as uwsgi, gunicorn, or similar alternatives instead of relying on the deprecated oslo.service WSGI server.