cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-1534) Disable/Enable-unmanage/manage cluster is setting CPU overcommit and Memory overcommit ratio to 1(default value)
Date Fri, 10 May 2013 10:05:15 GMT

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

Bharat Kumar resolved CLOUDSTACK-1534.
--------------------------------------

    Resolution: Fixed
    
> Disable/Enable-unmanage/manage cluster is setting CPU overcommit  and Memory overcommit
ratio to 1(default value)
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1534
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1534
>             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: prashant kumar mishra
>            Assignee: Bharat Kumar
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Disabling and unmanaging cluster is calling  API updateCluster with (CPU/Memory)overcommit
 ratio=1.0 resulting overcommit ratio set to 1;
> Steps
> -------
> 1-Create a cluster set overcommit ratio to some value say 2 and 3
> 2-Disable or unmanage cluster
> Expected
> ------------
> 1-cluster overcommit ratio should not change
> Actual
> ---------
> Overcommit ratio is getting changed to 1
> snippet of Log:
> ---------------------
> 2013-03-06 04:13:00,547 DEBUG [agent.transport.Request] (DirectAgent-124:null) Seq 1-518324229:
Processing:  { Ans: , MgmtId: 7382478356578, via: 1, Ver: v1, Flags: 10, [{"ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
}
> 2013-03-06 04:13:03,218 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null) ===START===
 10.146.0.133 -- GET  command=updateCluster&id=a236196c-26d7-4080-922e-190ea6df93ed&allocationstate=Enabled&response=json&sessionkey=Pk%2BX82p5dw5ddc6kDNV%2B1edTyD8%3D&_=1362561179729
> 2013-03-06 04:13:03,278 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null) ===END===
 10.146.0.133 -- GET  command=updateCluster&id=a236196c-26d7-4080-922e-190ea6df93ed&allocationstate=Enabled&response=json&sessionkey=Pk%2BX82p5dw5ddc6kDNV%2B1edTyD8%3D&_=1362561179729
> 2013-03-06 04:13:06,349 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) ===START===
 10.146.0.133 -- GET  command=listZones&response=json&sessionkey=Pk%2BX82p5dw5ddc6kDNV%2B1edTyD8%3D&id=7f23c968-c273-4b9a-a203-2d1166f0c67a&_=1362561182914
> 2013-03-06 04:13:06,388 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) ===END===
 10.146.0.133 -- GET  command=listZones&response=json&sessionkey=Pk%2BX82p5dw5ddc6kDNV%2B1edTyD8%3D&id=7f23c968-c273-4b9a-a203-2d1166f0c67a&_=1362561182914
> 2013-03-06 04:13:06,455 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===START===
 10.146.0.133 -- GET  command=listConfigurations&response=json&sessionkey=Pk%2BX82p5dw5ddc6kDNV%2B1edTyD8%3D&name=vmware.use.nexus.vswitch&_=1362561182981
> 2013-03-06 04:13:06,493 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===END===
 10.146.0.133 -- GET  command=listConfigurations&response=json&sessionkey=Pk%2BX82p5dw5ddc6kDNV%2B1edTyD8%3D&name=vmware.use.nexus.vswitch&_=1362561182981
> 2013-03-06 04:13:06,606 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null) ===START===
 10.146.0.133 -- GET  command=listClusters&id=a236196c-26d7-4080-922e-190ea6df93ed&response=json&sessionkey=Pk%2BX82p5dw5ddc6kDNV%2B1edTyD8%3D&_=1362561183133
> 2013-03-06 04:13:06,640 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null) ===END===
 10.146.0.133 -- GET  command=listClusters&id=a236196c-26d7-4080-922e-190ea6df93ed&response=json&sessionkey=Pk%2BX82p5dw5ddc6kDNV%2B1edTyD8%3D&_=1362561183133

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