cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2536) parameters (cpu/memory)overcommit ratio and (cpu/memory).overprosioning.factor are redundant(cluster level)
Date Tue, 23 Jul 2013 10:50:48 GMT

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

prashant kumar mishra commented on CLOUDSTACK-2536:
---------------------------------------------------

this fix require  in order to complete my second cycle testing ,changing priority to critical.
                
> 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: Harikrishna Patnala
>             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

Mime
View raw message