You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Vladimir Melnik (JIRA)" <ji...@apache.org> on 2014/03/22 19:59:42 UTC

[jira] [Commented] (CLOUDSTACK-6275) cpu.overprovisioning.factor doesn't work

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

Vladimir Melnik commented on CLOUDSTACK-6275:
---------------------------------------------

https://issues.apache.org/jira/browse/CLOUDSTACK-3187 looks similar, but it seems that the bug haven't been fixed yet.

> cpu.overprovisioning.factor doesn't work
> ----------------------------------------
>
>                 Key: CLOUDSTACK-6275
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6275
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.1
>         Environment: CentOS-6.5 on the management server and all hypevisors
>            Reporter: Vladimir Melnik
>
> Overprovisioning doesn't work. You couldn't set cpu.overprovisioning.factor = 4, restart the management server, but couldn't deploy new VMs:
> 2014-03-22 19:52:43,174 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-25:job-532 = [ 4ff67030-1608-4fd1-9149-593d28f875a6 ]) Searching all possible resources under this Zone: 1
> 2014-03-22 19:52:43,175 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-25:job-532 = [ 4ff67030-1608-4fd1-9149-593d28f875a6 ]) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-22 19:52:43,181 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-25:job-532 = [ 4ff67030-1608-4fd1-9149-593d28f875a6 ]) Cannot allocate cluster list [1] for vm creation since theirallocated percentage crosses the disable capacity threshold defined at each cluster/ at global value for capacity Type : 1, skipping these clusters
> 2014-03-22 19:52:43,181 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-25:job-532 = [ 4ff67030-1608-4fd1-9149-593d28f875a6 ]) No clusters found after removing disabled clusters and clusters in avoid list, returning.



--
This message was sent by Atlassian JIRA
(v6.2#6252)