[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742422#comment-13742422
 ] 

Sudha Ponnaganti commented on CLOUDSTACK-3721:
----------------------------------------------

we have introduced these parameters as part of feature in 4.2 itself but later 
we removed these parameters in 4.2.
Prior to 4.2 these parameters are not there, so I think no need to mark them as 
deprecated. 

                
> updateCluster API: mark cpuovercommitratio and memoryovercommitratio as 
> deprecated
> ----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3721
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3721
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: API
>    Affects Versions: 4.2.0
>            Reporter: Alena Prokharchyk
>            Assignee: Harikrishna Patnala
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> As memoryovercommitratio and cpuovercommitratio are being set using 
> updateConfiguration generic API starting from 4.2 release, they should be 
> marked as deprecated in updateCluster command so the customers won't use it 
> any more.

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

Reply via email to