Post by garyliu on Nov 27, 2019 14:00:52 GMT
Redfish spec 1.8 defined MultipartHttpsPushUri to push image and send parameters/oemparameters to perform update firmware/software.
We implement an oem action to support MultipartHttpsPushUri. However, the schema of ActionInfo is hard to provide parameters info to user.
the parameters of actioninfo look like as below:
"Parameters": [
{
"AllowableValues": [
"ForceRestart",
"ForceOff",
"On",
"GracefulShutdown"
],
"DataType": "String",
"Name": "ResetType",
"Required": true
}
]
As the description of MultipartHttpsPushUri request body in spec 1.8, there are one or more parameters in name "UpdateParameters" and other parameter(s) in name="OemXXXX" value or file.
In the simple case, if the oem action received name="OemParameters" json file to set the parameter, it at least need one more column to indicate the parameter belong to witch part(UpdateParameters/Oemparameters).
We implement an oem action to support MultipartHttpsPushUri. However, the schema of ActionInfo is hard to provide parameters info to user.
the parameters of actioninfo look like as below:
"Parameters": [
{
"AllowableValues": [
"ForceRestart",
"ForceOff",
"On",
"GracefulShutdown"
],
"DataType": "String",
"Name": "ResetType",
"Required": true
}
]
As the description of MultipartHttpsPushUri request body in spec 1.8, there are one or more parameters in name "UpdateParameters" and other parameter(s) in name="OemXXXX" value or file.
In the simple case, if the oem action received name="OemParameters" json file to set the parameter, it at least need one more column to indicate the parameter belong to witch part(UpdateParameters/Oemparameters).
