[
https://issues.apache.org/jira/browse/LIBCLOUD-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700672#comment-13700672
]
ASF subversion and git services commented on LIBCLOUD-357:
----------------------------------------------------------
Commit a8e473d2aac6e06b027afc6cb861aae0e8cf3685 in branch refs/heads/0.13.x
from [~bobt]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=a8e473d ]
LIBCLOUD-357: Modified ElasticHosts to store drive UUID in 'extra' field.
Signed-off-by: Tomaz Muraus <[email protected]>
> ElasticHosts: Proposal to store drive UUID of boot device in 'extra' field
> ---------------------------------------------------------------------------
>
> Key: LIBCLOUD-357
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-357
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Bob Thompson
> Priority: Trivial
> Attachments: LIBCLOUD-357.patch
>
>
> When an ElasticHosts node is launched, a drive is created and imaged. The
> drive's UUID can be stored to perform operations at a later time (e.g.,
> ex_destroy_drive()). Currently, the drive's UUID is not stored. This would
> save the developer from having to query the API server for the drive UUID.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
