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

Gaurav Aradhye commented on CLOUDSTACK-2181:
--------------------------------------------

Hi Prashant,

looks like I was using wrong API for scaling operation. Can you tell me what 
settings related to setup are required for testing scale vm scenarios? I have 
enabled the "enable.dynamic.scale.vm" option for zone, still in KVM its failing 
saying "This operation not permitted for this hypervisor of the vm", and on 
XenServer it says "Dynamic memory control is not enabled for the XenServer". Am 
I missing any setting?

> Scale down is allowed  when  one resource(say cpu) is being scale up and 
> other resource (say ram)is being scale down ;but not allowed when both 
> resources are being scaledown 
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2181
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2181
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server, XenServer
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: Harikrishna Patnala
>            Priority: Minor
>             Fix For: 4.2.0
>
>         Attachments: apilog.log, catalina.out, management-server.log, 
> scaleup.png
>
>
> Scale down is not allowed as per FS and condition is valid when you try to 
> scale down both resources (cpu and RAM); but not valid when you try to scale 
> up one resource and scale down other resource
> Steps to repo
> ------------------
> 1-Deploy a vm with small instance SO
> 2-create three service offering say a1, a2 ,a3 (a1{cpu=1 
> GHz,ram=256};a2{cpu=500MGz,ram=512};a3{cpu=300 MGz,ram=256})
> 3-try to scaledown to service offering a3 (it will fail with message "Only 
> scaling up the vm is supported, new service offering should have both cpu and 
> memory greater than the old values")
> 4-Try to scaleup to SO a1(successful)
> 5-Try to scaleup to SO a2 from a1(successful)
> Expected
> --------------
> AS per FS scale down should not be allowed in any case
> Snippet of Log
> -----------------------
> -----------------------
> 1-VM details
> ------------------
> 2013-04-25 08:50:27,150 DEBUG [agent.transport.Request] 
> (Job-Executor-7:job-171) Seq 5-1339424813: Sending  { Cmd , MgmtId: 
> 7635042566263, via: 5, Ver: v1, Flags: 100111, 
> [{"StartCommand":{"vm":{"id":29,"name":"i-2-29-VM","bootloader":"PyGrub","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
>  5.3 
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"f406158baa072feb","params":{},"uuid":"3355e0f2-d9c7-4fc1-adad-d6337adea271","disks":[{"id":39,"name":"ROOT-29","mountPoint":"/export/home/prashant/asfprime","path":"d1e10716-38ec-4d02-b785-6d3c9e381779","size":21474836480,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"59f08402-b4ed-3a26-9d59-eb04cc22886b","deviceId":0},{"id":29,"name":"CentOS
>  5.6(64-bit) no GUI 
> (XenServer)","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"e86fb52c-4e3e-4963-99c9-197038404f25","ip":"10.1.1.61","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:73:4c:00:18","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1101","isolationUri":"vlan://1101","isSecurityGroupEnabled":false}]},"hostIp":"10.147.40.8","wait":0}}]
>  }
> 2013-04-25 08:50:27,153 DEBUG [agent.transport.Request] 
> (Job-Executor-7:job-171) Seq 5-1339424813: Executing:  { Cmd , MgmtId: 
> 7635042566263, via: 5, Ver: v1, Flags: 100111, 
> [{"StartCommand":{"vm":{"id":29,"name":"i-2-29-VM","bootloader":"PyGrub","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
>  5.3 
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"f406158baa072feb","params":{},"uuid":"3355e0f2-d9c7-4fc1-adad-d6337adea271","disks":[{"id":39,"name":"ROOT-29","mountPoint":"/export/home/prashant/asfprime","path":"d1e10716-38ec-4d02-b785-6d3c9e381779","size":21474836480,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"59f08402-b4ed-3a26-9d59-eb04cc22886b","deviceId":0},{"id":29,"name":"CentOS
>  5.6(64-bit) no GUI 
> (XenServer)","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"e86fb52c-4e3e-4963-99c9-197038404f25","ip":"10.1.1.61","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:73:4c:00:18","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1101","isolationUri":"vlan://1101","isSecurityGroupEnabled":false}]},"hostIp":"10.147.40.8","wait":0}}]
>  }
> 2013-04-25 08:50:27,154 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-29:null) Seq 5-1339424813: Executing request
> 2013-04-25 08:50:27,236 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-29:null) 1. The VM i-2-29-VM is in Starting state
> 2-Scale down(cpu and ram) to a3
> ------------------------------
> 2013-04-25 08:53:37,706 INFO  [cloud.api.ApiServer] (catalina-exec-3:null) 
> Only scaling up the vm is supported, new service offering should have both 
> cpu and memory gre
> 3-Scale up cpu and  scale down ram->SO a1
> -----------------------------------------
> 2013-04-25 08:55:33,229 DEBUG [agent.transport.Request] 
> (catalina-exec-24:null) Seq 5-1339424827: Sending  { Cmd , MgmtId: 
> 7635042566263, via: 5, Ver: v1, Flags: 100111, 
> [{"ScaleVmCommand":{"vm":{"id":1,"name":"i-2-29-VM","cpus":1,"speed":1000,"minRam":256,"maxRam":256,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false},"vmName":"i-2-29-VM","cpus":1,"speed":1000,"minRam":256,"maxRam":256,"wait":0}}]
>  }
> 2013-04-25 08:55:33,230 DEBUG [agent.transport.Request] 
> (catalina-exec-24:null) Seq 5-1339424827: Executing:  { Cmd , MgmtId: 
> 7635042566263, via: 5, Ver: v1, Flags: 100111, 
> [{"ScaleVmCommand":{"vm":{"id":1,"name":"i-2-29-VM","cpus":1,"speed":1000,"minRam":256,"maxRam":256,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false},"vmName":"i-2-29-VM","cpus":1,"speed":1000,"minRam":256,"maxRam":256,"wait":0}}]
>  }
> 2013-04-25 08:55:33,231 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-13:null) Seq 5-1339424827: Executing request
> 2013-04-25 08:55:37,735 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-13:null) scaling VM i-2-29-VM is successful on host 
> com.xensource.xenapi.Host@d9987304
> 2013-04-25 08:55:37,735 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-13:null) Seq 5-1339424827: Response Received:
> 2013-04-25 08:55:37,736 DEBUG [agent.transport.Request] (DirectAgent-13:null) 
> Seq 5-1339424827: Processing:  { Ans: , MgmtId: 7635042566263, via: 5, Ver: 
> v1, Flags: 110, [{"ScaleVmAnswer":{"result":true,"details":"scaling VM 
> i-2-29-VM is successful on host 
> com.xensource.xenapi.Host@d9987304","wait":0}}] }
> 3-Scale up ram and down cpu->SO a2
> 2013-04-25 08:55:48,187 DEBUG [agent.transport.Request] 
> (catalina-exec-2:null) Seq 5-1339424828: Sending  { Cmd , MgmtId: 
> 7635042566263, via: 5, Ver: v1, Flags: 100111, 
> [{"ScaleVmCommand":{"vm":{"id":1,"name":"i-2-29-VM","cpus":1,"speed":500,"minRam":1024,"maxRam":1024,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false},"vmName":"i-2-29-VM","cpus":1,"speed":500,"minRam":1024,"maxRam":1024,"wait":0}}]
>  }
> 2013-04-25 08:55:48,188 DEBUG [agent.transport.Request] 
> (catalina-exec-2:null) Seq 5-1339424828: Executing:  { Cmd , MgmtId: 
> 7635042566263, via: 5, Ver: v1, Flags: 100111, 
> [{"ScaleVmCommand":{"vm":{"id":1,"name":"i-2-29-VM","cpus":1,"speed":500,"minRam":1024,"maxRam":1024,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false},"vmName":"i-2-29-VM","cpus":1,"speed":500,"minRam":1024,"maxRam":1024,"wait":0}}]
>  }
> 2013-04-25 08:55:48,189 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-43:null) Seq 5-1339424828: Executing request
> 2013-04-25 08:55:49,664 DEBUG [xen.resource.CitrixResourceBase] 
> (DirectAgent-43:null) scaling VM i-2-29-VM is successful on host 
> com.xensource.xenapi.Host@d9987304
> 2013-04-25 08:55:49,665 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-43:null) Seq 5-1339424828: Response Received:
> 2013-04-25 08:55:49,666 DEBUG [agent.transport.Request] (DirectAgent-43:null) 
> Seq 5-1339424828: Processing:  { Ans: , MgmtId: 7635042566263, via: 5, Ver: 
> v1, Flags: 110, [{"ScaleVmAnswer":{"result":true,"details":"scaling VM 
> i-2-29-VM is successful on host 
> com.xensource.xenapi.Host@d9987304","wait":0}}] }



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to