Current Series Release Notes

20.0.0.0rc1-32

New Features

  • A new module, manila.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/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.

Upgrade Notes

  • The WSGI script manila-wsgi has been removed. Deployment tooling should instead reference the Python module path for the wsgi module in Manila, manila.wsgi.api:application if their chosen WSGI server supports this (gunicorn, uWSGI, etc.) or implement a .wsgi script themselves if not (mod_wsgi).

Bug Fixes

  • Share replica snapshot creation was taking considerable time due to db operations and resulted in delay of execution for periodic tasks. Fixed it by fetching replicas without share data or without share server data wherever necessary. For more details, please check Launchpad bug #2008497

  • Fixed an issue where stopping a service would produce unhelpful database traceback if a service entry didn’t exist in the database for the service.

  • 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

  • Fixed an issue while creating shares due to an undesired retention period parameter in NetApp ONTAP driver. Fixed this by moving retention_period in PATCH instead of POST api request. For more details, please check Launchpad bug #2111918

  • 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 “*”.

  • NetApp ONTAP driver fixed to apply QoS policy on share only if the throughput is changed. For more details, please check Launchpad bug #2061976

  • NetApp ONTAP driver now updates correct export location after promotion of share replica of replication type readable. For more details, please check Launchpad bug #2104153