libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-649) Add new methods for LinodeNodeDriver
Date Sat, 21 Feb 2015 23:59:11 GMT

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

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

Github user asfgit closed the pull request at:

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


> Add new methods for LinodeNodeDriver
> ------------------------------------
>
>                 Key: LIBCLOUD-649
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-649
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute
>            Reporter: Wojciech Wirkijowski
>              Labels: features
>
> Add basic volume management methods for Linode: destroy_volume(), ex_create_volume(),
ex_list_volumes().
> The Linode node comes with persistent storage which can be divided to volumes. This pool
of storage can't be disconnected from the particular Linode or connected to other one. So
for every operation on volumes one have to provide specific LinodeID. This is the reason why
ex_ methods have been created. 
> In order to destroy volume one have to provide StorageVolume instance as a parameter
to destroy_volume(). Because this method checks StorageVolume.extra["LINODEID"] for LinodeID
it can be standard libcloud API method. By default ex_list_volumes() returns volume instances
with extra["LINODE"]



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

Mime
View raw message