almanach/doc/source/index.rst

Welcome to the Almanach documentation!

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

What is Almanach?

The main purpose of this software is to record the usage of the cloud resources of each tenants.

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.

Requirements

• OpenStack infrastructure installed (Nova, Cinder...)
• MongoDB
• Python 2.7, 3.4 or 3.5

Generate config file with default values

tox -e genconfig

Command line usage

Start the API daemon:

almanach-api --config-file /etc/almanach/almanach.conf

Start the collector:

almanach-collector --config-file /etc/almanach/almanach.conf

Signal Handling

• SIGINT: force instantaneous termination
• SIGTERM: graceful termination of the service
• SIGHUP: reload service

Authentication

Protocol

The authentication mechanism use the HTTP header X-Auth-Token to send a token. This token is validated through Keystone or with the config file (private secret key).

:: code:: raw

GET /volume_types HTTP/1.1 X-Auth-Token: secret Content-Type: application/json

{}

If the token is not valid, you will receive a 401 Not Authorized response.

Private Key Authentication

The private secret key authentication is the default method. In your config file, you have to define your private key in the field auth_token:

:: code:: raw

[auth] strategy = private_key private_key = secret

Keystone Authentication

The token will be validated with Keystone. To use this authentication backend you have to define the authentication strategy to keystone.

:: code:: raw

[auth] strategy = keystone keystone_username = my_service_username keystone_password = my_service_password keystone_url = http://keystone_url:5000/v3

RabbitMQ configuration

Each OpenStack services (Nova, Cinder, Neutron) need to be configured to send notifications to the Almanach queue.

For example with Nova, add the topic "almanach" in the config file /etc/nova.conf:

notification_topics=almanach

MongoDB configuration

Almanach requires a specific user to connect to the database. To create a new user, open a new MongoDB shell:

m = new Mongo()
m.getDB("almanach").createUser({user: "almanach", pwd: "almanach", roles: [{role: "readWrite", db: "almanach"}]})

Devstack configuration

[[local|localrc]]
ADMIN_PASSWORD=secret
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD

enable_plugin almanach https://git.openstack.org/openstack/almanach

Database entities

Each entity have at least these properties:

• entity_id: Unique id for the entity (UUID)
• entity_type: "instance" or "volume"
• project_id: Tenant unique ID (UUID)
• start: Start date of the resource usage
• end: End date of the resource usage or null if the resource still in use by the tenant
• name: Resource name

Compute Object

{
    "entity_id": "UUID",
    "entity_type": "instance",
    "project_id": "UUID",
    "start": "2014-01-01T06:00:00.000Z",
    "end": null,
    "last_event": "2014-01-01T06:00:00.000Z",
    "flavor": "MyFlavor1",
    "os": {
        "distro": "ubuntu",
        "version": "14.04"
    },
    "name": "my-virtual-machine.domain.tld"
}

Block Storage Object

{
    "entity_id": "UUID",
    "entity_type": "volume",
    "project_id": "UUID",
    "start": "2014-01-01T06:00:00.000Z",
    "end": null,
    "last_event": "2014-01-01T06:00:00.000Z",
    "volume_type": "MyVolumeType",
    "size": 50,
    "name": "my-virtual-machine.domain.tld-volume",
    "attached_to": "UUID"
}

List of events handled

Almanach will process those events:

• compute.instance.create.end
• compute.instance.delete.end
• compute.instance.resize.confirm.end
• compute.instance.rebuild.end
• volume.create.end
• volume.delete.end
• volume.resize.end
• volume.attach.end
• volume.detach.end
• volume.update.end
• volume.exists
• volume_type.create

API documentation

almanach.api.main:app