Current Series Release Notes

22.0.0-4

New Features

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

  You can now use:

  [uwsgi]
  module = cloudkitty.wsgi.api:application
  

  This also simplifies deployment with other WSGI servers that expect module paths such as gunicorn.

Upgrade Notes

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

22.0.0

New Features

• The CloudKitty policies implemented the scope concept and new default roles (admin, member, and reader) provided by keystone.

Upgrade Notes

• All the policies implement the scope_type and new defaults.

  • Scope

    Each policy is protected with project scope_type.

  • New Defaults (Admin, Member and Reader)

    Policies are default to Admin, Member and Reader roles. Old roles are also supported. There is no change in the legacy admin access.