os and release should not be on the node edit page
Bug #1379187 reported by
Blake Rouse
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
All items on the node edit page are static, once they are set there is no reason to really change those values. Except for the os and release which can get changed before each deployment. The selection of the os and release should really be on node page, before clicking start.
| Changed in maas: | |
| milestone: | none → 1.6.1 |
| milestone: | 1.6.1 → 1.7.0 |
Revision history for this message
| Graham Binns (gmb) wrote | #1 |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #2 |
| Changed in maas: | |
| milestone: | 1.7.0 → next |
| tags: | added: ux |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| milestone: | next → 1.8.0 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm inclined to say that we should push this off until the next release; it would be lovely for the workflow to be along the lines of:
1. Click "Start node"
2. Be asked for OS / Release preferences
3. Confirm
4. Node starts
But I don't think we've got time to implement that well in this cycle given that we're also in bugfix mode.