Current Series Release Notes¶
20.0.0.0rc1-14¶
New Features¶
A new module,
manila.wsgi
, has been added as a place to gather WSGIapplication
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/manila-wsgi
You can now use:
[uwsgi] module = manila.wsgi.api:application
This also simplifies deployment with other WSGI servers that expect module paths such as gunicorn.
Added support for authentication using an API token in the VAST Manila driver. Introduced the vast_api_token configuration option, allowing users to authenticate with a pre-generated API token instead of using vast_mgmt_user and vast_mgmt_password.
Bug Fixes¶
Manila now correctly handles the ‘server_migrating’ status of share and snapshot instances during share server migration especially during share server belonging to non-active replica. For more details, please check Launchpad bug #2104357
For generic driver, when resize a share it may failed due to exportfs can’t recognize “<world>” as part of the share path. This issue has been fixed by replacing “<world>” to “*”.