PersonalHomepage

Launchpad Entry: GlanceSpec:server-templates
Created: 28 Sep 2011
Contributors: Glen Campbell

Summary

Nova administrators want data on system usage for billing, chargeback, or monitoring purposes.

Release Note

This paper is based on "System Usage Data" http://wiki.openstack.org/SystemUsageData implemented for Essex realease.

We are planning to implement this features for Folsom

Rationale

The best way to gather this data is from a notifications system based on AMQP queues (RabbitMQ messaging System).

Then the main challenge of this BluePrint is to define the most useful events to be transmitted from OpenStack subsystems to AMQP queues. In order to be consumed by billing, chargeback or monitoring systems.

User stories

Design

There are two events generated for every activity <activity>.start and <activity>.end. The "start" one specifies the beginning of the activity, and the "end" one specifies the success of the activity.

The Events resources are the objects in the platform that we are interested to scan:

Instances
* Memory increase/decrease
* Disk increase/decrease
* Image mounted
* BW consumed
Volumes
* Created/deleted
* Attached/detached
Images:
* Created/Deleted
Floating IPs
* Associated/dissasociated (to an instance)
* Allocated/released (by a user/tenant)
Snapshots
Fixed Networks
Tenants
Users
Inbound traffic
Outbound traffic

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

data migration, if any
redirects from old URLs to new ones, if any
how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.