compute counter units are not accurate/consistent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
High
|
Unassigned | ||
Grizzly |
Fix Released
|
High
|
Eoghan Glynn |
Bug Description
relating to comments here: https:/
in compute counters we return unit as B but they are really either MB or GB... only in notes can you tell this. also, in resource_metadata, the items are returned in lowercase which i would assume means bits not bytes (this isn't that important)
"resource_
"host": "c1901948957087
"name": "instance-
},
in network counters pollster version of ip.floating* meters have 'ip' unit while notification version has 'floatingip' unit... not sure which is right but i would think one of them is wrong.
summary: |
- counter units are not accurate/consistent + compute counter units are not accurate/consistent |
Changed in ceilometer: | |
assignee: | gordon chung (chungg) → nobody |
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in ceilometer: | |
importance: | Undecided → High |
Changed in ceilometer: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | havana-1 → 2013.2 |
happy to take a look at this, if someone can confirm they are valid and what the expected values are.