Alarm history is not supported with the sqlalchemy driver

Bug #1221855 reported by Eoghan Glynn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Fix Released
Medium
Eoghan Glynn

Bug Description

Accessing the alarm history API when the sqlalchemy storage driver is configured fails with not a NotImplementedError.

(The alarm history is currently fully implemented for the mongodb driver only).

Eoghan Glynn (eglynn)
Changed in ceilometer:
milestone: none → havana-rc1
status: New → Confirmed
status: Confirmed → In Progress
importance: Undecided → Medium
assignee: nobody → Eoghan Glynn (eglynn)
Revision history for this message
Eoghan Glynn (eglynn) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ceilometer (master)

Reviewed: https://review.openstack.org/45244
Committed: http://github.com/openstack/ceilometer/commit/e393935eda4fa9f4d560d3710826f79ab0b876d7
Submitter: Jenkins
Branch: master

commit e393935eda4fa9f4d560d3710826f79ab0b876d7
Author: Eoghan Glynn <email address hidden>
Date: Thu Sep 5 10:30:29 2013 +0000

    Alarm history storage implementation for sqlalchemy

    Fixes bug 1221855

    Test coverage is provided by the alarm scenario tests
    included in a prior patch.

    Related to bp alarm-audit-api

    Change-Id: If0121459a21135a3bf0951470fec49aa4ddef5d1

Changed in ceilometer:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in ceilometer:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in ceilometer:
milestone: havana-rc1 → 2013.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.