By default not even an admin can use the get_summary endpoint with all_tenants=True or using a tenant_id parameter. This commit fixes that. This rule is now the same as how cinder defines admin_or_owner. Change-Id: I3e34927e8ab88f25d2975b4dbac89b52a7d94c98 (cherry picked from commit
|10 months ago|
|cloudkitty||9 months ago|
|contrib||1 year ago|
|devstack||2 years ago|
|doc||9 months ago|
|etc||3 years ago|
|releasenotes||1 year ago|
|.gitignore||4 years ago|
|.gitreview||1 year ago|
|.stestr.conf||4 years ago|
|.zuul.yaml||9 months ago|
|HACKING.rst||3 years ago|
|LICENSE||8 years ago|
|README.rst||3 years ago|
|lower-constraints.txt||1 year ago|
|requirements.txt||1 year ago|
|rtd-requirements.txt||3 years ago|
|setup.cfg||1 year ago|
|setup.py||2 years ago|
|test-requirements.txt||1 year ago|
|tox.ini||1 year ago|
Team and repository tags
Rating as a Service component
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.
CloudKitty has been successfully deployed in production on different OpenStack systems.
You can find the latest documentation on readthedocs.
We are welcoming new contributors, if you've got new ideas, suggestions or want to contribute contact us.
A storyboard is available if you need to report bugs.
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.
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.