You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Nitin Mehta (JIRA)" <ji...@apache.org> on 2013/06/18 08:15:21 UTC

[jira] [Resolved] (CLOUDSTACK-2957) deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nitin Mehta resolved CLOUDSTACK-2957.
-------------------------------------

    Resolution: Fixed
    
> deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2957
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2957
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>             Fix For: 4.2.0
>
>
> size atribute when used with custom disk offering should be limited by storage.max.volume.size global config (default 2000 gb) as it is in createVolume but from the code seems like its not. The number is used to avoid abuse by the end user.

--
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