BMC version check via restful
bradleyb at fuzziesquirrel.com
Sat Nov 4 00:37:50 AEDT 2017
> On Nov 3, 2017, at 4:14 AM, tao-ching Yu <yutaoc1984 at gmail.com> wrote:
> Hi Adriana,
> I noticed the version of BMC is under /xyz/openbmc_project/Software/xxxxxxx
> But I found that this "xxxxxxxx" is not fixed
> ex./xyz/openbmc_project/software/13264da3 or /xyz/openbmc_project/software/aaf838cc
> What does this "string" mean? Is this BMC FW related(version)? Could this string be fixed?
> How does user know the right object path and get the right information of BMC via restful?
> Because this object path is not fixed.
The image identifier is briefly discussed here: https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Software/README.md#image-identifier
As of today, the ID is an implementation detail and there aren’t any requirements on it
at an API level.
Keep in mind that the OpenBMC D-Bus API is first and foremost designed to facilitate
BMC application compatibility, not end user interface standardization. End user
interface standardization would be accomplished with Redfish, IPMI, etc…
This nuance is often lost because we do happen to have a REST server application that exposes
the internal D-Bus API via REST with little translation. But ideally that isn’t
the user-interface for a complete BMC implementation.
Can you think of a scenario where adding restrictions on the ID at the D-Bus API level would
enable additional compatibility between on-BMC applications?
More information about the openbmc