2025.2 Series Release Notes

21.0.0

New Features

• Added mutually exclusive config options [action_providers]/allowlist and [action_providers]/denylist that can be used to filter what action providers is loaded.

• Added mutually exclusive config options [legacy_action_provider]/allowlist and [legacy_action_provider]/denylist that can be used to filter what actions is loaded by the legacy action provider.

Upgrade Notes

• Support for Python 3.8 and 3.9 has been dropped.

• The oslo_rpc_executor option is removed. If you were explicitly setting oslo_rpc_executor = threading in your configuration, you can safely remove this setting as threading is now the only supported executor type.

Deprecation Notes

• Deprecate the api_workers option for mistral-api. This option was used to spawn multiple workers when using oslo.service wsgi server. Since we moved to cheroot, this is not possible anymore. If you want to use more than one process to handle Mistral API requests, you should consider using mistral-wsgi-api behind a wsgi server.

• Kombu RPC driver is now deleted from mistral RPC drivers. Only oslo messaging driver is supported.

Bug Fixes

• The Mistral API is now served by cheroot.wsgi.Server instead of the deprecated oslo_service.wsgi / eventlet stack. Behaviour and CLI commands are unchanged.

Other Notes

• Adding a new wsgi entrypoint to allow using it within WSGI servers (like uWSGI) using mistral.wsgi:application.

  Note that this is the only way to start more than one mistral API worker.

  Also adding two environment variables MISTRAL_CONFIG_DIR and MISTRAL_CONFIG_FILE to allow setting config-dir and config-file when using the new wsgi entrypoint.

• The /v2/services endpoint in mistral is now removed. This endpoint was using tooz.coordination which we decided to get rid of in the previous release. That endpoint was introduced in the past to help administrator know which services were running but we believe this is not widely used and can easily be replaced by external tooling.