[
https://issues.apache.org/jira/browse/LIBCLOUD-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719322#comment-13719322
]
ASF subversion and git services commented on LIBCLOUD-365:
----------------------------------------------------------
Commit d56f0c065099b30dc260775aabed30ec3fb57491 in branch refs/heads/0.13.x
from [~joe.miller]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=d56f0c0 ]
Issue LIBCLOUD-365: change ec2 ex_blockdevicemappings to support all possible
key/values
Signed-off-by: Tomaz Muraus <[email protected]>
> EC2 node driver only allows subset of BlockDeviceMapping parameters to be
> passed in
> -----------------------------------------------------------------------------------
>
> Key: LIBCLOUD-365
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-365
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: joe miller
> Priority: Minor
> Labels: patch
> Attachments: libcloud-365.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> My previous patch that added support for passing 'ex_blockdevicemappings' to
> the EC2 create_node() method only supported parameters 'DeviceName' and
> 'VirtualName'. This is sufficient for mapping ephemerals into the instance
> but it prevents other options such as specifying a root EBS volume with
> larger sizes, mapping other EBS, or creating EBS from snapshots.
> I have a patch forthcoming that will allow any possible Block Device Mapping
> argument to be submitted so that all current and future settings should Just
> Work.
--
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
