openstack
/
cloudkitty
Code Issues Proposed changes
Rating service for OpenStack
128 Commits 9 Branches 75 Tags 13 MiB
Python 96.3%
Shell 2.2%
PHP 0.6%
HTML 0.5%
Mako 0.4%
Go to file
Gauvain Pocentek bc0d3827b5 Generate the sample with oslo-config-generator 
Change-Id: I38ebc1843730970e6e62d040e8558b533ed479b7
 		2015-03-06 17:52:59 +01:00
cloudkitty Generate the sample with oslo-config-generator 2015-03-06 17:52:59 +01:00
contrib Merge "Update the devstack lib and documentation" 2015-03-05 08:31:37 +00:00
doc Merge "Provide an installation documentation" 2015-03-02 08:34:28 +00:00
etc Generate the sample with oslo-config-generator 2015-03-06 17:52:59 +01: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 Fixed typo in README 2014-07-09 12:00:28 +02:00
openstack-common.conf Implemented RPC messaging 2014-09-05 10:33:26 +02:00
requirements.txt Added multi-tenancy support 2015-02-10 12:01:47 +01:00
setup.cfg Generate the sample with oslo-config-generator 2015-03-06 17:52:59 +01:00
setup.py Pushing initial work 2014-05-30 19:37:53 +02:00
test-requirements.txt Modified utils to implement all time calculations 2014-11-24 14:45:19 +01:00
tox.ini Generate the sample with oslo-config-generator 2015-03-06 17:52:59 +01:00

README.rst

CloudKitty

OpenStack Billing and Usage Reporter

Goal

The goal of this project is to automate the extraction of the metrics from ceilometer, map them to billing 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 billing modules and request informations.
  • Every billing module should be able to expose its own API.
  • Move from importutils to stevedore.
  • Scheduling of billing calculations
  • Better collection of ceilometer metrics (Maybe Gnocchi)
  • Global code improvement

In a possible future :

  • Spawning of instances to do the calculations