Hi All, We started using I/O Throttling a few days ago on our platform to fairly share the available disk writes between our customers and create a more reliable disk performance.
It seems to work fine, expect i noticed that when you create a VM from ISO the I/O limit is not applied. We define the I/O write limit in the (VM)service offering, not the disk offering. It seems to work fine for templates, but for ISO installs it seems necessary to also define a limit in the disk offering. I would expect that when you define a limit in the (VM) service offering it's applied to all underlaying disks. And because templates officially don't have a disk offering, it's needed to apply in the service offering. We are now defining it twice, but it's not ideal. Is this normal behavior or a bug? Thanks! Met vriendelijke groet / Kind regards, Lennert den Teuling Tel direct: +31 (0)118 700 210
