Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Initial storage pools #8
Conversation
wallyworld
added some commits
Jan 27, 2015
axw
reviewed
Jan 27, 2015
| + Encrypted = "encrypted" | ||
| + | ||
| + // The Availability Zone in which to create the volume. | ||
| + AvailabilityZone = "availability-zone" |
axw
reviewed
Jan 27, 2015
| + // supplied options from a user friendly value to the equivalent | ||
| + // provider specific value. | ||
| + // eg for EBS providers, "magnetic" will be translated to "standard". | ||
| + TranslateUserOptions(map[string]interface{}) map[string]interface{} |
axw
Jan 27, 2015
Collaborator
The provider should handle this internally, when given a map. It doesn't need to be surfaced like this.
|
LGTM, can be cleaned up post-demo. |
wallyworld
added some commits
Jan 27, 2015
added a commit
that referenced
this pull request
Jan 27, 2015
wallyworld
merged commit 4c8edc6
into
storage-feature
Jan 27, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
wallyworld commentedJan 27, 2015
Add a 1.23 upgrade step to create storage pools ootb for the ebs provider.
When provisioning an ec2 instance, copy the options from the pool used for the deployment to the block device mapping params.
Note: I wanted to copy availability zone to block device params but it appears this isn't supported by goamz yet. Neither is encryption param.