storage minimum size and default size are conflated
Bug #1614072 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
Juju native storage only allows you to specify a minimum size, which is also used as the default size. The minimum size will generally need to be as small as possible for test installs, which makes it a horrible default for real installs.
I'd like to see a separate default size attribute.
I'd also like a charm to declare 'no default size' and require the operator to explicitly state the desired size at add-storage time. If operators don't have a second chance to get it right, they need to be explicit. For example, failing to specify a large enough partition will cause data migration from local storage to the new partition to fail, breaking the unit and possibly destroying data.
tags: | added: canonical-is |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.1.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
Changed in juju: | |
status: | New → Triaged |
To post a comment you must log in.
@Stuart,
Unfortunately we will not be able to address this issue for 2.1. I will remove it from the milestone.
Just to paraphrase, this is what you would like to see https:/ /pastebin. canonical. com/179166/ Correct?