You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Andrew Starr-Bochicchio (JIRA)" <ji...@apache.org> on 2015/03/31 02:15:56 UTC
[jira] [Commented] (LIBCLOUD-655) Add an API for managing the power
state of DigitalOcean droplets
[ https://issues.apache.org/jira/browse/LIBCLOUD-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387673#comment-14387673 ]
Andrew Starr-Bochicchio commented on LIBCLOUD-655:
--------------------------------------------------
{{ex_shutdown_node()}} and {{ex_power_on_node()}} we added when adding APIv2 support in https://github.com/apache/libcloud/pull/443/
> Add an API for managing the power state of DigitalOcean droplets
> ----------------------------------------------------------------
>
> Key: LIBCLOUD-655
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-655
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Richard Wall
> Labels: digitalocean
>
> The DigitalOceanDriver could provide an interface for shutting down, powering off, and powering on droplets.
> * https://developers.digitalocean.com/v1/droplets/
> It would be useful to wrap those in the DigitalOceanDriver.
> My use case is that after changing the droplet kernel (which I have to do via a separate call to the V2 API) I need to shutdown the droplet gracefully and then power it back on, as part of our cloud acceptance tests.
> See:
> * https://github.com/ClusterHQ/flocker/pull/1043#discussion_r23074028
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)