[
https://issues.apache.org/jira/browse/JCLOUDS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039339#comment-14039339
]
ASF subversion and git services commented on JCLOUDS-602:
---------------------------------------------------------
Commit 5641f675da6165d45da0df70adc789f9f643ee5a in jclouds's branch
refs/heads/master from [~abayer]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=5641f67 ]
JCLOUDS-602. Added live tests for new EBS volume fields.
While they're implemented in apis/ec2, the tests are in
providers/aws-ec2, generally, to make sure ec2-alike clones won't barf
on them. We're exercising creation of volumes, images and instances
with the new options. I also had to do some sketchy wait-and-loop'ing
in AMIAPILiveTest.testCreateAndListEBSBackedImage() due to what seems
to be a delay on new AMIs showing up in filtered DescribeImages calls,
though they'll show up instantly when you specify the image ID. Go figure.
> Add support for Iops, Encrypted and VolumeType fields for EC2
> BlockDeviceMapping
> --------------------------------------------------------------------------------
>
> Key: JCLOUDS-602
> URL: https://issues.apache.org/jira/browse/JCLOUDS-602
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Fix For: 1.8.0, 1.7.4
>
>
> We don't currently have any support for the Iops, Encrypted or VolumeType
> fields for EC2 EBS BlockDeviceMapping - they're described on
> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-RunInstances.html.
> We should add them, especially since VolumeType is needed to use the new
> General Purpose EBS SSD volumes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
