Post by elyes on Jan 23, 2020 15:28:00 GMT
Hi,
I'm trying to modelize Ethernet switches with Redfish data model within a rack manager providing a Redfish interface.
These Ethernet switches are only used for out-of-band management and for compute nodes diskless boot, but they're not used to interconnect compute nodes.
It's not clear for me what kind of Redfish representation could be used.
Is it correct and consistent to use the Fabric object like this:
If yes, what "Protocol" can be used for "FabricType" and "SwitchType" properties?
Or is it more suitable to use a Redfish OEM extension to represent these Ethernet switches, like this for instance:
I've noticed that intel RSD is doing that in its Redfish specification:
www.intel.com/content/dam/www/public/us/en/documents/guides/podm-api-spec-v2-4-guide.pdf
Please don't hesitate to share you thoughts, any help is welcome.
Thanks
Elyes
I'm trying to modelize Ethernet switches with Redfish data model within a rack manager providing a Redfish interface.
These Ethernet switches are only used for out-of-band management and for compute nodes diskless boot, but they're not used to interconnect compute nodes.
It's not clear for me what kind of Redfish representation could be used.
Is it correct and consistent to use the Fabric object like this:
/redfish/v1/Fabrics/EthernetFabric/Switches/<id>If yes, what "Protocol" can be used for "FabricType" and "SwitchType" properties?
Or is it more suitable to use a Redfish OEM extension to represent these Ethernet switches, like this for instance:
/redfish/v1/OEMEthernetSwitches/<id>I've noticed that intel RSD is doing that in its Redfish specification:
www.intel.com/content/dam/www/public/us/en/documents/guides/podm-api-spec-v2-4-guide.pdf
Please don't hesitate to share you thoughts, any help is welcome.
Thanks
Elyes