You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/01/23 23:10:34 UTC

[jira] [Updated] (JCLOUDS-2) document effect of ComputeService operations with different node states

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

Andrew Gaul updated JCLOUDS-2:
------------------------------
    Component/s: jclouds-compute

> document effect of ComputeService operations with different node states
> -----------------------------------------------------------------------
>
>                 Key: JCLOUDS-2
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-2
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-compute
>            Reporter: Dies Koper
>
> Make the behaviour of ComputeService operations consistent across providers by first including in their javadoc how they operate on nodes with different states.
> E.g.,
> - suspendNode on a node that is already suspended: throws IAE, or NOP?
> - suspendNode on a node that is currently starting: throws IAE, or waits (loops) until node has started and then tries to suspend it.
> - destroyNode on a node that is currently running, starting, creating... IAE or wait and bring it to a provider depending state in which it can be destroyed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)