The change contains a couple of minor improvements along with AWS driver which doesn't require any additional dependencies and actually could provision a good instances in the prepared environment.
It not just adds AWS as a driver, but also adds snapshot API interface (which is implemented now just for AWS but potentially can work with VMX and other drivers too). The idea behind it is to create the pre-filled workspaces for cache or to save the state of the instance if it needs some additional debugging elsewhere. It's not implemented properly and will work only on the node that has the AWS account, later need to be rewritten to work as expected in clustered environment.
Related Issue
fixes: #3
How Has This Been Tested?
Manual over examples. All the features seems working fine:
Allocating/de-allocating
Attaching snapshots and creating new disks
Snapshot full and partial creation with saving volume tags in snapshot
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Description
The change contains a couple of minor improvements along with AWS driver which doesn't require any additional dependencies and actually could provision a good instances in the prepared environment.
It not just adds AWS as a driver, but also adds snapshot API interface (which is implemented now just for AWS but potentially can work with VMX and other drivers too). The idea behind it is to create the pre-filled workspaces for cache or to save the state of the instance if it needs some additional debugging elsewhere. It's not implemented properly and will work only on the node that has the AWS account, later need to be rewritten to work as expected in clustered environment.
Related Issue
fixes: #3
How Has This Been Tested?
Manual over examples. All the features seems working fine:
Types of changes
Checklist: