[jira] [Commented] (CLOUDSTACK-1301) VM Disk I/O Throttling

["Wei Zhou (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641688#comment-13641688 ] 

Wei Zhou commented on CLOUDSTACK-1301:
--------------------------------------

I have finished the development and testing on cloudstack 4.0.2, and support KVM agent now.
see https://github.com/ustcweizhou/VMDiskIOThrottling
for file and block, it works well.
for network devices such as Ceph, I have no idea.
It should work because the disk I/O limitation is implemented in qemu.

Three ways to limit the disk I/O:
(1) service_offering
(2) disk_offering
(3) bytes_rate/io_rate in global configuration.

I need more discussions about
(1) name of class, columns in db, names in global configuration.
(2) Is it neccesary to limit systemvm ( I think no)?
(3) For attached additional disk, is it limited by service_offering or disk_offering?

                
> VM Disk I/O Throttling
> ----------------------
>
>                 Key: CLOUDSTACK-1301
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1301
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.0.0, 4.1.0
>            Reporter: Wei Zhou
>            Assignee: Wei Zhou
>             Fix For: 4.2.0
>
>
> VM Disk I/O Throttling, to set the maximum disk I/O rate of VMs.
> Virtual machines are running on the same storage device (local storage or share strage). Because of the rate limitation of device (such as iops), if one VM has large disk operation, it may affect the disk performance of other VMs running on the same storage device.
>  It is neccesary to set the maximum rate and limit the disk I/O of VMs.
> More details:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+IO+Throttling

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira