Post by ljfranklin on Feb 4, 2023 14:09:32 GMT
Hi all!
I'm building some deployment tooling that uses the BMC to force a machine to PXE boot to update the OS image. But the tooling needs a way to store a user-defined version number in Redfish to query the current deployment version of a given System. I'm struggling to see which API resource to use for this. Similar to this thread, but this metadata wouldn't need to store secrets or be accessed from the host OS.
The `SoftwareInventory` resource looks close but that resource seems to be controlled by the BMC manufacturer, it doesn't seem like I could POST a new SoftwareInventory instance for use by my tooling. The `AssetTag` property would work but that's already used for other purposes. I could create a dummy BMC user via the `AccountService` and repeatedly update that user's username to contain the version number, but that's obviously a hack. Any suggestions?
I'm building some deployment tooling that uses the BMC to force a machine to PXE boot to update the OS image. But the tooling needs a way to store a user-defined version number in Redfish to query the current deployment version of a given System. I'm struggling to see which API resource to use for this. Similar to this thread, but this metadata wouldn't need to store secrets or be accessed from the host OS.
The `SoftwareInventory` resource looks close but that resource seems to be controlled by the BMC manufacturer, it doesn't seem like I could POST a new SoftwareInventory instance for use by my tooling. The `AssetTag` property would work but that's already used for other purposes. I could create a dummy BMC user via the `AccountService` and repeatedly update that user's username to contain the version number, but that's obviously a hack. Any suggestions?