Created attachment 940406[details]
Screenshot and logs from engine and vdsm
Description of problem:
When creating a new rule of storage blkio QOS, the presented units are in Mbps which are Mega bits per seconds.
Examing the XML request passed to VDSM after allocating a disk to the new rule in the log, shows that the the usnits are in bytes per second.
Version-Release number of selected component (if applicable):
rhev3.5 vt3.1
rhevm-3.5.0-0.12.beta.el6ev.noarch
How reproducible:
Always
Steps to Reproduce:
1. Create a new QOS rule for storage in the DC. Specify "1" in the Mbps write field.
2. Attach the rule to a storage domain in the DC via the "storage" main tab in webadmin
3. Create a new VM with a disk attached. Pick the new disk profile.
4. Start the VM
Actual results:
The XML of CreateVM is sent to VDSM with:
2014-09-23 13:57:58,475 INFO
specParams={ioTune={write_bytes_sec=1}}
Expected results:
The units send to VDSM should be the same as specified by the user.
Need also to take under consideration the difference between bits and bytes.
Additional info:
Screenshot and logs from engine and vdsm
ioTune now includes the right size units as requested by user:
For example, I set the new QOS rule with 10MB total and in the request to vdsm, saw:
u'ioTune': {u'total_bytes_sec': 10485760}}
Verified using rhev 3.5 vt13.1
Created attachment 940406 [details] Screenshot and logs from engine and vdsm Description of problem: When creating a new rule of storage blkio QOS, the presented units are in Mbps which are Mega bits per seconds. Examing the XML request passed to VDSM after allocating a disk to the new rule in the log, shows that the the usnits are in bytes per second. Version-Release number of selected component (if applicable): rhev3.5 vt3.1 rhevm-3.5.0-0.12.beta.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Create a new QOS rule for storage in the DC. Specify "1" in the Mbps write field. 2. Attach the rule to a storage domain in the DC via the "storage" main tab in webadmin 3. Create a new VM with a disk attached. Pick the new disk profile. 4. Start the VM Actual results: The XML of CreateVM is sent to VDSM with: 2014-09-23 13:57:58,475 INFO specParams={ioTune={write_bytes_sec=1}} Expected results: The units send to VDSM should be the same as specified by the user. Need also to take under consideration the difference between bits and bytes. Additional info: Screenshot and logs from engine and vdsm