bac1960330
This patch proposes a method for operators to customize the aggregation query executed against Gnocchi. By default, we use the following query: (aggregate RE_AGGREGATION_METHOD (metric METRIC_NAME AGGREGATION_METHOD)) Therefore, this option enables operators to take full advantage of operations available in Gnocchi, such as any arithmetic operations, logical operations and many others. When using a custom aggregation query, one can use the placeholders `RE_AGGREGATION_METHOD`, `AGGREGATION_METHOD`, and `METRIC_NAME`: they will be replaced at runtime by values from the metric configuration. Different use cases can be addressed with the use of custom queries such as handling RadosGW usage data trimming, which causes a decrease in the usage data values; Libvirt attach/detach of disks, migration of VMs, start/stop of VMs, which will zero the usage data that are gathered by Ceilometer compute, and many other use cases where one might desire a more complex operation to be executed on the data before CloudKitty rates it. Change-Id: I3419075d6df165409cb1375ad11a5b3f7faa7471 |
||
|---|---|---|
| cloudkitty | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc | ||
| releasenotes | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| lower-constraints.txt | ||
| README.rst | ||
| requirements.txt | ||
| rtd-requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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 @ oftc.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.