[
https://issues.apache.org/jira/browse/LIBCLOUD-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987918#comment-13987918
]
zahlenofzahlen commented on LIBCLOUD-546:
-----------------------------------------
While evaluating this it's apparent that we also need to extend the NodeState
to handle a stopped state and add a stop_node / start_node function. Imaging
running nodes is unpredictable and often results in failure or bootstrapping
components, etc. I'll open an additional issue for the added node_states.
> Add support for states in NodeImage object
> ------------------------------------------
>
> Key: LIBCLOUD-546
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-546
> Project: Libcloud
> Issue Type: New Feature
> Components: Compute
> Reporter: zahlenofzahlen
> Priority: Minor
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> The NodeImage object could benefit from the use of a state attribute. This
> way when users are calling create_image and polling with get_image they can
> set the current state returned from the provider API. The states will need a
> mapper in types.py to map a generic state table to each provider specific
> state.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
