AW: KVM CPU Overprovisioning issues.
If you change the value of the setting you need to reboot all instances which
were running before the change. If you do not do this the calculation in CS is
wrong.
Reason for that is that CS is attaching the value to the instance.
Here is an example:
cpu.overprovisioning.factor = 1
create instance with 1x 1000Ghz (this will use 1000Ghz of your CPU capacity)
changing cpu.overprovisioning.factor to 2 and the same instance will use
2000Ghz of your CPU capacity)
after rebooting this instance it will use 500Ghz of your CPU capacity as
expected.
It is a little bit confusion.
Mit freundlichen Grüßen / With kind regards,
Swen Brüseke
-Ursprüngliche Nachricht-
Von: ilya [mailto:ilya.mailing.li...@gmail.com]
Gesendet: Samstag, 18. April 2015 02:27
An: users@cloudstack.apache.org
Betreff: Re: KVM CPU Overprovisioning issues.
When the deployment goes through, the allocation placement algorithm will tell
you if cpu over provisioning worked. You can see it in management-server.log
file..
Here is an easy way to extract useful info for failed vm deployment.
After deployment failed, grep for cloudstack internal name of the VM and note
the job id (i see in your log it was job-7312) in management-server.log . Once
you have the job id, grep 'job-'
management-server.log. Post the content here... I do see you post it the log
below, it appears we are missing some info.
You can override CPU overprovisioning values in global settings as well as
cluster settings.
If you are enable CPU reservations, than it probably wont work, because you
trying to reserve more than whats available.
What version of ACS you have and what hypervisor?
On 4/17/15 2:01 PM, Grayson Head wrote:
> I'm trying to figure out how CPU over-provisioning works in
> cloudstack. It seems that no matter how much I change the
> over-provisioning factor value in global settings, I cannot
> over-provision CPU allocation on the hosts. I suspect that I'm just
> having a lack of understanding on my part, but it seems like I should
> be able to increase the number of VMs I can deploy by increasing the
> CPU over-provisioning value (given that I'm not close to any other
> resource limits). But this doesn't seem to be the case in practice.
>
> https://screencloud.net/v/l1X7
>
> https://screencloud.net/v/9ifx
>
> Error message when trying to create additional machine via API.
>
> grayson@gworkstation:~$ cloudmonkey deploy virtualmachine
> zoneid=a4c20770-f17e-425e-bb21-413dd610b975
> serviceofferingid=4b391121-49c7-4434-883d-ffe569f63a3b
> templateid=e5701f73-b0c3-4dd7-8b2d-b8bf78875a85 keypair=key1
> networkids=86e6ded0-6155-449b-a4bd-03411bf0a9cd name=tvmsman1
> displayname & [1] 3907 Async job 09148c21-3c42-4334-93b2-428b48fb1fa2
> failed Error 533, Unable to create a deployment for
> VM[User|i-15-1151-VM]
> accountid = a4e6eaed-9b06-4806-98f9-4fcc781b773f
> cmd = org.apache.cloudstack.api.command.user.vm.DeployVMCmd
> created = 2015-04-17T13:46:22-0700
> jobid = 09148c21-3c42-4334-93b2-428b48fb1fa2
> jobprocstatus = 0
> jobresult:
> errorcode = 533
> errortext = Unable to create a deployment for VM[User|i-15-1151-VM]
> jobresultcode = 530 jobresulttype = object jobstatus = 2 userid =
> c7a0889e-fcec-4095-9d07-d29ea3c1e5d9
>
>
> (local) mycloudmonkey> list hosts
> filter=name,clustername,cpuallocated,cpunumber,cpusockets,cpuspeed,cpu
> used,cpuwithoverprovisioning,
> name = v-78-VM
> ==
> ==
> name = s-871-VM
> ==
> ==
> name = cl2hyper2
> clustername = CL2
> cpuallocated = 100.3%
> cpunumber = 8
> cpusockets = 2
> cpuspeed = 1994
> cpuused = 1.2%
> cpuwithoverprovisioning = 63808.0
> ==
> ==
> name = v-1-VM
> ==
> ==
> name = cl2hyper1
> clustername = CL2
> cpuallocated = 81.45%
> cpunumber = 8
> cpusockets = 2
> cpuspeed = 1995
> cpuused = 0.6%
> cpuwithoverprovisioning = 63840.0
> ==
> ==
>
>
>
> 2015-04-17 13:46:22,517 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-25:ctx-7b0eb43a ctx-751b2eca ctx-5c8a75fc) submit async
> job-7312, details: AsyncJobVO {id:7312, userId: 15, accountId: 15,
> instanceType: VirtualMachine, instanceId: 1151, cmd:
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo:
> {"serviceofferingid":"4b391121-49c7-4434-883d-ffe569f63a3b","cmdEventT
> ype":"VM.CREATE","ctxUserId":&
Re: KVM CPU Overprovisioning issues.
When the deployment goes through, the allocation placement algorithm
will tell you if cpu over provisioning worked. You can see it in
management-server.log file..
Here is an easy way to extract useful info for failed vm deployment.
After deployment failed, grep for cloudstack internal name of the VM and
note the job id (i see in your log it was job-7312) in
management-server.log . Once you have the job id, grep 'job-'
management-server.log. Post the content here... I do see you post it the
log below, it appears we are missing some info.
You can override CPU overprovisioning values in global settings as well
as cluster settings.
If you are enable CPU reservations, than it probably wont work, because
you trying to reserve more than whats available.
What version of ACS you have and what hypervisor?
On 4/17/15 2:01 PM, Grayson Head wrote:
I'm trying to figure out how CPU over-provisioning works in
cloudstack. It seems that no matter how much I change the
over-provisioning factor value in global settings, I cannot
over-provision CPU allocation on the hosts. I suspect that I'm just
having a lack of understanding on my part, but it seems like I should
be able to increase the number of VMs I can deploy by increasing the
CPU over-provisioning value (given that I'm not close to any other
resource limits). But this doesn't seem to be the case in practice.
https://screencloud.net/v/l1X7
https://screencloud.net/v/9ifx
Error message when trying to create additional machine via API.
grayson@gworkstation:~$ cloudmonkey deploy virtualmachine
zoneid=a4c20770-f17e-425e-bb21-413dd610b975
serviceofferingid=4b391121-49c7-4434-883d-ffe569f63a3b
templateid=e5701f73-b0c3-4dd7-8b2d-b8bf78875a85 keypair=key1
networkids=86e6ded0-6155-449b-a4bd-03411bf0a9cd name=tvmsman1
displayname &
[1] 3907
Async job 09148c21-3c42-4334-93b2-428b48fb1fa2 failed
Error 533, Unable to create a deployment for VM[User|i-15-1151-VM]
accountid = a4e6eaed-9b06-4806-98f9-4fcc781b773f
cmd = org.apache.cloudstack.api.command.user.vm.DeployVMCmd
created = 2015-04-17T13:46:22-0700
jobid = 09148c21-3c42-4334-93b2-428b48fb1fa2
jobprocstatus = 0
jobresult:
errorcode = 533
errortext = Unable to create a deployment for VM[User|i-15-1151-VM]
jobresultcode = 530
jobresulttype = object
jobstatus = 2
userid = c7a0889e-fcec-4095-9d07-d29ea3c1e5d9
(local) mycloudmonkey> list hosts
filter=name,clustername,cpuallocated,cpunumber,cpusockets,cpuspeed,cpuused,cpuwithoverprovisioning,
name = v-78-VM
name = s-871-VM
name = cl2hyper2
clustername = CL2
cpuallocated = 100.3%
cpunumber = 8
cpusockets = 2
cpuspeed = 1994
cpuused = 1.2%
cpuwithoverprovisioning = 63808.0
name = v-1-VM
name = cl2hyper1
clustername = CL2
cpuallocated = 81.45%
cpunumber = 8
cpusockets = 2
cpuspeed = 1995
cpuused = 0.6%
cpuwithoverprovisioning = 63840.0
2015-04-17 13:46:22,517 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-25:ctx-7b0eb43a ctx-751b2eca ctx-5c8a75fc) submit async
job-7312, details: AsyncJobVO {id:7312, userId: 15, accountId: 15,
instanceType: VirtualMachine, instanceId: 1151, cmd:
org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo:
{"serviceofferingid":"4b391121-49c7-4434-883d-ffe569f63a3b","cmdEventType":"VM.CREATE","ctxUserId":"15","zoneid":"a4c20770-f17e-425e-bb21-413dd610b975","signatureversion":"3","httpmethod":"GET","templateid":"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85","networkids":"86e6ded0-6155-449b-a4bd-03411bf0a9cd","apiKey":"wrxDdS8yi2kJPe8UrNdOdLtp55mCSKskk3MyTJ1ucIApdMoYnOWsd-dmigPywD1KC-6BVfVmKiJVenEM_kovpw","id":"1151","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85\",\"com.cloud.vm.VirtualMachine\":\"6b3ace85-8e4c-4467-afdf-b511136ca6b1\",\"com.cloud.network.Network\":\"86e6ded0-6155-449b-a4bd-03411bf0a9cd\",\"com.cloud.dc.DataCenter\":\"a4c20770-f17e-425e-bb21-413dd610b975\",\"com.cloud.offering.ServiceOffering\":\"4b391121-49c7-4434-883d-ffe569f63a3b\"}","expires":"2015-04-17T20:56:22+","keypair":"key1","name":"tvmsman1","uuid":"6b3ace85-8e4c-4467-afdf-b511136ca6b1","ctxAccountId":"15","ctxStartEventId":"11922","signature":"8Ebg1+qjfnk5nv7xz1GtdSju2ws\u003d"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
result: null, initMsid: 345050015385, completeMsid: null, lastUpdated:
null, lastPolled: null, created: null}
2015-04-17 13:46:22,518 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-16:ctx-e039eccb job-7312) Add job-7312 into job
monitoring
2015-04-17 13:46:22,518 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-16:
Re: KVM CPU Overprovisioning issues.
Sure enough.
Its been a while since I configured a new cluster, I completely forgot
they had their own over-provisioning limits.
Thanks!
On Fri, Apr 17, 2015 at 4:10 PM, Andrija Panic wrote:
> If not mistaken, there is global overprovisioning factor, and there is
> cluster level overprovisioning - the last one takes presedence I think...
>
> On 17 April 2015 at 23:01, Grayson Head wrote:
>
>> I'm trying to figure out how CPU over-provisioning works in
>> cloudstack. It seems that no matter how much I change the
>> over-provisioning factor value in global settings, I cannot
>> over-provision CPU allocation on the hosts. I suspect that I'm just
>> having a lack of understanding on my part, but it seems like I should
>> be able to increase the number of VMs I can deploy by increasing the
>> CPU over-provisioning value (given that I'm not close to any other
>> resource limits). But this doesn't seem to be the case in practice.
>>
>> https://screencloud.net/v/l1X7
>>
>> https://screencloud.net/v/9ifx
>>
>> Error message when trying to create additional machine via API.
>>
>> grayson@gworkstation:~$ cloudmonkey deploy virtualmachine
>> zoneid=a4c20770-f17e-425e-bb21-413dd610b975
>> serviceofferingid=4b391121-49c7-4434-883d-ffe569f63a3b
>> templateid=e5701f73-b0c3-4dd7-8b2d-b8bf78875a85 keypair=key1
>> networkids=86e6ded0-6155-449b-a4bd-03411bf0a9cd name=tvmsman1
>> displayname &
>> [1] 3907
>> Async job 09148c21-3c42-4334-93b2-428b48fb1fa2 failed
>> Error 533, Unable to create a deployment for VM[User|i-15-1151-VM]
>> accountid = a4e6eaed-9b06-4806-98f9-4fcc781b773f
>> cmd = org.apache.cloudstack.api.command.user.vm.DeployVMCmd
>> created = 2015-04-17T13:46:22-0700
>> jobid = 09148c21-3c42-4334-93b2-428b48fb1fa2
>> jobprocstatus = 0
>> jobresult:
>> errorcode = 533
>> errortext = Unable to create a deployment for VM[User|i-15-1151-VM]
>> jobresultcode = 530
>> jobresulttype = object
>> jobstatus = 2
>> userid = c7a0889e-fcec-4095-9d07-d29ea3c1e5d9
>>
>>
>> (local) mycloudmonkey> list hosts
>>
>> filter=name,clustername,cpuallocated,cpunumber,cpusockets,cpuspeed,cpuused,cpuwithoverprovisioning,
>> name = v-78-VM
>>
>>
>> name = s-871-VM
>>
>>
>> name = cl2hyper2
>> clustername = CL2
>> cpuallocated = 100.3%
>> cpunumber = 8
>> cpusockets = 2
>> cpuspeed = 1994
>> cpuused = 1.2%
>> cpuwithoverprovisioning = 63808.0
>>
>>
>> name = v-1-VM
>>
>>
>> name = cl2hyper1
>> clustername = CL2
>> cpuallocated = 81.45%
>> cpunumber = 8
>> cpusockets = 2
>> cpuspeed = 1995
>> cpuused = 0.6%
>> cpuwithoverprovisioning = 63840.0
>>
>>
>>
>>
>>
>> 2015-04-17 13:46:22,517 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>> (catalina-exec-25:ctx-7b0eb43a ctx-751b2eca ctx-5c8a75fc) submit async
>> job-7312, details: AsyncJobVO {id:7312, userId: 15, accountId: 15,
>> instanceType: VirtualMachine, instanceId: 1151, cmd:
>> org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo:
>>
>> {"serviceofferingid":"4b391121-49c7-4434-883d-ffe569f63a3b","cmdEventType":"VM.CREATE","ctxUserId":"15","zoneid":"a4c20770-f17e-425e-bb21-413dd610b975","signatureversion":"3","httpmethod":"GET","templateid":"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85","networkids":"86e6ded0-6155-449b-a4bd-03411bf0a9cd","apiKey":"wrxDdS8yi2kJPe8UrNdOdLtp55mCSKskk3MyTJ1ucIApdMoYnOWsd-dmigPywD1KC-6BVfVmKiJVenEM_kovpw","id":"1151","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85\",\"com.cloud.vm.VirtualMachine\":\"6b3ace85-8e4c-4467-afdf-b511136ca6b1\",\"com.cloud.network.Network\":\"86e6ded0-6155-449b-a4bd-03411bf0a9cd\",\"com.cloud.dc.DataCenter\":\"a4c20770-f17e-425e-bb21-413dd610b975\",\"com.cloud.offering.ServiceOffering\":\"4b391121-49c7-4434-883d-ffe569f63a3b\"}","expires":"2015-04-17T20:56:22+","keypair":"key1","name":"tvmsman1","uuid":"6b3ace85-8e4c-4467-afdf-b511136ca6b1","ctxAccountId":"15","ctxStartEventId":"11922","signature":"8Ebg1+qjfnk5nv7xz1GtdSju2ws\u003d"},
>> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
>> result: null, initMsid: 345050015385, completeMsid: null, lastUpdated:
>> null, lastPolled: null, created: null}
>> 2015-04-17 13:46:22,518 INFO [o.a.c.f.j.i.AsyncJobMonitor]
>> (API-Job-Executor-16:ctx-e039eccb job-7312) Add job-7312 into job
>> monitoring
>> 2015-04-17 13:46:22,518 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>> (API-Job-Executor-16:ctx-e039eccb job-7312) Executing AsyncJobVO
>> {id:7312, userId: 15, accountId: 15, instanceType: VirtualMachine,
>> instanceId: 1151, cmd:
>> org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo:
>>
>> {"ser
Re: KVM CPU Overprovisioning issues.
If not mistaken, there is global overprovisioning factor, and there is
cluster level overprovisioning - the last one takes presedence I think...
On 17 April 2015 at 23:01, Grayson Head wrote:
> I'm trying to figure out how CPU over-provisioning works in
> cloudstack. It seems that no matter how much I change the
> over-provisioning factor value in global settings, I cannot
> over-provision CPU allocation on the hosts. I suspect that I'm just
> having a lack of understanding on my part, but it seems like I should
> be able to increase the number of VMs I can deploy by increasing the
> CPU over-provisioning value (given that I'm not close to any other
> resource limits). But this doesn't seem to be the case in practice.
>
> https://screencloud.net/v/l1X7
>
> https://screencloud.net/v/9ifx
>
> Error message when trying to create additional machine via API.
>
> grayson@gworkstation:~$ cloudmonkey deploy virtualmachine
> zoneid=a4c20770-f17e-425e-bb21-413dd610b975
> serviceofferingid=4b391121-49c7-4434-883d-ffe569f63a3b
> templateid=e5701f73-b0c3-4dd7-8b2d-b8bf78875a85 keypair=key1
> networkids=86e6ded0-6155-449b-a4bd-03411bf0a9cd name=tvmsman1
> displayname &
> [1] 3907
> Async job 09148c21-3c42-4334-93b2-428b48fb1fa2 failed
> Error 533, Unable to create a deployment for VM[User|i-15-1151-VM]
> accountid = a4e6eaed-9b06-4806-98f9-4fcc781b773f
> cmd = org.apache.cloudstack.api.command.user.vm.DeployVMCmd
> created = 2015-04-17T13:46:22-0700
> jobid = 09148c21-3c42-4334-93b2-428b48fb1fa2
> jobprocstatus = 0
> jobresult:
> errorcode = 533
> errortext = Unable to create a deployment for VM[User|i-15-1151-VM]
> jobresultcode = 530
> jobresulttype = object
> jobstatus = 2
> userid = c7a0889e-fcec-4095-9d07-d29ea3c1e5d9
>
>
> (local) mycloudmonkey> list hosts
>
> filter=name,clustername,cpuallocated,cpunumber,cpusockets,cpuspeed,cpuused,cpuwithoverprovisioning,
> name = v-78-VM
>
>
> name = s-871-VM
>
>
> name = cl2hyper2
> clustername = CL2
> cpuallocated = 100.3%
> cpunumber = 8
> cpusockets = 2
> cpuspeed = 1994
> cpuused = 1.2%
> cpuwithoverprovisioning = 63808.0
>
>
> name = v-1-VM
>
>
> name = cl2hyper1
> clustername = CL2
> cpuallocated = 81.45%
> cpunumber = 8
> cpusockets = 2
> cpuspeed = 1995
> cpuused = 0.6%
> cpuwithoverprovisioning = 63840.0
>
>
>
>
>
> 2015-04-17 13:46:22,517 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-25:ctx-7b0eb43a ctx-751b2eca ctx-5c8a75fc) submit async
> job-7312, details: AsyncJobVO {id:7312, userId: 15, accountId: 15,
> instanceType: VirtualMachine, instanceId: 1151, cmd:
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo:
>
> {"serviceofferingid":"4b391121-49c7-4434-883d-ffe569f63a3b","cmdEventType":"VM.CREATE","ctxUserId":"15","zoneid":"a4c20770-f17e-425e-bb21-413dd610b975","signatureversion":"3","httpmethod":"GET","templateid":"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85","networkids":"86e6ded0-6155-449b-a4bd-03411bf0a9cd","apiKey":"wrxDdS8yi2kJPe8UrNdOdLtp55mCSKskk3MyTJ1ucIApdMoYnOWsd-dmigPywD1KC-6BVfVmKiJVenEM_kovpw","id":"1151","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85\",\"com.cloud.vm.VirtualMachine\":\"6b3ace85-8e4c-4467-afdf-b511136ca6b1\",\"com.cloud.network.Network\":\"86e6ded0-6155-449b-a4bd-03411bf0a9cd\",\"com.cloud.dc.DataCenter\":\"a4c20770-f17e-425e-bb21-413dd610b975\",\"com.cloud.offering.ServiceOffering\":\"4b391121-49c7-4434-883d-ffe569f63a3b\"}","expires":"2015-04-17T20:56:22+","keypair":"key1","name":"tvmsman1","uuid":"6b3ace85-8e4c-4467-afdf-b511136ca6b1","ctxAccountId":"15","ctxStartEventId":"11922","signature":"8Ebg1+qjfnk5nv7xz1GtdSju2ws\u003d"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 345050015385, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: null}
> 2015-04-17 13:46:22,518 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-16:ctx-e039eccb job-7312) Add job-7312 into job
> monitoring
> 2015-04-17 13:46:22,518 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-16:ctx-e039eccb job-7312) Executing AsyncJobVO
> {id:7312, userId: 15, accountId: 15, instanceType: VirtualMachine,
> instanceId: 1151, cmd:
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo:
>
> {"serviceofferingid":"4b391121-49c7-4434-883d-ffe569f63a3b","cmdEventType":"VM.CREATE","ctxUserId":"15","zoneid":"a4c20770-f17e-425e-bb21-413dd610b975","signatureversion":"3","httpmethod":"GET","templateid":"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85","networkids":"86e6ded0-6155-449b-a4bd-03411bf0a9cd","ap
KVM CPU Overprovisioning issues.
I'm trying to figure out how CPU over-provisioning works in
cloudstack. It seems that no matter how much I change the
over-provisioning factor value in global settings, I cannot
over-provision CPU allocation on the hosts. I suspect that I'm just
having a lack of understanding on my part, but it seems like I should
be able to increase the number of VMs I can deploy by increasing the
CPU over-provisioning value (given that I'm not close to any other
resource limits). But this doesn't seem to be the case in practice.
https://screencloud.net/v/l1X7
https://screencloud.net/v/9ifx
Error message when trying to create additional machine via API.
grayson@gworkstation:~$ cloudmonkey deploy virtualmachine
zoneid=a4c20770-f17e-425e-bb21-413dd610b975
serviceofferingid=4b391121-49c7-4434-883d-ffe569f63a3b
templateid=e5701f73-b0c3-4dd7-8b2d-b8bf78875a85 keypair=key1
networkids=86e6ded0-6155-449b-a4bd-03411bf0a9cd name=tvmsman1
displayname &
[1] 3907
Async job 09148c21-3c42-4334-93b2-428b48fb1fa2 failed
Error 533, Unable to create a deployment for VM[User|i-15-1151-VM]
accountid = a4e6eaed-9b06-4806-98f9-4fcc781b773f
cmd = org.apache.cloudstack.api.command.user.vm.DeployVMCmd
created = 2015-04-17T13:46:22-0700
jobid = 09148c21-3c42-4334-93b2-428b48fb1fa2
jobprocstatus = 0
jobresult:
errorcode = 533
errortext = Unable to create a deployment for VM[User|i-15-1151-VM]
jobresultcode = 530
jobresulttype = object
jobstatus = 2
userid = c7a0889e-fcec-4095-9d07-d29ea3c1e5d9
(local) mycloudmonkey> list hosts
filter=name,clustername,cpuallocated,cpunumber,cpusockets,cpuspeed,cpuused,cpuwithoverprovisioning,
name = v-78-VM
name = s-871-VM
name = cl2hyper2
clustername = CL2
cpuallocated = 100.3%
cpunumber = 8
cpusockets = 2
cpuspeed = 1994
cpuused = 1.2%
cpuwithoverprovisioning = 63808.0
name = v-1-VM
name = cl2hyper1
clustername = CL2
cpuallocated = 81.45%
cpunumber = 8
cpusockets = 2
cpuspeed = 1995
cpuused = 0.6%
cpuwithoverprovisioning = 63840.0
2015-04-17 13:46:22,517 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-25:ctx-7b0eb43a ctx-751b2eca ctx-5c8a75fc) submit async
job-7312, details: AsyncJobVO {id:7312, userId: 15, accountId: 15,
instanceType: VirtualMachine, instanceId: 1151, cmd:
org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo:
{"serviceofferingid":"4b391121-49c7-4434-883d-ffe569f63a3b","cmdEventType":"VM.CREATE","ctxUserId":"15","zoneid":"a4c20770-f17e-425e-bb21-413dd610b975","signatureversion":"3","httpmethod":"GET","templateid":"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85","networkids":"86e6ded0-6155-449b-a4bd-03411bf0a9cd","apiKey":"wrxDdS8yi2kJPe8UrNdOdLtp55mCSKskk3MyTJ1ucIApdMoYnOWsd-dmigPywD1KC-6BVfVmKiJVenEM_kovpw","id":"1151","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85\",\"com.cloud.vm.VirtualMachine\":\"6b3ace85-8e4c-4467-afdf-b511136ca6b1\",\"com.cloud.network.Network\":\"86e6ded0-6155-449b-a4bd-03411bf0a9cd\",\"com.cloud.dc.DataCenter\":\"a4c20770-f17e-425e-bb21-413dd610b975\",\"com.cloud.offering.ServiceOffering\":\"4b391121-49c7-4434-883d-ffe569f63a3b\"}","expires":"2015-04-17T20:56:22+","keypair":"key1","name":"tvmsman1","uuid":"6b3ace85-8e4c-4467-afdf-b511136ca6b1","ctxAccountId":"15","ctxStartEventId":"11922","signature":"8Ebg1+qjfnk5nv7xz1GtdSju2ws\u003d"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
result: null, initMsid: 345050015385, completeMsid: null, lastUpdated:
null, lastPolled: null, created: null}
2015-04-17 13:46:22,518 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-16:ctx-e039eccb job-7312) Add job-7312 into job
monitoring
2015-04-17 13:46:22,518 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-16:ctx-e039eccb job-7312) Executing AsyncJobVO
{id:7312, userId: 15, accountId: 15, instanceType: VirtualMachine,
instanceId: 1151, cmd:
org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo:
{"serviceofferingid":"4b391121-49c7-4434-883d-ffe569f63a3b","cmdEventType":"VM.CREATE","ctxUserId":"15","zoneid":"a4c20770-f17e-425e-bb21-413dd610b975","signatureversion":"3","httpmethod":"GET","templateid":"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85","networkids":"86e6ded0-6155-449b-a4bd-03411bf0a9cd","apiKey":"wrxDdS8yi2kJPe8UrNdOdLtp55mCSKskk3MyTJ1ucIApdMoYnOWsd-dmigPywD1KC-6BVfVmKiJVenEM_kovpw","id":"1151","response":"json","ctxDetails":"{\"com.cloud.template.VirtualMachineTemplate\":\"e5701f73-b0c3-4dd7-8b2d-b8bf78875a85\",\"com.cloud.vm.VirtualMachine\":\"6b3ace85-8e4c-4467-afdf-b511136ca6b1\",\"com.cloud.network.Network\":\"86e6ded0-6155-449b-a4bd-03411bf0a9cd\",\
