deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DTACLOUD-61) Unable to destroy EBS based instance in EC2
Date Fri, 28 Jun 2013 09:11:24 GMT

     [ https://issues.apache.org/jira/browse/DTACLOUD-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marios Andreou closed DTACLOUD-61.
----------------------------------

    Resolution: Fixed

closing as resolved by ticket https://issues.apache.org/jira/browse/DTACLOUD-557
                
> Unable to destroy EBS based instance in EC2
> -------------------------------------------
>
>                 Key: DTACLOUD-61
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-61
>             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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message