Newbie question on Redfish URI resource names
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hello all,
New to OpenBMC, and am not clear on one thing as pertaining to the Redfish schema and URI resource names:
The DMTF Redfish schema URIs are defined as:
/redfish/v1/Chassis/{ChassisId}/
/redfish/v1/Managers/{ManagerId}
/redfish/v1/Systems/{ComputerSystemId}
Vendors can use their own names for {ChassisId}, {ManagerId}, and {ComputerSystemId} as long as they conform to the syntax rules.
Question: Does OpenBMC specify names for these resources as part of the OpenBMC spec? Or does OpenBMC just refer to the existing DMTF Redfish schemas?
I ask because I have seen reference to the following names in examples for Managers and Systems on the OpenBMC website:
/redfish/v1/Chassis/{ChassisId}/
/redfish/v1/Managers/bmc/
/redfish/v1/Systems/system/
In summary, does OpenBMC specify these resource names as part of their spec, or does it refer to existing DMTF Redfish schema specs?
Thank you!
Jeff Friedman
Sr. Field Systems Engineer | ZT Systems
M: 206.819.2824
[ZT Systems]<http://www.ztsystems.com/>
This email and any files transmitted with it are privileged/confidential and intended solely for the use of the individual to whom they are addressed. If you have received this email in error, you are not authorized to distribute it in whole or in part. This communication does not constitute a contract offer, amendment, or acceptance of a contract offer, unless explicitly stated.
Quoted 24 lines · Jeff Friedman
Hello all, New to OpenBMC, and am not clear on one thing as pertaining to the Redfish schema and URI resource names: The DMTF Redfish schema URIs are defined as: /redfish/v1/Chassis/{ChassisId}/ ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEndHello all,
New to OpenBMC, and am not clear on one thing as pertaining to the Redfish schema and URI resource names:
The DMTF Redfish schema URIs are defined as:
/redfish/v1/Chassis/{ChassisId}/
/redfish/v1/Managers/{ManagerId}
/redfish/v1/Systems/{ComputerSystemId}
Vendors can use their own names for {ChassisId}, {ManagerId}, and {ComputerSystemId} as long as they conform to the syntax rules.
Question: Does OpenBMC specify names for these resources as part of the OpenBMC spec? Or does OpenBMC just refer to the existing DMTF Redfish schemas?
I ask because I have seen reference to the following names in examples for Managers and Systems on the OpenBMC website:
Quoted 8 lines
/redfish/v1/Chassis/{ChassisId}/
/redfish/v1/Managers/*/bmc/*/
/redfish/v1/Systems/*/system/*/
In summary, does OpenBMC specify these resource names as part of their spec, or does it refer to existing DMTF Redfish schema specs?
Can you link to the Redfish spec schemas?
As far as I know, the OpenBMC project does not have a separate spec for resource names (outside of the BMCWeb reference implementation).
BMCWeb: https://github.com/openbmc/bmcweb
Why do you ask? OpenBMC members have expressed some interest in having the BMC control multiple hosts. For example: system0, system1. See
https://lore.kernel.org/openbmc/CACWQX82d9NqHatq4of=LrQoP6hfLvbMuZs948ydrThj1J1uhCg@mail.gmail.com/
Joseph
Quoted 11 lines
Thank you!
*Jeff Friedman*
Sr. Field Systems Engineer | ZT SystemsM: 206.819.2824
ZT Systems <http://www.ztsystems.com/>
This email and any files transmitted with it are privileged/confidential and intended solely for the use of the individual to whom they are addressed. If you have received this email in error, you are not authorized to distribute it in whole or in part. This communication does not constitute a contract offer, amendment, or acceptance of a contract offer, unless explicitly stated.
Quoted 21 lines · Jeff Friedman
Hello all,
New to OpenBMC, and am not clear on one thing as pertaining to the Redfish schema and URI resource names:
The DMTF Redfish schema URIs are defined as:
/redfish/v1/Chassis/{ChassisId}/
/redfish/v1/Managers/{ManagerId}
/redfish/v1/Systems/{ComputerSystemId}
Quoted 5 lines
Vendors can use their own names for {ChassisId}, {ManagerId}, and {ComputerSystemId} as long as they conform to the syntax rules.
Question: Does OpenBMC specify names for these resources as part of the OpenBMC spec? Or does OpenBMC just refer to the existing DMTF Redfish schemas?
OpenBMC does not specify nor guarantee these names, which is in line with the Redfish specification. The spec essentially states that odata.id is for walking the Redfish tree, and nothing else. If you want to get a single object, you need to rely on $filter (either locally or on the client side).
Quoted 7 lines
I ask because I have seen reference to the following names in examples for Managers and Systems on the OpenBMC website:
Quoted 5 lines
/redfish/v1/Chassis/{ChassisId}/
/redfish/v1/Managers/bmc/
/redfish/v1/Systems/system/
The hardcoded ids of "bmc" and "system" are things we're actively trying to fix, because we need to support systems with more than one management controller, and more than one ComputerSystem resource. Most of the discussion has happened in code reviews (on gerrit) and in discord in the #bmcweb-and-redfish channel. You might check those out for more up to the minute information on what the plan is here, but the TL; DR is that those IDs need to change, as the redfish spec allows us to do.
Quoted 4 lines
In summary, does OpenBMC specify these resource names as part of their spec, or does it refer to existing DMTF Redfish schema specs?
Kinda the later, the the Redfish specs say that this is an opaque field, and the client should not be using it for resource identification if you want to be compatible with more than just one system, which ideally every client should at least try to do (please don't hardcode openbmc-specific assumptions in your redfish client).
-Ed
Quoted 17 lines
Thank you!
Jeff Friedman
Sr. Field Systems Engineer | ZT SystemsM: 206.819.2824
This email and any files transmitted with it are privileged/confidential and intended solely for the use of the individual to whom they are addressed. If you have received this email in error, you are not authorized to distribute it in whole or in part. This communication does not constitute a contract offer, amendment, or acceptance of a contract offer, unless explicitly stated.
This answers my question, thank you. I will check out the #bmcweb-and-redfish channel as well.
Thanks again!
Jeff Friedman
This email and any files transmitted with it are privileged/confidential and intended solely for the use of the individual to whom they are addressed. If you have received this email in error, you are not authorized to distribute it in whole or in part. This communication does not constitute a contract offer, amendment, or acceptance of a contract offer, unless explicitly stated.
-----Original Message-----
From: Ed Tanous <[email protected]>
Sent: Wednesday, June 8, 2022 12:18 PM
To: Jeff Friedman <[email protected]>
Cc: [email protected]
Subject: [EXTERNAL] Re: FW: Newbie question on Redfish URI resource names
Quoted 21 lines · Jeff Friedman
Hello all,
New to OpenBMC, and am not clear on one thing as pertaining to the Redfish schema and URI resource names:
The DMTF Redfish schema URIs are defined as:
/redfish/v1/Chassis/{ChassisId}/
/redfish/v1/Managers/{ManagerId}
/redfish/v1/Systems/{ComputerSystemId}
Quoted 5 lines
Vendors can use their own names for {ChassisId}, {ManagerId}, and {ComputerSystemId} as long as they conform to the syntax rules.
Question: Does OpenBMC specify names for these resources as part of the OpenBMC spec? Or does OpenBMC just refer to the existing DMTF Redfish schemas?
OpenBMC does not specify nor guarantee these names, which is in line with the Redfish specification. The spec essentially states that odata.id is for walking the Redfish tree, and nothing else. If you want to get a single object, you need to rely on $filter (either locally or on the client side).
Quoted 7 lines
I ask because I have seen reference to the following names in examples for Managers and Systems on the OpenBMC website:
Quoted 5 lines
/redfish/v1/Chassis/{ChassisId}/
/redfish/v1/Managers/bmc/
/redfish/v1/Systems/system/
The hardcoded ids of "bmc" and "system" are things we're actively trying to fix, because we need to support systems with more than one management controller, and more than one ComputerSystem resource.
Most of the discussion has happened in code reviews (on gerrit) and in discord in the #bmcweb-and-redfish channel. You might check those out for more up to the minute information on what the plan is here, but the TL; DR is that those IDs need to change, as the redfish spec allows us to do.
Quoted 4 lines
In summary, does OpenBMC specify these resource names as part of their spec, or does it refer to existing DMTF Redfish schema specs?
Kinda the later, the the Redfish specs say that this is an opaque field, and the client should not be using it for resource identification if you want to be compatible with more than just one system, which ideally every client should at least try to do (please don't hardcode openbmc-specific assumptions in your redfish client).
-Ed
Quoted 17 lines
Thank you!
Jeff Friedman
Sr. Field Systems Engineer | ZT SystemsM: 206.819.2824
This email and any files transmitted with it are privileged/confidential and intended solely for the use of the individual to whom they are addressed. If you have received this email in error, you are not authorized to distribute it in whole or in part. This communication does not constitute a contract offer, amendment, or acceptance of a contract offer, unless explicitly stated.