<div style="font-family: Helvetica; font-size: 13px;"><span style="color: rgb(160, 160, 168);">On Wednesday, 8 January, 2014 at 22:53, John Garbutt wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>On 8 January 2014 10:02, David Xie <<a href="mailto:david.scriptfan@gmail.com">david.scriptfan@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div>In nova/compute/api.py#2289, function resize, there's a parameter named</div><div>flavor_id, if it is None, it is considered as cold migration. Thus, nova</div><div>should skip resize verifying. However, it doesn't.</div><div><br></div><div>Like Jay said, we should skip this step during cold migration, does it make</div><div>sense?</div></div></blockquote><div><br></div><div>Not sure.</div><div><br></div><blockquote type="cite"><div><div>On Wed, Jan 8, 2014 at 5:52 PM, Jay Lau <<a href="mailto:jay.lau.513@gmail.com">jay.lau.513@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div><br></div><div>Greetings,</div><div><br></div><div>I have a question related to cold migration.</div><div><br></div><div>Now in OpenStack nova, we support live migration, cold migration and</div><div>resize.</div><div><br></div><div>For live migration, we do not need to confirm after live migration</div><div>finished.</div><div><br></div><div>For resize, we need to confirm, as we want to give end user an opportunity</div><div>to rollback.</div><div><br></div><div>The problem is cold migration, because cold migration and resize share</div><div>same code path, so once I submit a cold migration request and after the cold</div><div>migration finished, the VM will goes to verify_resize state, and I need to</div><div>confirm resize. I felt a bit confused by this, why do I need to verify</div><div>resize for a cold migration operation? Why not reset the VM to original</div><div>state directly after cold migration?</div></div></blockquote></div></blockquote><div><br></div><div>I think the idea was allow users/admins to check everything went OK,</div><div>and only delete the original VM when the have confirmed the move went</div><div>OK.</div><div><br></div><div>I thought there was an auto_confirm setting. Maybe you want</div><div>auto_confirm cold migrate, but not auto_confirm resize?</div><div><br></div></div></div></span></blockquote><div><font color="#0433ff">[David] If user run cold migration command by CLI, confirmation does make sense. But what if this action is called by a service or other process, there’s no chance for user to confirm it and maybe it’s better to auto confirm it.</font></div><div><font color="#0433ff"><br></font></div><div><font color="#0433ff">BTW, is there a auto_confirm setting for cold migration? If so, that’s all what I need.</font></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><div></div><blockquote type="cite"><blockquote type="cite"><div><div>Also, I think that probably we need split compute.api.resize() to two</div><div>apis: one is for resize and the other is for cold migrations.</div><div><br></div><div>1) The VM state can be either ACTIVE and STOPPED for a resize operation</div><div>2) The VM state must be STOPPED for a cold migrate operation.</div></div></blockquote></blockquote><div><br></div><div>We just stop the VM them perform the migration.</div><div>I don't think we need to require its stopped first.</div><div>Am I missing something?</div><div><br></div><div>Thanks,</div><div>John</div><div><br></div><div>_______________________________________________</div><div>OpenStack-dev mailing list</div><div><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a></div><div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>