|
Post by JenHuang on Oct 18, 2022 10:24:22 GMT
Hi, The redfish schema has defined the multipart push which allow user to do component update. My problem is, there is no property which is possible to indicate medium/interface(PCIe/I2C) from pldm componenet of view.
The redfish property doesn't well intergrate the concept of pldm for EID and medium information. User should be able to select the interface they'd like to update via PLDM fwupdate and this is not able to describe according the current redfish schema.
My assumption is, it might possible to implment with RelatedItem in SoftwareInventory redfish schema. The RelatedItem will be the EndpointGroup for those possible device endpoint but still missing the capability for select specific property for firmware update.
Anlternative way is add more property to describe as following example.
"UpdateDeviceInfo":{
"EndpointID": "PLDM device eid",
"TransportMediumOfDevice" :[
"PCIe",
"I2C"
],
"UsedTransportMedium": "PCIe"
}
But we need to consider which redfish schema is the one good to contains the information about EID&medium and select medium for pldm fwupdate. (Maybe EndpointGroup)
|
|
|
Post by mraineri on Oct 18, 2022 16:18:12 GMT
That aspect is entirely up to the service to control. The client is going to be unaware of those implementation details; from the client's perspective, they have no idea PLDM is going on underneath the covers. In the context of firmware update, the client's expectation is they will provide an image to the service, and possibly specific which device to apply it to, and it's up to the service to select the right path, protocol, and other details to update the device in question.
|
|
|
Post by JenHuang on Oct 18, 2022 18:06:07 GMT
I like your answer, and agree your point of view.
|
|