Open Stack

Hi Ryan,
a resize changes your instance "size" so makes sense to schedule the best node for it.
Also, the node that is currently running the instance may not have the available resources available for the resized instance.

The "allow_resize_to_same_host" only guaranties that the current node will not be excluded from the schedule.

cheers,
Belmiro


On May 21, 2013, at 11:25 PM, Ryan Lane <rlane at wikimedia.org> wrote:

> On Tue, May 21, 2013 at 2:20 PM, Juan José Pavlik Salles <jjpavlik at gmail.com> wrote:
> I'm not sure about your deployment, but i noticed that when i try to resize a vm nova also tries to move the vm to another compute-node, so if you don't have a shared storage for the VMs this is not possible (unless your compute-node can ssh to the other compute-node ofcourse). I found in my logs thigs like "ssh root at node2 mkdir -p /var/lib/nova/instances/instances_dir" when trying to resize a VM. Tomorrow i'll trying resizing with shared storage and i'll let you know. 
> 
> 
> Yes. This is the weirdest behavior. Why in the world is it necessary to move the instance to another compute node just to do a resize? It requires ssh between instances, makes the process *much* slower and also makes it way more error prone. I don't get it. This seems like a really convoluted way of handling resizes.
> 
> Is there some really great reasoning behind this?
> 
> - Ryan
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators