aodh/ceilometer/storage
Mehdi Abaakouk 7533bc6ff6 Allow to have different DB for alarm and metering
This changes splits the internal DB API in two parts, alarm and metering.
It also adds a new configuration options to set a different database
for alarm than the 'metering' one.

Example:

 [database]
 connection = mongodb://localhost/ceilometer
 alarm_connection = mysql://localhost/ceilometer

This changes don't take care of the drivers storaged.
They will be splitted in later changes
The ceilometer.storage.ConnectionProxy object ensure that only alarm methods
are available when the namespace is the alarm one, same for the metering
namespace.

Partial implements blueprint dedicated-alarm-database

Change-Id: I1e118e4adc59ca5cd3781dbb18865818c3cc2300
2014-07-18 11:18:17 +02:00
..
hbase Merge "Fix typos in code comments & docstrings" 2014-07-17 09:31:40 +00:00
mongo Merge "Fix typos in code comments & docstrings" 2014-07-17 09:31:40 +00:00
sqlalchemy Fix H405 violations and re-enable gating 2014-07-01 13:41:27 +03:00
__init__.py Allow to have different DB for alarm and metering 2014-07-18 11:18:17 +02:00
base.py Allow to have different DB for alarm and metering 2014-07-18 11:18:17 +02:00
impl_db2.py Fix H405 violations and re-enable gating 2014-07-01 13:41:27 +03:00
impl_hbase.py Allow to have different DB for alarm and metering 2014-07-18 11:18:17 +02:00
impl_log.py Allow to have different DB for alarm and metering 2014-07-18 11:18:17 +02:00
impl_mongodb.py Fix H405 violations and re-enable gating 2014-07-01 13:41:27 +03:00
impl_sqlalchemy.py Allow to have different DB for alarm and metering 2014-07-18 11:18:17 +02:00
models.py Fix H405 violations and re-enable gating 2014-07-01 13:41:27 +03:00
pymongo_base.py Allow to have different DB for alarm and metering 2014-07-18 11:18:17 +02:00