Firmware: Extended version

gmills
Minnow

Posts: 25

Firmware: Extended version Mar 25, 2020 21:04:01 GMT

Quote

Post by gmills on Mar 25, 2020 21:04:01 GMT

In OpenBMC, we have the concept of extended version, which contains additional information about the firmware image, it could list versions of individual packages for example.

Don't see an obvious field to add that information to the software inventory - redfish.dmtf.org/schemas/v1/SoftwareInventory.v1_2_3.json

Would Redfish be interested in adding a ‘subsoftwareinventory’ field like the processors' subprocessors - redfish.dmtf.org/schemas/v1/ProcessorCollection.json ?

Or a different field to model this information?

Thanks!
Gunnar

github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Software/ExtendedVersion.interface.yaml

Example value:
"ExtendedVersion": "buildroot-2019.05.3-17-g522600d,skiboot-v6.5-242-ge19dddc5-p37cfc70,hostboot-820a099-pe030f7b,occ-3ab2921,linux-5.4.25-openpower1-p2339fe8,petitboot-v1.12,machine-xml-0f9b366-p7fb7a8d,hostboot-binaries-hw013120a.opmst,capp-ucode-p9-dd2-v4,sbe-0a77603,hcode-hw031620a.opmst"

gmills Minnow Posts: 25	Firmware: Extended version May 1, 2020 16:55:59 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by gmills on May 1, 2020 16:55:59 GMT Is this something Redfish would be interested in adding?

mraineri
Administrator

Posts: 1,049

Firmware: Extended version May 2, 2020 23:51:23 GMT

Quote

Post by mraineri on May 2, 2020 23:51:23 GMT

I think it could be useful. Technically you could encode that all in the "Version" property along with the main version info (since it's just a string property), but that seems very ugly and doesn't provide much benefit to the client. Having a new property in SoftwareInventory (something like "ExtendedInfo" or "ExtendedVersion") would make sense to me since it can be used as a dumping ground of miscellaneous packages, but as I'm typing this, if clients really aren't expected to do anything with this data, maybe just leaving it as an OEM property in the SoftwareInventory resource is good enough. Still, I think it's worth thinking more about.

Another option could be to create a SoftwareInventory instance for each package, but I don't know if that will be particularly helpful to clients if you cannot update individual packages.

gmills Minnow Posts: 25	Firmware: Extended version May 7, 2020 19:43:50 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by gmills on May 7, 2020 19:43:50 GMT Moving internally for additional discussion. Thanks!

Post by gmills on Mar 25, 2020 21:04:01 GMT

Post by gmills on May 1, 2020 16:55:59 GMT

Post by mraineri on May 2, 2020 23:51:23 GMT

Post by gmills on May 7, 2020 19:43:50 GMT