openstack
/
diskimage-builder
Code Issues Proposed changes
diskimage-builder/elements/ilo
History
Robert Collins 027dcc2dbe Add support for flashing ILO BMC's from ramdisks 
This is more than a bit hard to test, requiring as it does an actual
iLO BMC, so sadly I have no tests :(.

HP Hardware really wants to be running latest firmware, and its
commonly agreed that one place where it can be sanely applied is in
the deploy environment, so this is my long threatened implementation
of that.

Change-Id: I3117a250d0d0eb8ee33eb4b15c837485a5cbf476
 		2014-08-28 17:07:03 +01:00
..
extra-data.d Add support for flashing ILO BMC's from ramdisks 2014-08-28 17:07:03 +01:00
init.d Add support for flashing ILO BMC's from ramdisks 2014-08-28 17:07:03 +01:00
ramdisk-install.d Add support for flashing ILO BMC's from ramdisks 2014-08-28 17:07:03 +01:00
README.md Add support for flashing ILO BMC's from ramdisks 2014-08-28 17:07:03 +01:00

README.md

Ramdisk support for applying HP iLO firmware.

The firmware files are copied in via an extra-data hook: the variable DIB_ILO_FIRMWARE_PATH specifies a directory, and every file in that directory will be unpacked into a same-named directory in the ramdisk (using --unpack=...). If the path is not specified, a diagnostic is output but no error is triggered.

During ramdisk init every found firmware installer will be executed using --silent --log=log The log is displayed after the firmware has executed.

If the firmware exits with status 0 (ok), status 2 (same or older version) or 4 (ilo not detected) a diagnostic message is logged and init proceeds.

Any other status code is treated as an error.