Record the utilization of OpenStack resources for each tenant
Go to file
Frédéric Guillot 13d383a50c Rename exception class to be consistent with the code base
Change-Id: Iffcfad802a1e588ed3886f9573ddaec675b82d55
2016-10-12 08:59:24 -04:00
almanach Rename exception class to be consistent with the code base 2016-10-12 08:59:24 -04:00
devstack Add devstack plugin 2016-09-09 16:48:08 -04:00
doc/source Generate api documentation using sphinx and autoflask 2016-10-07 14:25:43 -04:00
integration_tests Clean imports in code 2016-08-25 17:14:29 -04:00
tests Rename exception class to be consistent with the code base 2016-10-12 08:59:24 -04:00
.gitignore Make project compatible with OpenStack CI 2016-08-15 10:17:51 -04:00
.gitreview Make project compatible with OpenStack CI 2016-08-15 10:17:51 -04:00
docker-compose-integration-tests.yml Added integration tests with Docker (#17) 2016-05-19 16:06:02 -04:00
docker-compose.yml Modify api to support edition of closed entity 2016-05-18 12:05:09 -04:00
docker-entrypoint.sh Modify api to support edition of closed entity 2016-05-18 12:05:09 -04:00
Dockerfile Add compatibility to python3 2016-08-22 17:47:19 -04:00
Dockerfile.integration-tests Added integration tests with Docker (#17) 2016-05-19 16:06:02 -04:00
integration-test-requirements.txt Added integration tests with Docker (#17) 2016-05-19 16:06:02 -04:00
LICENSE First opensource commit 2016-03-25 11:30:58 -04:00
README.rst Convert Markdown to reStructuredText format 2016-08-17 17:11:52 -04:00
requirements.txt Add compatibility to python3 2016-08-22 17:47:19 -04:00
setup.cfg Fix gate docs-ubuntu-xenial 2016-09-21 18:01:15 -04:00
setup.py flake8 now automated (#5) 2016-04-15 07:49:15 -04:00
test-requirements.txt Generate api documentation using sphinx and autoflask 2016-10-07 14:25:43 -04:00
tox-integration.ini Split and add new integration tests (#20) 2016-05-31 12:09:35 -04:00
tox.ini Generate api documentation using sphinx and autoflask 2016-10-07 14:25:43 -04:00

Almanach

image

Almanach stores the utilization of OpenStack resources (instances and volumes) for each tenant.

What is Almanach?

The main purpose of this software is to bill customers based on their usage of the cloud infrastructure.

Almanach is composed of two parts:

  • Collector: Listen for OpenStack events and store the relevant information in the database.
  • REST API: Expose the information collected to external systems.

Resources

Launchpad Projects

Blueprints

Bug Tracking

License

Almanach is distributed under Apache 2.0 LICENSE.