We need to specify doc requirements in doc/requirements.txt to avoid problems with the pip resolver  for the release team . Removed specific doc requirements from test-requirements.txt. The problem here is that this repos haven't doc/requirements.txt file and by default in this case zuul will use the test-requirements.txt file to pull requirements . This requirements file contains extra requirements like flake8 that collided with those allowed in our job environment and so the new pip resolver fails to install these requirements and the job exits in error. This project meet the conditions leading to the bug.  http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html  http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html  http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html  https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36 Change-Id: I6bdfa9830a32ecf36e1931e1bb0afa366f1dfeb9
|1 week ago|
|cloudkitty||3 weeks ago|
|contrib||5 months ago|
|devstack||1 year ago|
|doc||1 week ago|
|etc||4 months ago|
|releasenotes||3 weeks ago|
|.gitignore||2 years ago|
|.gitreview||1 year ago|
|.stestr.conf||2 years ago|
|.zuul.yaml||3 months ago|
|HACKING.rst||2 years ago|
|LICENSE||6 years ago|
|README.rst||2 years ago|
|lower-constraints.txt||1 month ago|
|requirements.txt||1 month ago|
|rtd-requirements.txt||2 years ago|
|setup.cfg||4 months ago|
|setup.py||10 months ago|
|test-requirements.txt||1 week ago|
|tox.ini||1 week ago|
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.
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.
Release notes can be found in the release notes section of the documentation.