On Sat, Apr 18, 2009 at 1:43 PM, Chris Webb <chris.webb@elastichosts.com> wrote:

Sam Johnston <samj@samj.net> writes:

> I have created a diagram (attached) of what I think the absolute minimum
> core states need to be... essentially boiling them down to "STOPPED" and
> "ACTIVE" with "START" and "STOP" being the only requisite actuators.
> Transitional "STOPPING" and "STARTING" states are optional.

+1

I strongly agree with simplifying things in this way. Good stuff!

I subsequently realised that in fact infrastructure like Amazon, Mosso and ElasticHosts don't actually have a "stopped" state - "stop" for these guys is more like "destroy".

It then occurred to me that there was no point making "stopped" optional as if you don't need to start/stop/restart machines then you just don't implement the machine control extension. It's far easier to create (HTTP PUT) and then destroy (HTTP DELETE) a server than what it is to parse the response to fire an actuator.

So basically the machine control extension becomes optional (but possibly still interesting to indicate transitional states like "starting" and "stopping" as Chris pointed out privately).

Sam