Rating service for OpenStack
Go to file
Hervé Beraud 3668a76fe4 Stop to use the __future__ module.
The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: I74f1cce5430d81aa7dad08920baa9d771271f871
2020-08-13 09:44:17 +00:00
cloudkitty Stop to use the __future__ module. 2020-08-13 09:44:17 +00:00
contrib Removing author identification in all files 2019-07-22 12:21:54 +00:00
devstack Merge "Replace deprecated devstack authtoken function" 2019-09-24 14:17:50 +00:00
doc Fix docs build error due to duplicate references 2020-06-24 16:56:51 -05:00
etc Merge "Update the default metrics.yml file" 2019-04-02 10:43:51 +00:00
releasenotes Update master for stable/ussuri 2020-06-24 22:55:24 +00:00
.gitignore Switch to stestr 2018-07-18 08:00:06 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:29:58 +00:00
.stestr.conf Switch to stestr 2018-07-18 08:00:06 +07:00
.zuul.yaml [ussuri][goal] Drop python 2.7 support and testing 2019-11-16 14:35:39 +00:00
HACKING.rst Adds doc8 check to pep8 2018-10-22 11:14:57 +02:00
LICENSE Set copyright/license information in .py files 2014-06-07 09:14:06 +02:00
README.rst Changed author email 2018-12-06 09:45:17 +01:00
lower-constraints.txt tox: Keeping going with docs 2019-12-19 15:21:01 +08:00
requirements.txt [ussuri][goal] Cleanup drop python 2.7 support 2020-02-24 20:16:56 +01:00
rtd-requirements.txt Bump the openstackdocstheme extension to 1.20 2018-08-21 13:54:06 +00:00
setup.cfg [ussuri][goal] Cleanup drop python 2.7 support 2020-02-24 20:16:56 +01:00
setup.py [ussuri][goal] Cleanup drop python 2.7 support 2020-02-24 20:16:56 +01:00
test-requirements.txt [ussuri][goal] Cleanup drop python 2.7 support 2020-02-24 20:16:56 +01:00
tox.ini Fix docs build error due to duplicate references 2020-06-24 16:56:51 -05:00

README.rst

Team and repository tags

image

CloudKitty

cloudkitty

Rating as a Service component

Goal

CloudKitty aims at filling the gap between metrics collection systems like ceilometer and a billing system.

Every metrics are collected, aggregated and processed through different rating modules. You can then query CloudKitty's storage to retrieve processed data and easily generate reports.

Most parts of CloudKitty are modular so you can easily extend the base code to address your particular use case.

You can find more information on its architecture in the documentation, architecture section.

Status

CloudKitty has been successfully deployed in production on different OpenStack systems.

You can find the latest documentation on readthedocs.

Contributing

We are welcoming new contributors, if you've got new ideas, suggestions or want to contribute contact us.

You can reach us thought IRC (#cloudkitty @freenode.net), or on the official OpenStack mailing list openstack-discuss@lists.openstack.org.

A storyboard is available if you need to report bugs.

Additional components

We're providing an OpenStack dashboard (Horizon) integration, you can find the files in the cloudkitty-dashboard repository.

A CLI is available too in the python-cloudkittyclient repository.

Trying it

CloudKitty can be deployed with devstack, more information can be found in the devstack section of the documentation.

Deploying it in production

CloudKitty can be deployed in production on OpenStack Kilo environments, for more information check the installation section of the documentation. Due to oslo libraries new namespace backward compatibility is not possible. If you want to install it on an older system, use a virtualenv.

Getting release notes

Release notes can be found in the release notes section of the documentation.