You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Jozef Zigmund (Created) (JIRA)" <ji...@apache.org> on 2012/04/17 17:16:20 UTC
[jira] [Created] (DTACLOUD-195) Instance states - need info
Instance states - need info
---------------------------
Key: DTACLOUD-195
URL: https://issues.apache.org/jira/browse/DTACLOUD-195
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-195) Instance states - need info
Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271379#comment-13271379 ]
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)
For RHEV-M:
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: https://issues.apache.org/jira/browse/DTACLOUD-195
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-195) Instance states - need info
Posted by "Ronelle Landy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255773#comment-13255773 ]
Ronelle Landy commented on DTACLOUD-195:
----------------------------------------
Waiting for dev to comment further, however including some additional info below:
ec2 instance-store vs. EBS, stop vs. destroy is an open issue
See related JIRAs: DTACLOUD-100, 101, 61 and 8
For RHEV-M: the state transitions differ depending on the version of deltacloud in use:
for deltacloud 0.5.0 (included in CloudForms release):
>> instanceCreated.stop!
Instance state goes from RUNNING -> PENDING -> STOPPED
for deltacloud version in git master branch (6499cf7feba60ccdd26a750627b4df7d798036e6 branch 'master' of https://git-wip-us.apache.org/repos/asf/deltacloud)
>> instanceCreated.stop!
Instance state goes from RUNNING -> STOPPING -> STOPPED
> Instance states - need info
> ---------------------------
>
> Key: DTACLOUD-195
> URL: https://issues.apache.org/jira/browse/DTACLOUD-195
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira