Aodh don't need to support precise timestamp which strongly depens on sql>=5.6
Bug #1649484 reported by
Liusheng
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Aodh |
Won't Fix
|
Undecided
|
Liusheng | ||
Bug Description
Devstack with Aodh enabled maybe installed failed because version of sql < 5.6, that is because change[1] need sql>=5.6 support. The change[1] replaced the native implementation of PreciseTimestamp type of sql, but alarm data don't need precise timestamp, like most of other resources(e.g. servers, image, networks), the normal DataTime time is enough, and that will reduce the dependency of sql version.
Revision history for this message
| Julien Danjou (jdanjou) wrote | #1 |
| Changed in aodh: | |
| status: | New → Opinion |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to aodh (master) | #2 |
| Changed in aodh: | |
| assignee: | nobody → Liusheng (liusheng) |
| status: | Opinion → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on aodh (master) | #3 |
| Changed in aodh: | |
| status: | In Progress → Won't Fix |
To post a comment you must log in.
This seems reasonable, though I wonder if it's not useful to have good precision in order to be able to link timestamp and events in a fine grained manner.