re-commissioning just to reset partition scheme is overkill
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Currently, with 1.9 RC2, I can set custom storage configs or I can use the defaults of either LVM or Flat (set as global defaults).
MAAS should provide a means on a per node basis to reset the storage config to the systemwide default WITHOUT having to re-commission.
Of course, the current behaviour should be preserved so that re-commissioning will also accomplish this, but since changing the storage config on a node is done before the node is ever turned on, we are just changing bits in a database, requiring a recommissioning just to change something that doesn't even exist on disk yet is simply overkill and a waste of time and resources.
Consider the behaviour of the installer itself when installing from ISO.
You can create a schema, then delete it and re-create it and delete it and recreate it and delete it and reset to the defaults, all without ever having to reboot into the installer just to reset. MAAS should behave similarly.
E.g. I should be able to do the following:
Access Node page in the web UI
Change the storage config
Decide I don't like that
Click "Reset storage config to default setting"
Storage is reset like magic
Deploy node.
| Blake Rouse (blake-rouse) wrote | #1 |
| Changed in maas: | |
| status: | New → Invalid |
There is the "Retain storage configuration" when you start commissioning that allows you to prevent this behaviour. This will also stop inventory of any new disks.
The reason it gets reset is because we have no way to coordinate the storage items into your defined model as the storage information changes. That is why the option is available when you start commissioning.