precision of floating point metering stats is discarded unnecessarily
Bug #1241467 reported by
Eoghan Glynn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Eoghan Glynn | ||
Havana |
Fix Released
|
Medium
|
Eoghan Glynn |
Bug Description
Ceilometer returns aggregated statistical values as float, whereas the 'resource usage' panel narrows to int before inserting these data into the line chart.
For meters defined over a narrow range (such as cpu_util ranging from 0.0% to 100.0%) this has the effect of unnaturally smoothening the graph by discarding precision.
If it really was crucial that the line chart contain only ints, then the float->int conversion should be a round:
i = int(round(f, 0))
as opposed to narrowing cast:
i = int(f)
However, AFAICS there's no reason why these raw data couldn't be represented directly as floats in the line chart.
Changed in horizon: | |
assignee: | nobody → Eoghan Glynn (eglynn) |
status: | New → In Progress |
tags: | added: havana-backport-potential |
Changed in horizon: | |
importance: | Undecided → Medium |
Changed in horizon: | |
milestone: | none → icehouse-1 |
tags: | added: metering-ui |
tags: | removed: havana-backport-potential |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/52603
Review: https:/