Rating service for OpenStack
Go to file
Stéphane Albert 34390d5308 Updated requirements to stable/kilo
Change-Id: I96114c8a9b2fb684be82d5edd6427c53e7ca9921
2015-06-09 16:53:10 +02:00
cloudkitty Sync oslo modules 2015-06-09 08:52:06 +02:00
contrib Changed network bandwidth from B to MB 2015-05-13 23:29:19 +02:00
devstack Fixed dashboard installation with devstack 2015-05-13 00:21:02 +02:00
doc doc: enable ceilometer and horizon in devstack 2015-05-26 16:10:08 +02:00
etc Make keystone optional 2015-05-26 16:17:27 +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
README.rst Renaming billing to rating 2015-04-08 16:07:25 +02:00
requirements.txt Updated requirements to stable/kilo 2015-06-09 16:53:10 +02:00
setup.cfg Added a fake fetcher and collector 2015-05-13 21:06:17 +02:00
setup.py Updated requirements to stable/kilo 2015-06-09 16:53:10 +02:00
test-requirements.txt Updated requirements to stable/kilo 2015-06-09 16:53:10 +02: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