slotain
Minnow
It's bigger than a regular hat. It's funny.
Posts: 19 
|
Post by slotain on Jan 25, 2022 15:38:44 GMT
If we were to release our new Redfish service before the PCIe Switch schema is released, should we just hang our data off the `Oem` attribute of the `Chassis.v1_17_0.Chassis`?
My team is very interested in the PCIe Switch schema that's in progress. We found a slide presentation:
Are there any additional materials that DMTF can share in addition to this slide presentation, linked above? Is there a video of this material in the slides?
I noticed also that there is some code in the Redfish Emulator, and that maybe we can borrow some attributes from this schema.
Redfish-Interface-Emulator/api_emulator/redfish/templates/pcie_switch.py === ...
PCIeSwitch_TEMPLATE={
"@odata.type": "#PCIeSwitch.v1_0_0.PCIeSwitch", ...
|
|
|
|
Post by j2hilland on Jan 25, 2022 19:14:45 GMT
That presentation is very old, but the Fabrics model hasn't changed significantly since it was published. There are artifacts under development, and there is the CXL work in progress release to go look at (but it is really CXL specific) as well as Gen-Z presentations.
Support in the Fabric model has been there for PCIe since the first release of the Fabric model. And Switch of SwitchType=PCIe has been there since day one. There isn't a PCIe specific section in the switch, but that's because we haven't found a property that is needed other than the base properties. If you find some properties are needed, let us know. The last property added for PCIe was in 2020 and I think that was a link to the PCIe device that can be used to communicate with the switch.
Everything you need should be published in Fabric, Switch, Zone, Port, etc. and you should be able to trace from a PCIe device, through a switch, etc. Everything we know about for PCIe is released and there should be no need to use an OEM extension. If you find something you missed, please let us know.
|
|
|
|
Post by jleung on Jan 26, 2022 15:31:02 GMT
The PCIeSwitch is included as a dynamic resource in the Redfish Interface Emulator is an older version of the schema. The resource was included in order to demonstrate the python coding for a dynamic resource which had subordinate resources. Namely, the resource's subordinate resources should not become available until the resource is created (and not before). This coding construct provides the correct 404 behavior for subordinate resources.
Also, for coded Emulator dynamic resources for Fabric, Switch, Zone, etc - see the Swordfish API Emulator additions - github.com/SNIA/Swordfish-API-Emulator.
|
|
slotain
Minnow
It's bigger than a regular hat. It's funny.
Posts: 19
|
Post by slotain on Jan 27, 2022 0:37:17 GMT
Cheers to you both. This was a point of clarification for me, but I hadn't realized that external rack mounted PCIe switches were covered by the schema.
I reviewed your answers with the team, and from what we understand a rack mounted PCIe switch and an embedded PCIe switch have similar enough attributes that we could relate our new hardware device's embedded HW switch attributes in the schemas you provided.
|
|
|
|
Post by jautor on Jan 27, 2022 15:43:25 GMT
The only significant difference between a rack-mounted PCIe switch and an embedded one from the Redfish model perspective may be the presence of the Chassis resource to describe the rack-mounted device. We're recommending that all free-standing "products" include the Chassis resource so that clients have a consistent method to discover rack topology ("Location", "ContainedBy") and general production information ("SerialNumber", "Model").
Jeff
|
|
