cASO Release Notes

Current Release Notes

4.1.1-18

Bug Fixes

  • Fixes issue 115, where timestamps where incorrecly rendered. This fix requires a republish of records.

4.1.1

Upgrade Notes

  • The reader role with a system scope of all must be granted to the cASO user, please check the documentation.

Bug Fixes

    • #108 <https://github.com/IFCA/caso/issues/108>. Failure getting accounting data when using different domains.

4.1.0

New Features

  • Allow loading VO mapping directly from Keystone. Instead of mainitaining a separate file, we now allow users to load the VO directly from a configurable project property.

  • Allow to use Keystone project tags to get usages from projects.

Upgrade Notes

  • Now cASO defaults to all the installed default extractors, that are the OpenStack Compute (nova), Volume (cinder) and Network (neutron), publishing Cloud, Storage and IP records.

  • It is reccomended that you stop using the Keystone voms mapping file as soon as possible, please migrate your old JSON mapping to the new method using Keystone project’s properties. In order to do so, you can use the caso-mapping-migrate command line option, that will provide you with the correct commands to run to perform the migration.

  • If using tags to gather the list of projects you need to ensure that the correct roles and system scopes are applied. Please ensure that the correct roles are defined, as indicated in the configuration documentation.

Deprecation Notes

  • The VO mapping file is now deprecated, in favour of project properties.

4.0.0

New Features

  • Allow to load more than one extractor in the configuration, making possible to get more than one type of record.

  • Add support for the EMI STaR records for storage, and support extracting records from OpenStack Cinder.

3.0.0

New Features

  • Add support for GPU accounting, using the GPU 0.1 record agreed with APEL.

Upgrade Notes

  • Please ensure that you have the correct configuration in the policy files, as a new policy rule must be modified. The accounting user does not need to have access to the “identity:list_users” action, but to the “identity:get_user” action instead.

Deprecation Notes

  • All the benchmark_* and accelerator_ option definitions in the [DEFAULT] section of the configuration file have been marked as deprecated, and are now included in the individual [benchmark] and [acelerator] sections, with the corresponding prefix (i.e. benchmark_ and accelerator_) removed. Check the sample configuration file for more details.

Bug Fixes

  • Fix an issue when getting the usernames, that caused configuration errors to be unnoticed.

Other Notes

  • Keystone versions from Ussuri onwards (>= 17.0.0) implement a new policy. Please check the documentation so as to ensure that you are applying the correct changes.

2.1.0

Prelude

This version includes a refactoring of the base extractors, dropping support for the ceilometer extractor that was unmaintained for a long period of time.

Upgrade Notes

  • Ceilometer extractor is no longer supported.

2.0.0

Prelude

Starting with this version cASO release notes are published within the documentation. This version is a major release that implements IP accounting record, as well as several bugfixes. There are no upgrade notes to take into account.

New Features

  • Add multi-region support in order to extract information from several regions through different configuration files.

  • New IP accounting record is implemented. Now cASO is able to extract IP accounting and publish it using its JSON rendering. No new configuration needs to be done, but the cASO user needs to have access to the Neutron endpoints.

  • cASO now allows to specity the projects to extract records from as project IDs, rather than names. When dealing with different identity domains this is troublesome, therefore we need to allow users to specify project IDs rather than names.

Bug Fixes

  • Define the correct entrypoints for the V2 and V4 messengers.

  • Generate LOG warnings when mappings cannot be found.