ec2: pass root-disk constraint via block device mapping
Bug #1212688 reported by
Sidnei da Silva
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Nate Finch | ||
Bug Description
Follow up from LP:1201503:
For ec2 ebs instances, which we default to using, the root disk size defaults to 8G but you can specify a custom root disk size via block device mapping. refs:
- http://
- http://
Example:
ec2-run-instances --key KEYPAIR --block-
... creates an instance that boots with a created on-demand 100G ebs which gets thrown away when the instance is terminated. We'll need to implement passing the block device mapping in the goamz run instance api call to expose this.
| tags: | added: constraints ec2 |
| Changed in juju-core: | |
| assignee: | Sidnei da Silva (sidnei) → nobody |
| tags: |
added: ec2-provider removed: ec2 |
| Changed in juju-core: | |
| assignee: | nobody → Nate Finch (natefinch) |
| status: | Triaged → Fix Released |
Revision history for this message
| Martin Packman (gz) wrote | #1 |
To post a comment you must log in.
This was fixed in the 1.17.0 development release.