Storage options should be applicable on a per-system or per-batch basis
Bug #1522933 reported by
Jeff Lane
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
There are couple Storage defaults that are currently (in 1.9) universal. Those should be also applicable per node or per selected nodes.
These are:
partition scheme... I may well want to use the default of LVM, but on certain nodes only use Flat.
and
Erasing disk. The Disk erasing thing can take a VERY long time. I do not want to use it by default for that reason, but sometimes I do want to zero a node's disks before re-deploying. I shoudln't have to set the default, then work with one node, then reset the default back to disabling disk erasing.
I should be able to set disk erase per node.
Changed in maas: | |
milestone: | none → next |
importance: | Undecided → Medium |
importance: | Medium → Wishlist |
Changed in maas: | |
status: | New → Triaged |
summary: |
- Storage options should be applicable on a per-system or per-batch - basisaa + Storage options should be applicable on a per-system or per-batch basis |
Changed in maas: | |
milestone: | next → none |
To post a comment you must log in.
We do provide the ability to set the storage layout on a per-node basis over the API. We should expose this functionality in the WebUI as well.