Re: [openstack-dev] [nova] formally distinguish server desired state from actual state?

2014-10-02 Thread Chen CH Ji
@lists.openstack.org Date: 10/02/2014 03:05 AM Subject:[openstack-dev] [nova] formally distinguish server desired state from actual state? Currently in nova we have the vm_state, which according to the code comments is supposed to represent a VM's current stable (not transition

[openstack-dev] [nova] formally distinguish server desired state from actual state?

2014-10-01 Thread Chris Friesen
Currently in nova we have the vm_state, which according to the code comments is supposed to represent a VM's current stable (not transition) state, or what the customer expect the VM to be. However, we then added in an ERROR state. How does this possibly make sense given the above

Re: [openstack-dev] [nova] formally distinguish server desired state from actual state?

2014-10-01 Thread Chris Friesen
On 10/01/2014 01:23 PM, Jay Pipes wrote: On 10/01/2014 03:07 PM, Chris Friesen wrote: Currently in nova we have the vm_state, which according to the code comments is supposed to represent a VM's current stable (not transition) state, or what the customer expect the VM to be. However, we then

Re: [openstack-dev] [nova] formally distinguish server desired state from actual state?

2014-10-01 Thread Johannes Erdfelt
On Wed, Oct 01, 2014, Chris Friesen chris.frie...@windriver.com wrote: Currently in nova we have the vm_state, which according to the code comments is supposed to represent a VM's current stable (not transition) state, or what the customer expect the VM to be. However, we then added in an

Re: [openstack-dev] [nova] formally distinguish server desired state from actual state?

2014-10-01 Thread Jay Pipes
On 10/01/2014 04:31 PM, Chris Friesen wrote: On 10/01/2014 01:23 PM, Jay Pipes wrote: On 10/01/2014 03:07 PM, Chris Friesen wrote: Currently in nova we have the vm_state, which according to the code comments is supposed to represent a VM's current stable (not transition) state, or what the