cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-2957) deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume
Date Wed, 12 Jun 2013 11:26:20 GMT

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

Nitin Mehta updated CLOUDSTACK-2957:
------------------------------------

    Description: 
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.

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

Mime
View raw message