|
Post by msilva on Jun 5, 2020 16:37:08 GMT
I'm working in a project where we implement the RedFish schema manually, my main question is how valid it would be to use this /redfish/v1/UpdateService/SoftwareInventory for listing the softwares installed in the OS, the description of this schema says:
My question is if SoftwareInventory is valid for this specific purpose (i.e. Listing softwares from the OS instead of pre-OS tools and such). Alternatively i thought about creating a custom OEM schema inside /redfish/v1/Systems/, this would be my fallback strategy.
|
|
|
Post by jautor on Jun 5, 2020 23:53:24 GMT
The SoftwareInventory schema gets used in two instances under the UpdateService. We envisioned the "FirmwareInventory" one to contain those system components (BIOS, BMC firmwware, etc. normally not part of the host OS), while "SoftwareInventory" would contain the OS applications, etc. So yes, that collection would be appropriate, and what was intended. The distinction between the two was intended to be that firmware included those items that were part of the "platform" and had to use platform-specific methods to update, while software was updated or installed using OS-specific tools or methods.
Jeff
|
|
|
Post by msilva on Jun 8, 2020 17:43:56 GMT
The SoftwareInventory schema gets used in two instances under the UpdateService. We envisioned the "FirmwareInventory" one to contain those system components (BIOS, BMC firmwware, etc. normally not part of the host OS), while "SoftwareInventory" would contain the OS applications, etc. So yes, that collection would be appropriate, and what was intended. The distinction between the two was intended to be that firmware included those items that were part of the "platform" and had to use platform-specific methods to update, while software was updated or installed using OS-specific tools or methods. Jeff Excellent, thanks!
|
|