8869de5282
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1], Tempest has defined the base job 'devstack-tempest-ipv6' (adding in Depends-On patch) which will deploy services on IPv6. This commit adds the new job 'cloudkitty-tempest-full-ipv6-only' run on gate which is derived from 'devstack-tempest-ipv6'. Verification structure will be: - 'devstack-IPv6' deploy the service on IPv6 - 'devstack-tempest-ipv6' run will verify the IPv6-only setting and listen address - 'cloudkitty-tempest-full-ipv6-only' will run the tests. Story: #2005477 Task: #35884 Depends-On: https://review.opendev.org/#/c/671231/ [1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html Change-Id: I214b410137e825b529f0bdc34fda74ed1df091ab
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-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.