[
https://issues.apache.org/jira/browse/DTACLOUD-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
André Dietisheim updated DTACLOUD-8:
------------------------------------
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>
was:
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' 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>
> stopping an ec2 instance reports start to be an available action
> ----------------------------------------------------------------
>
> Key: DTACLOUD-8
> URL: https://issues.apache.org/jira/browse/DTACLOUD-8
> Project: DeltaCloud
> Issue Type: Bug
> Environment: deltacloud 0.0.9, REST API
> Reporter: André Dietisheim
> Assignee: David Lutterkort
>
> 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
