openstack/cloudkitty
Code Issues Proposed changes
Rating service for OpenStack
139 Commits 10 Branches 79 Tags 14 MiB
Python 96.5%
Shell 2%
PHP 0.6%
HTML 0.5%
Mako 0.4%
fef8344f33
Go to file
Stéphane Albert fef8344f33 Added support for rating module priority 
Rating modules are now sorted based on a priority number. The modules
with the highest priority are loaded first.
Added API calls to set the priority of a module.

Change-Id: I84d9f6c31014c3164e5b7d8efdd3c909e342df96
2015-04-20 11:08:59 +02:00
cloudkitty Added support for rating module priority 2015-04-20 11:08:59 +02:00
contrib Merge "Update the devstack lib and documentation" 2015-03-05 08:31:37 +00:00
doc Renaming billing to rating 2015-04-08 16:07:25 +02:00
etc Renaming billing to rating 2015-04-08 16:07:25 +02:00
.gitignore Repository general files update 2014-11-19 09:56:55 +00:00
.gitreview Added .gitreview 2014-05-22 00:52:17 +00:00
.testr.conf Move the tests in the cloudkitty package 2014-09-26 15:33:33 +02:00
LICENSE Set copyright/license information in .py files 2014-06-07 09:14:06 +02:00
openstack-common.conf Implemented RPC messaging 2014-09-05 10:33:26 +02:00
README.rst Renaming billing to rating 2015-04-08 16:07:25 +02:00
requirements.txt Use keystone middleware for authentication 2015-03-06 17:56:45 +01:00
setup.cfg Renaming billing to rating 2015-04-08 16:07:25 +02:00
setup.py Pushing initial work 2014-05-30 19:37:53 +02:00
test-requirements.txt New HashMap rating module version 2015-03-16 15:32:23 +01:00
tox.ini Added support for rating module priority 2015-04-20 11:08:59 +02:00

README.rst

CloudKitty

OpenStack Rating and Usage Reporter

Goal

The goal of this project is to automate the extraction of the metrics from ceilometer, map them to rating informations and generate reports.

Status

This project is highly work in progress. Most of the work that we've done was targeted to quickly create a POC. We are now aiming towards the creation of an OpenStack module. Changes needed to attain our goal are huge, that's why the time between commits can be long.

Roadmap

  • Create a project API to manage the configuration of rating modules and request informations.
  • Every rating module should be able to expose its own API.
  • Move from importutils to stevedore.
  • Scheduling of rating calculations
  • Better collection of ceilometer metrics (Maybe Gnocchi)
  • Global code improvement

In a possible future :

  • Spawning of instances to do the calculations