GitHub user wirkijowski opened a pull request:
https://github.com/apache/libcloud/pull/430
Libcloud 649 basic volume management linode
Unit tests included
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wirkijowski/libcloud
LIBCLOUD-649_basic_volume_management_linode
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/430.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 #430
----
commit 07c582d887ee9c3c63bddbdb39156d4a6db162f2
Author: Wojciech Wirkijowski <[email protected]>
Date: 2014-11-09T12:46:54Z
Experimental create and list volumes for linode
It's to be rewritten to comply with libcloud design
commit e05907c9cde5a3e3d45db5288f05603df20fca22
Author: Wojciech Wirkijowski <[email protected]>
Date: 2014-11-13T22:34:25Z
Tests for ex_{create_volume,list_volumes}
commit 96409b4eababe45682168bd044e2effa2d3ac48f
Author: Wojciech Wirkijowski <[email protected]>
Date: 2015-01-05T14:21:09Z
Add new methods for the Linode driver
* ex_create_volume() for adding volumes for the Linode
* ex_list_volumes() for listing volumes for the Linode
* LINODE_DISK_FILESYSTEMS
* updated _linode_disk_list.json
Includes tests for new methods
commit d805e3ab9431694f6ac704f6ee6ca6162ce6e8b4
Author: Wojciech Wirkijowski <[email protected]>
Date: 2015-01-07T15:46:26Z
Add destroy_volume() method for Linode driver
* destroy_volume() method for Linode
* basic test for destroy_volume()
commit 257ff82f3f84b30c32ca7f5cb8f79a168458d786
Author: Wojciech Wirkijowski <[email protected]>
Date: 2015-01-07T15:49:33Z
Fix coding conventions
commit 74293600420b3131527228e11c1b32588118e4b4
Author: Wojciech Wirkijowski <[email protected]>
Date: 2015-01-09T22:05:40Z
Minor refactoring of destroy_volume() method for Linode
* refactoring of destroy_volume()
* minor fixes for coding style
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
