Rating service for OpenStack
Go to file
Ghanshyam Mann d6154abbe1 Update gate jobs as per the 2025.1 cycle testing runtime
As per 2025.1 testing runtime[1], we need to test on Ubuntu
Noble (which will be taken care by depends-on tempest and devstack
patches to move base jobs to Noble) and at least single job to run on
Ubuntu Jammy (for smooth upgrade from previous releases).

This commit adds a new job to run on Jammy which can be removed
in future cycle when testing runtime test next version of Ubuntu
as default.

Depends-On: https://review.opendev.org/c/openstack/tempest/+/932156

[1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html

Change-Id: Ida3f01b386747732b08f034c83c5b27b05dc706a
2024-11-26 20:15:00 +00:00
api-ref/source Add rating modules PUT endpoint to v2 API 2024-04-15 14:33:28 +00:00
cloudkitty Drop workaround for old setuptools 2024-11-26 14:52:11 +09:00
contrib Update hacking for Python3 2020-08-18 22:27:09 -03:00
devstack Drop workaround for old setuptools 2024-11-26 14:52:11 +09:00
doc Merge "Add rating modules PUT endpoint to v2 API" 2024-05-13 11:58:47 +00:00
etc Include /v2 in public routes for keystone auth 2022-03-10 17:31:51 +11:00
releasenotes Correct release note formatting 2024-10-21 13:03:09 +00:00
.gitignore Introduce reprocessing API 2022-02-25 14:49:49 +01:00
.gitreview OpenDev Migration Patch 2019-04-19 19:29:58 +00:00
.stestr.conf Switch to stestr 2018-07-18 08:00:06 +07:00
.zuul.yaml Update gate jobs as per the 2025.1 cycle testing runtime 2024-11-26 20:15:00 +00:00
CONTRIBUTING.rst [ussuri][goal] Update contributor documentation 2021-05-18 10:03:01 +02:00
HACKING.rst Replace deprecated assertRaisesRegexp 2022-06-27 00:28:14 +09:00
LICENSE Set copyright/license information in .py files 2014-06-07 09:14:06 +02:00
README.rst Update README content 2024-04-15 15:51:57 +02:00
requirements.txt Merge "Add requests to requirements" 2024-02-19 16:03:51 +00:00
setup.cfg Removal of Monasca fetcher and collector 2024-02-14 08:59:28 -03:00
setup.py [ussuri][goal] Cleanup drop python 2.7 support 2020-02-24 20:16:56 +01:00
test-requirements.txt Bump hacking minimum version to 6.1.0 2024-06-10 16:35:34 +02:00
tox.ini Remove the manual patch for WSME 2023-09-21 15:45:50 -03:00

Team and repository tags

image

CloudKitty

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 documentation.

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 environments, for more information check the installation section of the documentation.

Getting release notes

Release notes can be found in the release notes section of the documentation.

Contributing to CloudKitty

For information on how to contribute to CloudKitty, please see the contents of the CONTRIBUTING.rst.

Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.