cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4331) Cannot update capacity_bytes or capacity_iops in storage_pool_details via API
Date Wed, 14 Aug 2013 21:03:48 GMT


ASF subversion and git services commented on CLOUDSTACK-4331:

Commit 0f60b5d41cc1db8d29ff72de1a8c38f96a44915e in branch refs/heads/master from [~mike-tutkowski]
[;h=0f60b5d ]

CLOUDSTACK-4331 - Enable more capacity from a managed storage device to be given to CloudStack
> Cannot update capacity_bytes or capacity_iops in storage_pool_details via API
> -----------------------------------------------------------------------------
>                 Key: CLOUDSTACK-4331
>                 URL:
>             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:

View raw message