IPMI configuration can be done directly with -e section:key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
We currently set IPMI configuration using a fragment of IPMI config (ipmi.conf in templates) which is sent to the BMC, along the lines of:
./ipmi-cmd -u X -p Y -h Z --commit -n <filename.cfg>
We can actually send the configuration much more directly, using the "-e section:key=value" pattern in freeipmi. So:
./ipmi-
The -e section can be repeated several times on the command line, enabling us to set everything we need in a single transaction. The current IPMI config fragment would thus become:
-e Chassis_
-e Chassis_
-e Chassis_
The configuration subprocess exits with 0 on success, making for easy validation.
tags: | added: server-hwe |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in maas: | |
milestone: | none → 2.1.0 |
Changed in maas: | |
milestone: | 2.1.0 → 2.1.1 |
Changed in maas: | |
milestone: | 2.1.1 → 2.1.2 |
Changed in maas: | |
milestone: | 2.1.2 → 2.1.3 |
The way MAAS uses ipmi has changed since the issue was submitted.