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. Regards, Dies Koper > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Thursday, 20 December 2012 7:12 PM > To: [email protected] > Cc: Koper, Dies > Subject: Re: Adding an error state to the instance state machine > > On 20/12/12 05:50, Koper, Dies wrote: > > (How) do we advertise what operations are possible on a machine in the > error state? > > you can use the existing syntax - i've made 'error' a bona-fide state > now, so you could do something like: > > error.to(:finish) .on(:destroy) > > for example. > > > From the documentation, Fgcp API can return STOP_ERROR when it failed > to stop, START_ERROR when it failed to start and ERROR in other error cases > (error during fail-over, creating snapshots, etc.). > > 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. > > > marios > > > > > Regards, > > Dies Koper > > > > > >> -----Original Message----- > >> From: Michal Fojtik [mailto:[email protected]] > >> Sent: Thursday, 20 December 2012 8:04 AM > >> To: [email protected] > >> Subject: Re: Adding an error state to the instance state machine > >> > >> +1 oVirt and possibly VSphere does have 'UNKNOWN' or 'ERROR' state too. > In > >> that case only possible operation is 'destroy'. > >> > >> > >> On Wed, Dec 19, 2012 at 11:57 PM, David Lutterkort > >> <[email protected]>wrote: > >> > >>> On Wed, 2012-12-19 at 19:27 +0200, [email protected] wrote: > >>>> basically $SUBJECT... openstack instances (and likely other clouds too) > >>>> can enter a 'error' state. This adds the new state and a 'from' keyword > >>>> to the state machine dsl... comments on syntax etc welcome (e.g. > making > >>> this an > >>>> 'auto' transition, makes sense?) > >>>> > >>>> thanks, marios > >>> > >>> ACK; makes sense to me. > >>> > >>> David > >>> > >>> > >>> > >> > >> > >> -- > >> ----------------------------------------------- > >> Michal Fojtik <[email protected]> > >> Enthusiastic Ruby programmer. >
