deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Fojtik (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-195) Instance states - need info
Date Wed, 09 May 2012 12:55:51 GMT


Michal Fojtik commented on DTACLOUD-195:

For the EC2:

It's a compromise we made to support both models. Basically you can destroy the non-ebs instances
and they disappear after a while. This is indicated by proper HTTP return code (HTTP_ACCEPTED).
For the EBS instances we would need to support different state machine, which currently we
do not support. So if you destroy the EBS instance, DC will stop it but do not remove it.
This need to be done using external tools or manually through EC2 GUI.

Basically the transitions for the non-EBS instance are:

RUNNING.on(:stop) -> STOPPED.on(:automatically) -> DESTROYED

For the EBS instance:

RUNNING.on(:stop) -> STOPPED.on(:destroy) -> DESTROYED

In other words, you need to do two operations in order to destroy the EBS instance completely,
which is not stateless (you would need to wait for the :stop action to finish)


That is probably a bug and we should have such transition of someone don't prove me wrong.

> Instance states - need info
> ---------------------------
>                 Key: DTACLOUD-195
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>            Reporter: Jozef Zigmund
>            Assignee: David Lutterkort
> I'd like to ask for better understanding of your instance states.
> For EC2: 
> Why DC cannot stop the instance but only destroy? (I see that EC2's destroying instance
when it's stopped, but seems that it doesnt destroy EBS instance)
> When I reboot instance via AWS, I see the state 'Rebooting' in GUI, but in DC EC2 driver
I dont see that state, any reason for that?
> For RHEV-M:
> Why RHEVM driver doesnt have set transition from stopping to stopped?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message