059a940392
This patch provides a refactoring of the metric configuration model (and file description) to improve genericity, maintainability and usage for non-openstack deployment. The new metric yaml format is defined in the attached story task and is validated on load with voluptuous. Now, a processor is dedicated to one collector and one storage backend. Thus, collector and storage configuration go back to the cloudkitty oslo conf. Collectors have been refactored to have a code as similar as possible, in order to ease comprehension for new contributors. Story: 2001883 Task: 14354 Task: 14355 Task: 14431 Change-Id: I948dd9cd5c113bdaa4e49c532354938ffb45f0e7
Team and repository tags
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-dev@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.