Re: 回复： 问题 InsufficientServerCapacityException: Unable to create a deployment for VM[User|vm1]

2014-06-23 文章 Yujiang Pang 
我通过给第二个xen cluster新添加一个主存储解决了这个问题。VM被创建起来了。


On 20 June 2014 17:25, Yujiang Pang  wrote:

> 成功了的。初步判断是 “No storage pools available for shared volume allocation,
> returning” 日志里面的这个问题。
>
> 现在Google了下，有个帖子
> http://comments.gmane.org/gmane.comp.apache.cloudstack.user/7871
>  说要给我的第二个xen cluster的host加一个primary，刚试了下， 没有InsuffientServerCapacity了，
> VM还在创建中。
>
>
> On 20 June 2014 16:45, Adagio <68630...@qq.com> wrote:
>
>> 好像host没有被正确识别，你确定添加host成功了吗？
>>
>>
>>
>>
>>
>>
>> -- 原始邮件 --
>> 发件人: "Yujiang Pang";;
>> 发送时间: 2014年6月20日(星期五) 下午4:33
>> 收件人: "users-cn";
>>
>> 主题: Re: 问题 InsufficientServerCapacityException: Unable to create a
>> deployment for VM[User|vm1]
>>
>>
>>
>> hi 大家好，
>>
>> 我按照第一个方法 改好日志输出级别后 发现日志如下， 麻烦大家帮忙看下呢：
>> {{
>> DEBUG [c.c.a.ApiServlet] (catalina-exec-23:ctx-4284f15a ctx-a17c36f3)
>> ===END===  10.121.123.166 -- GET
>>
>>  
>> command=deployVirtualMachine&response=json&sessionkey=S%2FzlgI8p4FapWwN%2BW39POd5RkBs%3D&zoneid=d718cbb3-2a42-47b1-b428-9fe80e6abfef&templateid=ef7f2226-f775-11e3-b668-14feb5e24708&hypervisor=XenServer&serviceofferingid=3ead12b2-77af-4ef5-9fbf-b6b4b313f398&diskofferingid=8257cf83-9328-4ad2-aad2-775de2a17a8f&networkids=90bccdc2-4580-46d4-8e2f-a8f7bed9c6cc&displayname=vm1&name=vm1&_=1403251372470
>> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> InfrastructureEntity name is:com.cloud.offering.ServiceOffering
>> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> ControlledEntity name is:com.cloud.template.VirtualMachineTemplate
>> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> ControlledEntity name is:com.cloud.network.Network
>> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> InfrastructureEntity name is:com.cloud.offering.DiskOffering
>> DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Service SecurityGroup is not supported in the network id=204
>> DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Service SecurityGroup is not supported in the network id=204
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Deploy avoids pods: [], clusters: [], hosts: []
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) DeploymentPlanner allocation algorithm:
>> com.cloud.deploy.FirstFitPlanner@67619b83
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Trying to allocate a host and storage pools from dc:1,
>> pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Is ROOT volume READY (pool already allocated)?: No
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Searching all possible resources under this Zone: 1
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Listing clusters in order of aggregate capacity, that have (atleast one
>> host with) enough CPU and RAM capacity under this Zone: 1
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Removing from the clusterId list these clusters from avoid set: []
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Cannot allocate cluster list [1] for vm creation since their allocated
>> percentage crosses the disable capacity threshold defined at each cluster/
>> at global value for capacity Type : 0, skipping these clusters
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Checking resources in Cluster: 2 under Pod: 1
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) Looking for hosts in dc: 1  pod:1
>>  cluster:2
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to
>> check for allocation: [Host[-4-Routing]]
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) Found 1 hosts for allocation after
>> prioritization: [Host[-4-Routing]]
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=512
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Host: 4 has cpu capability (cpu:2, speed:2926)
>> to
>> support requested CPU: 1 and requested speed: 500
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Checking if host: 4 has enough capacity for
>> requested CPU: 500 and requested RAM: 536870912 ,
>> cpuOverprovisioningFactor: 1.0
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Hosts's actual total CPU: 5

Re: 回复： 问题 InsufficientServerCapacityException: Unable to create a deployment for VM[User|vm1]

2014-06-20 文章 Yujiang Pang 
成功了的。初步判断是 “No storage pools available for shared volume allocation,
returning” 日志里面的这个问题。

现在Google了下，有个帖子
http://comments.gmane.org/gmane.comp.apache.cloudstack.user/7871
 说要给我的第二个xen cluster的host加一个primary，刚试了下， 没有InsuffientServerCapacity了，
VM还在创建中。


On 20 June 2014 16:45, Adagio <68630...@qq.com> wrote:

> 好像host没有被正确识别，你确定添加host成功了吗？
>
>
>
>
>
>
> -- 原始邮件 --
> 发件人: "Yujiang Pang";;
> 发送时间: 2014年6月20日(星期五) 下午4:33
> 收件人: "users-cn";
>
> 主题: Re: 问题 InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|vm1]
>
>
>
> hi 大家好，
>
> 我按照第一个方法 改好日志输出级别后 发现日志如下， 麻烦大家帮忙看下呢：
> {{
> DEBUG [c.c.a.ApiServlet] (catalina-exec-23:ctx-4284f15a ctx-a17c36f3)
> ===END===  10.121.123.166 -- GET
>
>  
> command=deployVirtualMachine&response=json&sessionkey=S%2FzlgI8p4FapWwN%2BW39POd5RkBs%3D&zoneid=d718cbb3-2a42-47b1-b428-9fe80e6abfef&templateid=ef7f2226-f775-11e3-b668-14feb5e24708&hypervisor=XenServer&serviceofferingid=3ead12b2-77af-4ef5-9fbf-b6b4b313f398&diskofferingid=8257cf83-9328-4ad2-aad2-775de2a17a8f&networkids=90bccdc2-4580-46d4-8e2f-a8f7bed9c6cc&displayname=vm1&name=vm1&_=1403251372470
> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> InfrastructureEntity name is:com.cloud.offering.ServiceOffering
> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> ControlledEntity name is:com.cloud.template.VirtualMachineTemplate
> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> ControlledEntity name is:com.cloud.network.Network
> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> InfrastructureEntity name is:com.cloud.offering.DiskOffering
> DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> Service SecurityGroup is not supported in the network id=204
> DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> Service SecurityGroup is not supported in the network id=204
> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3) Deploy avoids pods: [], clusters: [], hosts: []
> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3) DeploymentPlanner allocation algorithm:
> com.cloud.deploy.FirstFitPlanner@67619b83
> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3) Trying to allocate a host and storage pools from dc:1,
> pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3) Is ROOT volume READY (pool already allocated)?: No
> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> Searching all possible resources under this Zone: 1
> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> Listing clusters in order of aggregate capacity, that have (atleast one
> host with) enough CPU and RAM capacity under this Zone: 1
> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> Removing from the clusterId list these clusters from avoid set: []
> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
> Cannot allocate cluster list [1] for vm creation since their allocated
> percentage crosses the disable capacity threshold defined at each cluster/
> at global value for capacity Type : 0, skipping these clusters
> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3) Checking resources in Cluster: 2 under Pod: 1
> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3 FirstFitRoutingAllocator) Looking for hosts in dc: 1  pod:1
>  cluster:2
> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to
> check for allocation: [Host[-4-Routing]]
> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3 FirstFitRoutingAllocator) Found 1 hosts for allocation after
> prioritization: [Host[-4-Routing]]
> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
> ctx-a17c36f3 FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=512
> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3
> FirstFitRoutingAllocator) Host: 4 has cpu capability (cpu:2, speed:2926) to
> support requested CPU: 1 and requested speed: 500
> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3
> FirstFitRoutingAllocator) Checking if host: 4 has enough capacity for
> requested CPU: 500 and requested RAM: 536870912 ,
> cpuOverprovisioningFactor: 1.0
> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3
> FirstFitRoutingAllocator) Hosts's actual total CPU: 5852 and CPU after
> applying overprovisioning: 5852
> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3
> FirstFitRoutingAllocator) Free CPU: 5852 , Requested CPU: 500
> DEBUG