[
https://issues.apache.org/jira/browse/CLOUDSTACK-10039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292446#comment-16292446
]
ASF subversion and git services commented on CLOUDSTACK-10039:
--------------------------------------------------------------
Commit 47419df368336b089814d66f4a70afeae9e1ba47 in cloudstack's branch
refs/heads/master from [~syed1]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=47419df ]
CLOUDSTACK-10039: Adding used IOPS to storage pool response (#2294)
This change adds allocatediops to the ListStoragePool API. This applies to
managed storage where we have a guaranteed minimum IOPS set. This is useful for
monitoring if we have reached the IOPS limit on a storage cluster.
> 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)
