Bug 999799 - Network QoS burst units should be MB
Summary: Network QoS burst units should be MB
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.0
Assignee: Doron Fediuck
QA Contact: GenadiC
URL:
Whiteboard: sla
Depends On:
Blocks: 1019461
TreeView+ depends on / blocked
 
Reported: 2013-08-22 07:28 UTC by ofri
Modified: 2016-02-10 20:15 UTC (History)
9 users (show)

Fixed In Version: is12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 22:13:50 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 18395 0 None None None Never
oVirt gerrit 18398 0 None None None Never

Description ofri 2013-08-22 07:28:05 UTC 
Description of problem:
The units of the network QoS 'Burst' property should always be in Mega-Bytes, not Mega-bits.

Version-Release number of selected component (if applicable):


How reproducible:
100%


Additional info:
need to be fixed in UI
Comment 1 ofri 2013-08-22 07:44:17 UTC 
Adding to this bug:

- the translation of QoS units from the engine to vdsm is wrong. 
current translation is Mb --> Kb
should be              Mb --> KB (since vdsm works in kilobytes)
Comment 2 GenadiC 2013-08-29 09:47:49 UTC 
The value is MiB when it should be MB
Comment 3 ofri 2013-09-02 05:54:32 UTC 
according to Wikipedia: 
Mebibyte (MiB) - 2^20 Byte (1024 Kibibyte)
Megabyte (MB) - three different values depending on context: 
   2^20 bytes generally for computer memory
   one million bytes generally for computer storage or transmission rates
   and in rare cases 1000×1024 (1024000) bytes

I think Mib is less ambiguous and there for better.
Comment 6 Itamar Heim 2014-01-21 22:13:50 UTC 
Closing - RHEV 3.3 Released
Comment 7 Itamar Heim 2014-01-21 22:21:37 UTC 
Closing - RHEV 3.3 Released
Note You need to log in before you can comment on or make changes to this bug.