|
Post by ueliyahu on Feb 20, 2023 15:21:40 GMT
Hi all
In order to initialized UEFI bios attribute , one of the requirements from the UEFI team was to support PUT request to /redfish/v1/Registries/BiosAttributeRegistry/BiosAttributeRegistry.
Does PUT is valid request in this case ? I did not find an answer for that in DMFT documentation
Get request for /redfish/v1/Registries/BiosAttributeRegistry/BiosAttributeRegistry retrieve the following information
"@odata.id": "/redfish/v1/Registries/BiosAttributeRegistry/BiosAttributeRegistry",
"@odata.type": "#AttributeRegistry.v1_3_2.AttributeRegistry",
"Description": "This registry represent DPU's BIOS Attribute instances",
"Id": "BiosAttributeRegistry",
"Language": "en",
"Name": "DPU Bios Attribute Registry", "RegistryEntries": {
"Attributes": []
},
"RegistryVersion": "1.0.0"
} according to redfish.dmtf.org/schemas/v1/AttributeRegistry.v1_3_2.json it seems that PUT request can be supported but according to redfish.dmtf.org/schemas/v1/AttributeRegistry.json only GET request can be supported. Thanks !
|
|
|
Post by mraineri on Feb 20, 2023 15:55:18 GMT
As an internal data provider for the Redfish service, you are certainly free to supply the data in whatever method makes the most sense to you. Many read-only portions of the data model will need to be supplied by some internal firmware components, like filling in CPU and memory information populated by UEFI. The scope of what's published in the Redfish Specification and Redfish Schema Bundle is focused on the end-user experience. An end-user of Redfish will never be able to perform these operations, hence why the capabilities in the schema contain "false".
|
|
|
Post by Abner Chang on Feb 21, 2023 1:28:07 GMT
ueliyahu, We don't allow users to write to BIOS AttributeRegistry because AttributeRegistry is used to represent the BIOS Attribute characteristics and the attributes hierarchy from UI viewpoint. If you were saying BIOS->BMC when provisioning the BIOS AttributeRegistry through PUT, the Host Interface boot credential can give different privileges to BIOS as it is a provider. However, this would be the agreement between BIOS and BMC, not the Redfish spec or defined in the schema.
|
|