Caso

We introduce a new option allowing to limit the outgoing message size. The `max_size` option will limit the number of messages, default is 100.

Commit 0058b6c introduced a bug in how we retrieve the records, since we introduced the "deleted" filter and this was filtering out all the instances that are not deleted.

In order to get accurate results, accounting records must be regenerated at sites, possibly month by month, like:

caso-extract --extract-from 2017-01-01 --extract-to 2017-01-31
caso-extract --extract-from 2017-02-01 --extract-to 2017-02-28
(...)

Bugfixes:

* 47 cASO only accounts for deleted VMs bug
* 44 tenant or project in voms.json documentation

Version 1.0.0 introduced support for reporting records that changed within a period, but calculation was not done properly as it only reported nodes that started and ended within that period. This changed cASO functionality as it stopped sending records that started before that date or ended after that date (i.e. those records were lost).

Sites running a 1.X.X version should republish their data. This can be done safely by using the `--extract-from` CLI option.

Enhancements:
- Underscored options (`--dry_run`, `--extract_from`, `--extract_to`) have been marked as deprecated and replaced with dashed ones (`--dry-run`, `--extract-from`, `--extract-to`).

Bugfixes:
- https://github.com/IFCA/caso/issues/35: Take nova pagination into account.

This is a bugfix release.
- https://github.com/IFCA/caso/issues/41 Properties in flavors need to be prefixed, therefore they have been renamed to "accounting:benchmark_name" and "accounting:benchmark_type".

This is a major release. Backwards compatibility in the functionality is assured (when using the `caso.messenger.ssm.SSMMessengerV02 messenger`), but configuration needs to be updated. cASO running with an old configuration may not work as expected. Users are requested to adapt their configuration file, check https://caso.readthedocs.io/en/stable/configuration.html for details.

This relase implements to major changes:

- Support for Keystone V3 authentication: cASO now relies on the official keystoneauth library. It can be configured to use any of the existing authentication plugins.
- Support for the new v0.4 of the accounting record (and an updated SSM messenger). Users willing to publish v0.4 of the accounting record are requested to use the caso.messenger.ssm.SSMMessengerV04 messenger.

And some minor changes (apart from bugfixing):

- tenants configuration option is deprecated in favour of projects.
- the v0.4 of the accounting record allows users to publish becnhmark information within each record. This is extracted from the flavor, via its propertiess (see https://caso.readthedocs.io/en/stable/configuration.html for more details).

The following fixes have been included: https://github.com/IFCA/caso/milestone/2?closed=1