Hi
I stumbled upon behavior in the deltacloud API that I did not expect:
I started an instance in the AWS console, and went to the deltacloud
tools. I then stopped the instance and the following behaviour differs
from what I'd have expected:
- after stopping the instance, the response from the deltacloud server
states that the instance is STOPPED. Chatting to bbrowing in the IRC
showed me that stopping ec2 instances results in destroying them. If
this is the way things have to be, I would have expected state DESTROYED
in the response. Any objections, ideas, hints?
- when I tried to start it again, I recieved a 302. I'd expect a 404
here since this is a client error (4xx) and more specifically, the
resource I address does not exist. Agree?
Thanks!
Cheers
André