incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lalancette (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-61) Unable to destroy EBS based instance in EC2
Date Tue, 19 Jul 2011 15:52:57 GMT


Chris Lalancette commented on DTACLOUD-61:

I also took a look at this a while back, but didn't have time to follow-up.

Personally, I think a separate state machine for non-EBS and EBS instances makes the most
sense.  They have different transitions to different states, and it will be easier to debug
them in the future if they are separated out.  When I briefly looked at it before, it wasn't
entirely clear to me how to tell whether this was an EBS instance or a non-EBS instance, but
assuming we can discover that this should be doable.

> Unable to destroy EBS based instance in EC2
> -------------------------------------------
>                 Key: DTACLOUD-61
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: deltacloud-core-0.3.0
>            Reporter: Michal Fojtik
>            Assignee: David Lutterkort
>              Labels: drivers, ec2
> State machine currently defined for EC2 drivers allow client to 'stop' non-EBS instance
which mean that this instance will be destroyed. But this only works for non-EBS instance.
If you have EBS instance stop action will just 'stop' the instance and this instance will
remain in 'STOPPED' state and need to be destroyed manually using Amazon web interface.
> So far I have this solutions:
>  - Replace 'stop' with destroy, where this action will 'stop' non-EBS instance and 'destroy'
EBS instance
>  - Add 'destroy' action to state machine, where in non-EBS instance this action will
return 202 (Accepted) which is AFAIK ok for client.
>  - Make separate state machine for non-EBS and EBS instances 

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message