Mike, The features are totally different. For the VM Disk I/O Throttling, I want to limit the vm disk I/O in the hypervisors (support KVM only now). However, you do it in the storage device (such as SAN).
I added two fields: bps and iops (maximum, not average/minimum/burst) in disk_offering and service_offering. I also changed cloudstack UI (configuration.js) to add/list the fields. The source codes was put on https://github.com/ustcweizhou/VMDiskIOThrottling/commit/ae9e1fe3ff1f82aa9dedc5e50536b4e959a81fe7 Wei 2013/5/17 Mike Tutkowski <mike.tutkow...@solidfire.com> > It looks like your feature revolves around rate limiting, if I understand > correctly. > > It seems like I could leverage a bit of what you're doing here, but I'd > need additional fields in the Add Disk Offering dialog (and DB) since we > support min, max, and burst values for IOPS (as opposed to just a max). > > What do you think? > > > On Thu, May 16, 2013 at 4:18 PM, Mike Tutkowski < > mike.tutkow...@solidfire.com> wrote: > > > Thanks for the info, Wei. > > > > I am in the process of writing a storage plug-in for Edison's new storage > > framework. The idea is to be able to have a single SAN volume associated > > with a single data disk. In our SAN, you can set Min, Max, and Burst IOPS > > values on a volume-by-volume basis and I'd like to see CloudStack support > > this. > > > > Can you tell me a bit about how you see our features overlapping? Perhaps > > I will not need to update the GUI at all because you might already be > > putting in place such new fields? > > > > Thanks! > > > > > > On Thu, May 16, 2013 at 4:13 PM, Wei ZHOU <ustcweiz...@gmail.com> wrote: > > > >> Mike, > >> > >> I am working on Disk I/O Throttling now. The source code has been > verified > >> on 4.0.2. It need more test on master branch. > >> I hope to finish it before the deadline of 4.2 feature freeze > (31-5-2013). > >> > >> For more information: > >> https://issues.apache.org/jira/browse/CLOUDSTACK-1301 > >> > >> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Disk+IO+Throttling > >> > >> Wei > >> > >> > >> 2013/5/16 Mike Tutkowski <mike.tutkow...@solidfire.com> > >> > >> > Hi everyone, > >> > > >> > I'm trying to add a few fields to the GUI's Add Disk Offering dialog > >> (min, > >> > max, and burst IOPS). > >> > > >> > Once I have these fields in place, they will of course need to pass > this > >> > information to the backend and the data will need to end up in new > >> fields > >> > in the DB. > >> > > >> > I was wondering if anyone knew of example code I might be able to > >> pattern > >> > my changes off of. The one that comes to mind is CPU and RAM > overcommit > >> > changes to the Add Cluster dialog (but I'm having a hard time tracking > >> > these down in Git). > >> > > >> > Thanks! > >> > > >> > -- > >> > *Mike Tutkowski* > >> > *Senior CloudStack Developer, SolidFire Inc.* > >> > e: mike.tutkow...@solidfire.com > >> > o: 303.746.7302 > >> > Advancing the way the world uses the > >> > cloud<http://solidfire.com/solution/overview/?video=play> > >> > *™* > >> > > >> > > > > > > > > -- > > *Mike Tutkowski* > > *Senior CloudStack Developer, SolidFire Inc.* > > e: mike.tutkow...@solidfire.com > > o: 303.746.7302 > > Advancing the way the world uses the cloud< > http://solidfire.com/solution/overview/?video=play> > > *™* > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *™* >
