Current Series Release Notes

22.0.0-14

New Features

• Add new fields to specify the validity period of rating rules for modules hashmap and pyscripts. These new fields also improve the audit mechanism for rating rules changes and deletion, allowing users to know when the rules were changed or removed (marked as deleted) and by whom.

• 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

• New rules for both hashmap and pyscript modules will no longer be reprocessed for past periods, by default they are valid from the moment they were created on. To allow new rules to be valid for past periods, operators will need to specify a start_date in the past and pass the query parameter force=true when creating the rating rule, then the rule will be valid and used since the defined start date. Update rating rules for both hashmap and pyscript modules will no longer be allowed for rules where the start_date is in the past, to do so, you will need to delete and create a new rating rule with the desired values, the unique value you can update for rules that already started, is the end_date.

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

• 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.