Dedicated database for the alarm part of ceilometer
Currently if we use mongodb for storing metering data, we are forced to use mongodb
for storing event and alarm.
The blueprint propose to allow to have a different database for alarm.
Blueprint information
- Status:
- Complete
- Approver:
- Eoghan Glynn
- Priority:
- High
- Drafter:
- Mehdi Abaakouk
- Direction:
- Approved
- Assignee:
- Mehdi Abaakouk
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Mehdi Abaakouk
- Completed by
- Eoghan Glynn
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Allow to have different DB for alarm and metering
Gerrit topic: https:/
Addressed by: https:/
Splits hbase storage code base
Addressed by: https:/
Separate alarm storage models from other models
Addressed by: https:/
Splits mongo storage code base
Addressed by: https:/
Allow to have different DB for alarm and metering
Addressed by: https:/
Move mongodb/db2 alarms driver code to alarm tree
Addressed by: https:/
Move log alarms driver code to alarm tree
Addressed by: https:/
Move hbase alarms driver code to alarm tree
Addressed by: https:/
Move sqlalchemy alarms driver code to alarm tree
Addressed by: https:/
Remove ConnectionProxy temporary class
Addressed by: https:/
Allows to share engine between both sql driver
Bumped to juno-3, as gating issues prevented the approved patches from landing in time.
