[ https://issues.apache.org/jira/browse/CLOUDSTACK-10039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216101#comment-16216101 ]
ASF GitHub Bot commented on CLOUDSTACK-10039: --------------------------------------------- mike-tutkowski commented on issue #2294: [CLOUDSTACK-10039] Adding allocated IOPS to storage pool response URL: https://github.com/apache/cloudstack/pull/2294#issuecomment-338831054 @borisroman Are we good to go with this PR? Should I merge it? Thanks! ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Adding IOPS/GB offering > ----------------------- > > Key: CLOUDSTACK-10039 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10039 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller > Reporter: Syed Ahmed > Fix For: Future > > > We want to add a disk offering where we can specify the Min/Max IOPS as a > function of size. The idea is the larger volume you create, the greater your > IOPS will be (this is similar to the way GCE handles IOPS). We also have > added limits to the IOPS (min and max) so that once the volume goes beyond a > certain size, the IOPS won't change and are capped to the given values. > The following parameters are added to the `createDiskOffering` API: > 1. `miniopspergb' : Minimum IOPS/GB for the offering > 2. `maxiopspergb`: Maximum IOPS/GB for the offering > 3. `highestminiops`: The highest `miniops` value that is allowed for this > offering > 3. `highestmaxiops`: The highest `maxiops` value that is allowed for this > offering -- This message was sent by Atlassian JIRA (v6.4.14#64029)