juju does not allow a persistent storage block for the controller disk
Bug #1631138 reported by
Richard Harding
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Unassigned | ||
Bug Description
Running a Juju controller at scale requires a large chunk of disk. The charms, resources, and potentially lxd images in the near future, grow over time and eat up disk space over time.
To handle this, a large production controller needs the ability to stick the mongo storage or the entire machine onto a persistent storage block assigned from swift or ceph. This needs to be part of the bootstrap UX and should be migratable if a controller grows over time from a non-persistent store and the user wants to move to a persistent store.
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| milestone: | 2.1-rc2 → none |
Revision history for this message
| Sandor Zeestraten (szeestraten) wrote | #2 |
Revision history for this message
| Sandor Zeestraten (szeestraten) wrote | #3 |
Revision history for this message
| Tom Haddon (mthaddon) wrote | #4 |
Revision history for this message
| Ian Booth (wallyworld) wrote | #5 |
To post a comment you must log in.
Persistent storage is on the roadmap this cycle.
Removing 2.1 milestone as we will not be addressing this issue in 2.1.