Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding block_device_mapping iops parameter, fixes #157 #165

Merged
merged 2 commits into from
Jun 24, 2015
Merged

Conversation

tyler-ball
Copy link
Contributor

Necessary when specifying volume_type of io1. Fixes #157

\cc @fnichol @metadave @randomcamel

@tyler-ball tyler-ball added this to the 0.10.0 milestone Jun 24, 2015
@tyler-ball tyler-ball self-assigned this Jun 24, 2015
@@ -280,7 +285,8 @@ storage config keys are present.

The keys `ebs_volume_type`, `ebs_virtual_name` and `ebs_snapshot_id` are optional. See
[Amazon EBS Volume Types](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html) to find out more about
volume types. `ebs_volume_type` defaults to `standard` but can also be `gp2` or `io1`.
volume types. `ebs_volume_type` defaults to `standard` but can also be `gp2` or `io1`. If you specify `io1` you must
also specify `ebs_iops`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if a user specifies io1 without specifying ebs_iops?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They get a 'nice' error from AWS that is shown in the bug report (#157)

@randomcamel
Copy link

👍

tyler-ball added a commit that referenced this pull request Jun 24, 2015
Adding block_device_mapping iops parameter, fixes #157
@tyler-ball tyler-ball merged commit 633108f into master Jun 24, 2015
@tyler-ball tyler-ball deleted the tball/iops branch June 24, 2015 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants