IOPS throttling is not applied to CDROM
|Affected Versions:||OpenNebula 4.10|
We get IO issues and I add
TOTAL_IOPS_SEC = "80" to
During VMs installations from ISOs, I saw a pick of IO/s (6k).
I made a little script to check VM block device configuration and the output is the following:
INFO: Show total IOPS on one-11857/vda total_bytes_sec: 0 read_bytes_sec : 0 write_bytes_sec: 0 total_iops_sec : 80 read_iops_sec : 0 write_iops_sec : 0 INFO: Show total IOPS on one-11857/hda total_bytes_sec: 0 read_bytes_sec : 0 write_bytes_sec: 0 total_iops_sec : 0 read_iops_sec : 0 write_iops_sec : 0
So, during installation, I have read IO pick on ISO images, which saturate our SAN.
I think the
*IOPS* should be applied to CDROM too.
#2 Updated by EOLE Team almost 6 years ago
Ruben S. Montero wrote:
They should be applied, please check virsh dumpxml. Note that IOPS* are not applied to the CONTEXT CDROM disk. We'll reopen this if needed
hda was the CONTEXT CDROM.
I started a new VM with a proper iso image and the IOPS is applied.
Sorry for the noise.