Imported Translations from Transifex

Change-Id: I83e1eea98f5b10d3358a014a0f3a4dabc67ac57d
Remove compat cfg wrapper

This wrapper was there to allow oslo-config changes through the gate
while keystoneclient hadn't been updated.

Also update to 2013.1b4.

Change-Id: I3d48673af58ae379e8e4d2c7fb4b4d81f3ed67dd
Fix count type in MongoDB

This fixes some API tests ran with CEILOMETER_LIVE_TEST

Change-Id: I3c77ffb3b6287dd4efcf0afd6f437033acb5f2b7
Signed-off-by: Julien Danjou <julien@danjou.info>
Allow empty dict as metaquery param for sqlalchemy.

Corrected the test of metaquery param in sqlalchemy backend.

Fixed bug #1131620.

Change-Id: Ief7e78444b99f6e8a46bd634c9be12708e10b212
Add glossary definitions for additional terms

Add glossary definitions for the following: meter, project, resource, sample, source, user.

Fixes bug 1070382

Change-Id: I56120cafcdb6faa160724e7774c6e54a25e1bf43
Remove nose wrapper script

Change-Id: I8e244aa892ac66dddd1be96369dfb0e90cc1543d
Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
Initial implementation of ceilometer-alarm

The implemented use case is raising an alarm (i.e. executing something)
as soon as a cumulative counter is above or below a certain threshold.

Alarms are stored in alarms.json inside the config directory.

The result of the "statistic" during a "period" is compared
to the alarm "threshold" with the operator in "comparaison_operator"
field of the alarm.

the statistic is calculated with get_meter_statistics() of the storage
connection.

The criteria handled to check if the alarm threshold needs to be checked
for a meter are for now only:
- counter_name
- resource_id

When a alarm is triggered a shell script is executed, same things when the
alarm is untriggered

The used shell script are stored in fields "ok_action" and "alarm_action" of the
alarm description.

The alarm status stays in memory as long as the alarms aren't stored in a
persistante storage.

Change-Id: I2dfebc30a47576e83906a6d4011ce5d52041e901