DeltaCloud
  1. DeltaCloud
  2. DTACLOUD-8

stopping an ec2 instance reports start to be an available action

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Component/s: None
    • Labels:
      None
    • Environment:
      deltacloud 0.0.9, REST API

      Description

      If you perform an action on an instance, Deltacloud answers with the actions that are available to it. Perfect REST style.

      If you stop an instance that runs on ec2, deltacloud responds with the actions that are available to it. For a stopped instance, Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

      • Request to stop an instance:

      POST /api/instances/i-00e28a6d/stop HTTP/1.1

      • Response from Deltacloud (see <actions />):

      <?xml version='1.0' encoding='utf-8' ?>
      <instance href='http://localhost:3002/api/instances/i-00e28a6d' id='i-00e28a6d'>
      <name>ami-7d07ec14</name>
      <image href='http://localhost:3002/api/images/ami-7d07ec14' id='ami-7d07ec14'></image>
      <realm href='http://localhost:3002/api/realms/us-east-1a' id='us-east-1a'></realm>
      <state>STOPPED</state>
      <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small' id='m1.small'>
      </hardware_profile>
      <actions>
      <link href='http://localhost:3002/api/instances/i-00e28a6d/start' method='post' rel='start' />
      </actions>
      <launch_time>2010-11-19T12:23:06.000Z</launch_time>
      <public_addresses>
      <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
      </public_addresses>
      <private_addresses>
      <address>ip-10-112-38-207.ec2.internal</address>
      </private_addresses>
      <authentication type='key'>
      <login>
      <keyname>ad</keyname>
      </login>
      </authentication>
      </instance>

        Issue Links

          Activity

          André Dietisheim created issue -
          André Dietisheim made changes -
          Field Original Value New Value
          Description If you stop an instance on ec2, the respond to it, report start to be available to this instance. If you check the AWS console, you'd see that neither start nor destroy is available. Deltacloud answers with the available actions to an instance if you perform actions on it. Perfect REST style.
          If you stop an instance on ec2, deltacloud responds with the actions that are available to the instance you stopped. Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          Respond from Deltacloud (see <actions />):


          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          André Dietisheim made changes -
          Description Deltacloud answers with the available actions to an instance if you perform actions on it. Perfect REST style.
          If you stop an instance on ec2, deltacloud responds with the actions that are available to the instance you stopped. Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          Respond from Deltacloud (see <actions />):


          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          Deltacloud answers with the available actions to an instance if you perform actions on it. Perfect REST style.
          If you stop an instance that runs on ec2, deltacloud responds with the actions that are available to it. For a stopped instance, Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          Respond from Deltacloud (see <actions />):


          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          André Dietisheim made changes -
          Environment deltacloud 0.0.9 deltacloud 0.0.9, REST API
          André Dietisheim made changes -
          Description Deltacloud answers with the available actions to an instance if you perform actions on it. Perfect REST style.
          If you stop an instance that runs on ec2, deltacloud responds with the actions that are available to it. For a stopped instance, Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          Respond from Deltacloud (see <actions />):


          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          If you perform an action on an instance, Deltacloud answers with the actions that are available to it. Perfect REST style.

          If you stop an instance that runs on ec2, deltacloud responds with the actions that are available to it. For a stopped instance, Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          Respond from Deltacloud (see <actions />):


          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          André Dietisheim made changes -
          Description If you perform an action on an instance, Deltacloud answers with the actions that are available to it. Perfect REST style.

          If you stop an instance that runs on ec2, deltacloud responds with the actions that are available to it. For a stopped instance, Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          Respond from Deltacloud (see <actions />):


          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          If you perform an action on an instance, Deltacloud answers with the actions that are available to it. Perfect REST style.

          If you stop an instance that runs on ec2, deltacloud responds with the actions that are available to it. For a stopped instance, Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          * Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          * Respond from Deltacloud (see <actions />):

          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          André Dietisheim made changes -
          Description If you perform an action on an instance, Deltacloud answers with the actions that are available to it. Perfect REST style.

          If you stop an instance that runs on ec2, deltacloud responds with the actions that are available to it. For a stopped instance, Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          * Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          * Respond from Deltacloud (see <actions />):

          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          If you perform an action on an instance, Deltacloud answers with the actions that are available to it. Perfect REST style.

          If you stop an instance that runs on ec2, deltacloud responds with the actions that are available to it. For a stopped instance, Deltacloud reports "start" to be available. IMHO this is bogus since the AWS console does not offer START nor DESTROY to instances that are stopped.

          * Request to stop an instance:

          POST /api/instances/i-00e28a6d/stop HTTP/1.1

          * Response from Deltacloud (see <actions />):

          <?xml version='1.0' encoding='utf-8' ?>
          <instance href='http://localhost:3002/api/instances/i-00e28a6d&#39; id='i-00e28a6d'>
            <name>ami-7d07ec14</name>
            <image href='http://localhost:3002/api/images/ami-7d07ec14&#39; id='ami-7d07ec14'></image>
            <realm href='http://localhost:3002/api/realms/us-east-1a&#39; id='us-east-1a'></realm>
            <state>STOPPED</state>
            <hardware_profile href='http://localhost:3002/api/hardware_profiles/m1.small&#39; id='m1.small'>
            </hardware_profile>
            <actions>
              <link href='http://localhost:3002/api/instances/i-00e28a6d/start&#39; method='post' rel='start' />
            </actions>
            <launch_time>2010-11-19T12:23:06.000Z</launch_time>
            <public_addresses>
              <address>ec2-184-72-186-65.compute-1.amazonaws.com</address>
            </public_addresses>
            <private_addresses>
              <address>ip-10-112-38-207.ec2.internal</address>
            </private_addresses>
            <authentication type='key'>
              <login>
                <keyname>ad</keyname>
              </login>
            </authentication>
          </instance>
          Michal Fojtik made changes -
          Link This issue relates to DTACLOUD-9 [ DTACLOUD-9 ]
          Ronelle Landy made changes -
          Link This issue duplicates DTACLOUD-111 [ DTACLOUD-111 ]

            People

            • Assignee:
              David Lutterkort
              Reporter:
              André Dietisheim
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development