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

Posted to notifications@libcloud.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/06/13 14:28:00 UTC

[jira] [Commented] (LIBCLOUD-710) CloudSigma driver doesn't take advantage of new(er) NodeStates

    [ https://issues.apache.org/jira/browse/LIBCLOUD-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584587#comment-14584587 ] 

ASF GitHub Bot commented on LIBCLOUD-710:
-----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/libcloud/pull/517


> CloudSigma driver doesn't take advantage of new(er) NodeStates
> --------------------------------------------------------------
>
>                 Key: LIBCLOUD-710
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-710
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>            Reporter: Chris O'Brien
>            Priority: Minor
>
> The NodeStates 'ERROR', and 'PAUSED' are not utilized for the corresponding CloudSigma statuses (in CloudSigma_2_0_NodeDriver's NODE_STATE_MAP) 'unavailable' and 'paused'.  
> I propose having CloudSigma's 'unavailable' state translate to NodeState.ERROR and the 'paused' state translate to NodeState.PAUSED (duh...).  



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