Open leftwo opened 2 years ago
An important constraint and thing for us to consider is how we want to distribute the firmware which probably isn't something we want to store in the ramdisk and instead make something slightly more persistent delivered via updates.
We have an existing rack we would like to upgrade the U.2 disk firmware on (see oxidecomputer/mfg-quality#161 for the meta issue and oxidecomputer/mfg-quality#166 for a concrete example). Noting this here to connect those issues to the control plane work required.
When a new NVMe drive is inserted, sled-agent should work with the upgrade process to properly upgrade (or downgrade) the drive firmware to the required version.