On Thu, 2013-01-24 at 11:40 +1100, Koper, Dies wrote: > Hi Marios, > > For completion's sake, let me describe what I eventually pushed last night. > > > This patch is about the instance entering an error state - not sure if > > 'STOP_ERROR' for example is the same; do you mean it returns an error > > code for instance, or the actual instance goes into the 'stop_error' > > state... in which case you could use the deltacloud error state. > > The actual instance goes into the 'stop_error' state. > Fgcp has three 'error' states, ERROR, STOP_ERROR and START_ERROR. > However, the allowable actions on instances in these states differ. > With ERROR, it seems most operations are not allowed, while STOP_ERROR is > basically equivalent to RUNNING and START_ERROR is equivalent to STOPPED in > respect to what operations you can do on them. > So that is how I have mapped them.
For the sake of completeness, you could have mapped all three to error; describe in the state machine all the actions that are possible from the error state, and list in the actions section of an individual machine only the ones that are possible based on the finer-grained FGCP error states. Though whether what you have vs what I describe is better largely depends on whether the user needs to know that an error happened in START_ERROR or STOP_ERROR. David
