[jira] [Comment Edited] (CLOUDSTACK-2536) parameters (cpu/memory)overcommit ratio and (cpu/memory).overprosioning.factor are redundant(cluster level)

["Alena Prokharchyk (JIRA)" <ji...@apache.org>]

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

Alena Prokharchyk edited comment on CLOUDSTACK-2536 at 7/22/13 6:12 PM:
------------------------------------------------------------------------

We can't just remove the parameter if it used to be present in the older release. As it might be used by existing customers already, and removing it will break their setups. We should leave both APIs, just mark the older one as deprecated so no new customers use it anymore.
The customers that use it, should have a chance to change their systems in 4.2 to use the new way of setting up the param. We can remove it in 4.3 release.

                
      was (Author: alena1108):
    We can't just remove the parameter if it used to be present in the older release. As it might be used by existing customers already, and removing it will break the setups. Resolving as Won't fix.
                  
> parameters  (cpu/memory)overcommit ratio and (cpu/memory).overprosioning.factor are redundant(cluster level)
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2536
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2536
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, UI
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: Alena Prokharchyk
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> Parameters
> ------------------
> -------------------
> 1-(cpu overcommit ratio ;memory overcommit ratio)
> ----------------------------------------------------------------------------
> APIcalled : 
> http://10.147.*.*:8080/client/api?command=updateCluster&id=a407e95d-0081-44db-9ef0-812d23d6995c&cpuovercommitratio=1&memoryovercommitratio=3
> Result:
> cluster_details table got updated with new overcommit ratio
> 2-cpu.overprovisioning.factor;mem.overprovisioning.factor
> ----------------------------------------------------------------------------------
> APIcalled:
> http://10.147.*.*:8080/client/api?command=updateConfiguration&clusterid=a407e95d-0081-44db-9ef0-812d23d6995c&response=json&sessionkey=rARvjYlVHxDhU6sDx4Jmel%2F%2FFyY%3D&name=cpu.overprovisioning.factor&value=2
> Result:
> Cluster_details table got updated with new overcommit value
> Expected
> -----------------
> -----------------
> Since both parameters are performing same job one of the parameter should be removed 

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