29601366ee
Why I did it The Mellanox platform is required to support the fwutil auto-update feature defined here This is to allow switches, when performing SONiC upgrades to choose whether to perform firmware upgrades that may interrupt the data plane through a cold boot. How I did it Two methods were added to the component implementations for mellanox. In the base Component class we add a default function that chooses to skip the installation of any firmware unless the cold boot option is provided. This is because the Mellanox platform, by default, does not support installing firmware on ONIE, the CPLD, or the BIOS "on-the-fly". In the ComponentSSD class we add a function that behaves similarly but uses the Mellanox specific SSD firmware upgrade tool to check if the current SSD supports being upgraded on the fly in order to decide whether to skip or perform the installation. How to verify it Unit tests are included with this PR. These test will run on build of target sonic-mellanox.bin You may also perform fwutil auto-update ... commands after Azure/sonic-utilities#1242 is merged in. |
||
|---|---|---|
| .. | ||
| barefoot | ||
| broadcom | ||
| cavium | ||
| centec | ||
| centec-arm64 | ||
| generic | ||
| innovium | ||
| marvell | ||
| marvell-arm64 | ||
| marvell-armhf | ||
| mellanox | ||
| nephos | ||
| p4 | ||
| pddf | ||
| template | ||
| vs | ||