3c3af85ac3
Currently in master, cloudkitty is leaking the build hostname in the cloudkitty.conf file when generating it. This makes the entire package no reproducible. This patch adds a sample_default= argument when defining host=, so that the default value when generating the config file is *not* the hostname of the build host. This doesn't change at all the behavior, which will use the hostname FQDN if the value isn't set by the user. Change-Id: I59eb50018dd895f40ff949123c4ab78360c74850 |
||
---|---|---|
cloudkitty | ||
contrib | ||
devstack | ||
doc | ||
etc | ||
playbooks/cloudkitty-tempest-full | ||
releasenotes | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
.zuul.yaml | ||
HACKING.rst | ||
LICENSE | ||
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 @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.