|
Post by asmithakr on Feb 3, 2021 10:33:46 GMT
Hi All, There exists a scenario where an attribute for the Host network interface(ip addr) can be set by two different Redfish APIs - one is through the bios settings and the other way is through ethernetInterface like the following: 1. -X PATCH https://${bmc}/redfish/v1/Systems/system/Bios/Settings -d '{"Attributes":{"<Host ip addr attribute in bios table>":"<ip>"}}' 2. -X PATCH -D patch.txt https://${BMC_IP}/redfish/v1/Systems/hypervisor/EthernetInterfaces/eth0 -d '{"IPv4StaticAddresses":[{"Address": "<ip addr>","SubnetMask": "<subnet mask>","Gateway":"<gateway>"}]}'
Is it permissible to set a common attribute through two different redfish schemas? If this is considered a violation to the spec - what do you recommend as an alternative here?
|
|
|
Post by mraineri on Feb 3, 2021 14:49:23 GMT
Generally speaking, things you would find in the BIOS F2 menu get translated to the BIOS resource. The BIOS resource is going to be vendor-specific, meaning a set of attributes you find on one service will likely not be available on another service. We encourage folks to submit requests for common things people set in the F2 menu to the forum so we can make standard properties as needed.
In the case you've highlighted, you've found such a property. It's not a violation of the spec to expose two places to manage a setting like this. Many products have requirements to expose all of their F2 settings as-is via the BIOS resource, and specific clients prefer to manage things using the BIOS resource as if they're sitting at the F2 menu. However, from a general Redfish client perspective, it's encouraged to use the standard resources and properties since the BIOS resource is not interoperable.
|
|