The old API changeServiceForVirtualMachine too can be used for scaling up a
running vm that too above host capacity (both RAM and CPU) without any
over-provisioning. I have created issue for this -->
https://issues.apache.org/jira/browse/CLOUDSTACK-4881
Regards,
Gaurav
On Wed, Oct 16, 2013 at 5:
I have logged issue https://issues.apache.org/jira/browse/CLOUDSTACK-4880 for
this. I will check bevavior for changeServiceForVirtualMachine API too and
log issue if confirmed.
Regards,
Gaurav
On Wed, Oct 16, 2013 at 4:46 PM, Harikrishna Patnala <
harikrishna.patn...@citrix.com> wrote:
> Yes Ga
Yes Gaurav, please file a bug ticket for this issue. We should also consider
host cpu cores while scaling up the VM.
If you want to check for changeServiceForVirtualMachine API, try it on stopped
vm since the API is meant for only stopped vms.
Thankyou
Harikrishna
On 16-Oct-2013, at 4:16 PM, G
Hi Nitin,
I am able to scale a virtual machine (using scaleVirtualMachine API) to use
5 CPU cores where as the host has only 4 physical CPU cores. According to
David, this should not be the case. I can also reboot this instance. But I
can't create a new instance with this scaled up service offerin
changeServiceForVirtualMachine API was the old API to change the service
offering for a stopped vm only.
I think it shouldn't have succeeded for a running vm. Please file a bug if
this is the case
scaleVirtualMachine is the new API introduced in 4.2 for scaling a
running/stopped vm. Do read the li
Hi Nitin,
I was trying on running vm only, but I was
using changeServiceForVirtualMachine API instead of scaleVirtualMachine API.
But I wonder why changeServiceForVirtualMachine API succeeded in allocating
more than host capacity.
What is the basic difference between these two operations?
Regard
Gaurav - Were you trying this on a stopped vm ? If you try and start it
with an offering
above the host capacity (including over provisioning ) then it shouldn't
start. Let me know how it goes.
More details on scale vm feature @
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Dynamic+scali
Thanks David. That disabuses my confusion about the CPU provisioning. I was
using the wrong API to scale up the virtual machine, so above observations
stand invalid till I get the same results with the right API.
About over-provisioning, I have the over provisioning factor set as 1 both
in case of
A machine won't be able to support more cores on a VM than the physical
processor. That should result in problems trying to deploy it. I'm guessing
the service offering is still valid since you could add a host later which has
a hex core or two cpus in it. As far as RAM goes, do you have over
