<div dir="ltr">Hello Jeff,<div><br></div><div>I am not an authority, but I will give you a quick answer for chassis ID. For chassis bmcweb checks with the dbus mapper to find all daemon in "/xyz/openbmc_project/inventory" that have either the "xyz.openbmc_project.Inventory.Item.Board", or the "xyz.openbmc_project.Inventory.Item.Chassis" interfaces. There are some extra checks and information, but that is a simplified version of it. </div><div><br></div><div>See the bmcweb code that sets up the handler here <a href="https://github.com/openbmc/bmcweb/blob/5b9e95a17fae7aaf9f8716b65345bb64ade5f403/redfish-core/lib/chassis.hpp#L206">https://github.com/openbmc/bmcweb/blob/5b9e95a17fae7aaf9f8716b65345bb64ade5f403/redfish-core/lib/chassis.hpp#L206</a></div><div><br></div><div><br></div><div>The next question might be "how are these interfaces created", and I believe they come from entity-manager. Entity-manager reads a json file, and creates the corresponding dbus interfaces. I know less about entity-manager. But this looks to be the creation of the interfaces, which depending on the json, could be a chassis. <br><a href="https://github.com/openbmc/entity-manager/blob/e45d8c71bdbae39f14a638137da9dc03474536c1/src/entity_manager.cpp#L603">https://github.com/openbmc/entity-manager/blob/e45d8c71bdbae39f14a638137da9dc03474536c1/src/entity_manager.cpp#L603</a></div><div><br></div><div>Ed, Patrick, and Brad know more about this process. </div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 8, 2022 at 4:27 PM Jeff Friedman <<a href="mailto:jfriedman.seattle@gmail.com">jfriedman.seattle@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="ltr"></div><div dir="ltr"><span style="font-family:Calibri,sans-serif;font-size:11pt">Hello all,</span></div><div dir="ltr"><div><p class="MsoNormal"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">New to OpenBMC, and am not clear on one thing as pertaining to the Redfish schema and URI resource names:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The DMTF Redfish schema URIs are defined as:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">/redfish/v1/Chassis/{ChassisId}/<u></u><u></u></p>
<p class="MsoNormal">/redfish/v1/Managers/{ManagerId}<u></u><u></u></p>
<p class="MsoNormal">/redfish/v1/Systems/{ComputerSystemId}<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Vendors can use their own names for {ChassisId}, {ManagerId}, and {ComputerSystemId} as long as they conform to the syntax rules.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I ask because I have seen reference to the following names in examples for Managers and Systems on the OpenBMC website:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">/redfish/v1/Chassis/{ChassisId}/ <u></u><u></u></p>
<p class="MsoNormal">/redfish/v1/Managers/<b><i>bmc</i></b>/
<u></u><u></u></p>
<p class="MsoNormal">/redfish/v1/Systems/<b><i>system</i></b>/ <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">In summary, does OpenBMC specify these resource names as part of their spec, or does it refer to existing DMTF Redfish schema specs?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thank you!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(223,72,38)">Jeff Friedman</span></b><span style="font-size:9pt;color:rgb(31,73,125)"><br>
</span><span style="font-size:9pt;color:gray">Sr. Field Systems Engineer | ZT Systems</span><span style="font-size:9pt;color:rgb(68,84,106)"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="font-size:9pt;color:rgb(127,127,127)">M: <a href="tel:(206)%20819-2824" value="+12068192824" target="_blank">206.819.2824</a><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-bottom:12pt"><a href="http://www.ztsystems.com/" target="_blank"><span style="font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(74,88,171);text-decoration:none"></span></a></p><div><a href="http://www.ztsystems.com/" target="_blank"><image001.gif></a></div><span style="font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(109,110,113)"><br>
<br>
</span><span style="font-size:7pt;font-family:Arial,sans-serif;color:rgb(127,127,127)">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.</span><span style="font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(109,110,113)"> </span><u></u><u></u><p></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></blockquote></div>