[
https://issues.apache.org/jira/browse/LIBCLOUD-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318803#comment-14318803
]
ASF GitHub Bot commented on LIBCLOUD-655:
-----------------------------------------
GitHub user Jacob-E opened a pull request:
https://github.com/apache/libcloud/pull/452
[LIBCLOUD-655] OpenStack identity component does not refresh auth tokens...
... automatically
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Jacob-E/libcloud 655_refreshauthtoken
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/452.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #452
----
commit 36aad9a2dcec76185589404f377eb4db038c1379
Author: Jacob-E <[email protected]>
Date: 2015-02-12T18:32:34Z
[LIBCLOUD-655] OpenStack identity component does not refresh auth tokens
automatically
----
> 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)
