On Fri, Apr 17, 2009 at 3:23 PM, Tino Vazquez <span dir="ltr">&lt;<a href="mailto:tinova@fdi.ucm.es">tinova@fdi.ucm.es</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div id=":1hb" class="ii gt">IMHO I think &quot;migrating&quot;  and/or &quot;migrated&quot; are states that doesn&#39;t<br>
make sense under the point of view of a Cloud API, this should be<br>
something internal completely transparent to the user. Also, I am not<br>
sure that we need the &quot;copied&quot; state. What does it mean exactly?<br>
<br>
Aside from that I kind of like the model. I would suggest adding a<br>
&quot;suspending&quot; state (or &quot;saving&quot; since it presumabley the VM is going<br>
to dump a snapshot) and also a &quot;finished&quot; state and &quot;failed&quot; state to<br>
handle errors.<br>
<br>
What do you think?</div></blockquote></div><br>My dead tree version has states like:<br><br>STOPPED<br>RESTORING/STARTING<br>STARTED<br>SUSPENDING/STOPPING<br><br>It was derived (at least in part) from the <a href="http://msdn.microsoft.com/en-us/library/aa368893%28VS.85%29.aspx">Microsoft Virtual Server state diagram</a>.<br>
<br>As a user of cloud services giving sensible and consistent visual feedback during the state changes is <i>very</i> important for the user experience.<br><br>Sam<br><br>