<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Hi Ryan,</div>
<div><br>
</div>
<div>Yes it is a little bit weird, I think the reasons its doing this is likely due to it being the most generic solution to the resizing problem. I believe there is a flag like 'resize_same_host' but I haven't used it that might help.</div>
<div><br>
</div>
<div>I think your concern is valid though and could/should(?) be fixed. </div>
<div><br>
</div>
<div>You could imagine the scheduler 'preferring' the origin compute and the origin compute node in this case doing a 'fast path' resize path that would trigger the compute manager to just move some folders around (instead of invoking the ssh sequence you talked
about). This would seem to make sense to me and would avoid the 'slow path' of actually moving the instance (and disks and so on) to a new node since the origin node doesn't have enough space/cpu/memory… That would make sense to me and likely with beefy enough
compute nodes the 'fast path' would be the common case.</div>
<div><br>
</div>
<div>-Josh</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Ryan Lane <<a href="mailto:rlane@wikimedia.org">rlane@wikimedia.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, May 21, 2013 2:25 PM<br>
<span style="font-weight:bold">To: </span>Juan José Pavlik Salles <<a href="mailto:jjpavlik@gmail.com">jjpavlik@gmail.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>" <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack-operators] resizing an instance<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">On Tue, May 21, 2013 at 2:20 PM, Juan José Pavlik Salles <span dir="ltr">
<<a href="mailto:jjpavlik@gmail.com" target="_blank">jjpavlik@gmail.com</a>></span> wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">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 "<b>ssh root@node2 mkdir -p /var/lib/nova/instances/instances_dir"</b> when trying to resize a VM. Tomorrow i'll trying resizing with shared storage and i'll let you know. </div>
<div class="gmail_extra"><br>
</div>
</blockquote>
<div><br>
</div>
<div style="">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.</div>
<div style=""><br>
</div>
<div style="">Is there some really great reasoning behind this?</div>
<div style=""><br>
</div>
<div style="">- Ryan</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>