Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Component/s: Server
    • Labels:
      None

      Description

      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?

        Activity

        Hide
        Michal Fojtik added a comment -

        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.

        Show
        Michal Fojtik added a comment - 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.
        Hide
        Ronelle Landy added a comment -

        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

        Show
        Ronelle Landy added a comment - 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

          People

          • Assignee:
            David Lutterkort
            Reporter:
            Jozef Zigmund
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development