<html><body>
<p><font size="2" face="sans-serif">Not only ERROR state, but also VERIFY_RESIZE might have this kind problem </font><br>
<a href="https://review.openstack.org/#/c/101435/"><font size="2" face="sans-serif">https://review.openstack.org/#/c/101435/</font></a><font size="2" face="sans-serif"> has more info </font><br>
<font size="2" face="sans-serif">so guess the server task stuff might be the right direction to those problems ...</font><br>
<br>
<font size="2" face="sans-serif">Best Regards! <br>
<br>
Kevin (Chen) Ji ¼Í ³¿<br>
<br>
Engineer, zVM Development, CSTL<br>
Notes: Chen CH Ji/China/IBM@IBMCN Internet: jichenjc@cn.ibm.com<br>
Phone: +86-10-82454158<br>
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC </font><br>
<br>
<img width="16" height="16" src="cid:1__=C7BBF7F6DFDC4D2F8f9e8a93df938@cn.ibm.com" border="0" alt="Inactive hide details for Chris Friesen ---10/02/2014 03:05:20 AM---Currently in nova we have the "vm_state", which according t"><font size="2" color="#424282" face="sans-serif">Chris Friesen ---10/02/2014 03:05:20 AM---Currently in nova we have the "vm_state", which according to the code comments is supposed to repre</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Chris Friesen <chris.friesen@windriver.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">10/02/2014 03:05 AM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[openstack-dev] [nova] formally distinguish server "desired state" from "actual state"?</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<tt><font size="2"><br>
Currently in nova we have the "vm_state", which according to the code <br>
comments is supposed to represent "a VM's current stable (not <br>
transition) state", or "what the customer expect the VM to be".<br>
<br>
However, we then added in an ERROR state. How does this possibly make <br>
sense given the above definition? Which customer would ever expect the <br>
VM to be in an error state?<br>
<br>
Given this, I wonder whether it might make sense to formally distinguish <br>
between the expected/desired state (i.e. the state that the customer <br>
wants the VM to be in), and the actual state (i.e. the state that nova <br>
thinks the VM is in).<br>
<br>
This would more easily allow for recovery actions, since if the actual <br>
state changes to ERROR (or similar) we would still have the <br>
expected/desired state available for reference when trying to take <br>
recovery actions.<br>
<br>
Thoughts?<br>
<br>
Chris<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
<br>
</font></tt><br>
</body></html>