[
https://issues.apache.org/jira/browse/CLOUDSTACK-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Tutkowski resolved CLOUDSTACK-4331.
----------------------------------------
Resolution: Fixed
Modified logic to allow CloudStack to increase the capacity_bytes and/or
capacity_iops fields (an exception is throw if one tries to reduce either of
them).
> Cannot update capacity_bytes or capacity_iops in storage_pool_details via API
> -----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4331
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4331
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.2.0
> Environment: Mac OS X
> Reporter: Mike Tutkowski
> Assignee: Mike Tutkowski
> Priority: Critical
> Fix For: 4.2.0
>
>
> When creating managed primary storage, you need to specify the maximum bytes
> and maximum IOPS that CloudStack can leverage from the device being managed.
> For example, you can add a primary storage to CloudStack that's based on the
> SolidFire plug-in. In the process, you specify how many bytes and IOPS can be
> used from the SAN.
> The problem here is that there is no way to bump these numbers up if you'd
> like to provide more bytes and/or IOPS to CloudStack from the storage system
> (ex. say the storage system's capacity increases and you'd like to give more
> of this capacity to CloudStack).
--
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
