2 different moonshot power types is confusing
Bug #1361426 reported by
dann frazier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I was trying to add some m400 cartridges to MAAS, but it wasn't clear to me which power type I needed. There are 2 power types that seem to meet the description: "Moonshot HP iLO Chassis Manager" and "iLO 4 Moonshot Chassis". Turns out I needed the "Moonshot HP iLO Chassis Manager". Can this distinction be clarified in the UI?
Related branches
lp:~andreserl/maas/maas_hp_moonshot
- Raphaël Badin (community): Approve
- Andres Rodriguez (community): Approve
-
Diff: 21 lines (+2/-2)1 file modifiedsrc/provisioningserver/power_schema.py (+2/-2)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: confusing-ui server-hwe |
Changed in maas: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
I think I understand the correct usage myself - basically "iLO 4 Moonshot Chassis" can be used for chassis that will only include x86 cartridges and will support the "boot-node- to-enlist" mechanism. "Moonshot HP iLO Chassis Manager" supports autoenlistment of all nodes via the chassis manager without needing to boot, and also works for non-x86 Nodes.
I understand that we need to retain "iLO 4 Moonshot Chassis" for upgrades - but it seems like "Moonshot HP iLO Chassis Manager" will work in a superset of the cases that "iLO 4 Moonshot Chassis" provides, and doesn't require as much admin intervention (manual boot-to-enlist). My recommendation would be to clarify these descriptions and deprecate the x86-only mechanism but continue to support it for backwards compatibility.
This rename would have clarified things for me:
iLO 4 Moonshot Chassis -> iLO 4 Moonshot Chassis (x86-only, deprecated)