Rating service for OpenStack
Go to file
Stéphane Albert a5961cff80 Added support for dashboard in devstack
Moved to devstack plugin.
Added section in the documentation related to CloudKitty's devstack
integration.

Change-Id: I9a7ce8c73724a54fb7855d788a1c4cb56a832535
2015-05-12 19:20:14 +02:00
cloudkitty Merge "Added new mapping type: threshold" 2015-05-07 07:40:56 +00:00
contrib Added support for dashboard in devstack 2015-05-12 19:20:14 +02:00
devstack Added support for dashboard in devstack 2015-05-12 19:20:14 +02:00
doc Added support for dashboard in devstack 2015-05-12 19:20:14 +02:00
etc Fix the config sample generator method 2015-05-06 09:53:53 +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 Add ACL support on the API 2015-05-05 11:36:01 +02:00
setup.cfg Added support for pluggable tenant fetcher 2015-04-30 11:51:35 +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

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