provider/ec2: don't artificially limit EBS volumes to xvdf-xvdp

Bug #1517474 reported by Andrew Wilkins on 2015-11-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Unassigned
juju-core
High
Unassigned

Bug Description

The EBS volume provider currently limits each machine to a maximum of 11 volume attachments, because it follows the AWS recommendation of naming block devices in the range xvdf-xvdp. It is permissible to use xvdf-xvdz, and it's not clear why those names are not recommended for use.

We should not artificially limit them, and just let the AWS APIs complain if there's an issue. We'll only use those names if a large number of volumes is requested anyway.

Changed in juju-core:
milestone: 1.25.2 → 1.25.3
Changed in juju-core:
milestone: 1.25.3 → 1.25.4
Changed in juju-core:
milestone: 1.25.4 → 1.25.5
Changed in juju-core:
milestone: 1.25.5 → 1.25.6
Curtis Hovey (sinzui) on 2016-07-14
Changed in juju-core:
milestone: 1.25.6 → 1.25.7
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0.0
Changed in juju-core:
status: Triaged → Won't Fix
milestone: 1.25.7 → none
Changed in juju:
milestone: 2.0.0 → 2.0.1
Curtis Hovey (sinzui) on 2016-10-28
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers