Description of problem: [Rest] - Wrong current rx/tx rate reported in the Rest API. Rest API display wrong values for the current rx/tx rates. For example, i'm running iperf between 2 physical hosts, the tx rate is 984Mbps, UI shows 984 and report correct value, but rest api shows - 120000000 in bytes per second, which means after converting - 120 megabyte per second. <name>data.current.tx</name> <description>Transmit data rate</description> <kind>gauge</kind> <type>decimal</type> <unit>bytes_per_second</unit> <values> <value> <datum>120000000</datum> </value> </values> - Please note that only the current tx/rx values are wrong, the 'total' tx/rx seems to be OK. Version-Release number of selected component (if applicable): 4.1.7.4-0.1.el7 4.2.0-0.0.master.20171022103432.gitaf9d8b6.el7.centos How reproducible: 100% Steps to Reproduce: 1. Run iperf between 2 physical hosts 2. Check the current tx rate reported in the UI and in rest API Actual results: Rest API shows wrong current tx/rx values. UI shows correct values. Expected results: Rest should show correct values. Looks like rest has a limit of 120000000 bytes per second.
I have checked it and it seems like everything is correct. In your case REST is reporting 120000000Bps which is 960Mbps (converting Bytes to Bits). That means difference about ~25Mbps. This difference is caused by slight delay. REST has newer values than UI. It's true that it is confusing both UI and REST should report their values in either bps or Bps. We can change the REST values to bps, what do you think?
Ok i see now, REST report 120000000Bps which is: 120 - megabyte per second (MB/s) 960 - megabit per second (Mbps) , and from here is the whole confusion, Bytes vs Bits. I agree this is extremely confusing, i think that REST should report bps indeed in order to avoid such confusion, specially if the UI report in Mbps.
I agree that <unit>bits_per_second</unit> would be better.
We cannot change the units of data.current.tx/rx but we have added new value which is data.current.tx/rx.bps in bit per second.
Verified on - 4.2.0-0.0.master.20171108151837.gita7de53e.el7.centos Rest now report both data.current.tx/rx and data.current.tx/rx.bps which make it much more easier to understand what is actually reported in the rest. <name>data.current.rx</name> <description>Receive data rate</description> <kind>gauge</kind> <type>decimal</type> <unit>bytes_per_second</unit> <values> <value> <datum>120000000</datum> </value> </values> <name>data.current.rx.bps</name> <description>Receive data rate</description> <kind>gauge</kind> <type>decimal</type> <unit>bits_per_second</unit> <values> <value> <datum>960000000</datum> </value> </values> <name>data.current.tx</name> <description>Transmit data rate</description> <kind>gauge</kind> <type>decimal</type> <unit>bytes_per_second</unit> <values> <value> <datum>830000</datum> </value> </values> <name>data.current.tx.bps</name> <description>Transmit data rate</description> <kind>gauge</kind> <type>decimal</type> <unit>bits_per_second</unit> <values> <value> <datum>6600000</datum> </value> </values>
Hello, can we back-port this into next z stream release? Marian
Hello, we can backport it, but I am not sure if it related to the customer case. The bug name might be misleading a bit. There is no actual bug. We have added reporting in bps to prevent confusion in differences between REST and UI. Hopefully this explanation will help you. Ales
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.