PATCH – 对更新服务状态进行更新
使用 PATCH 方法对更新服务资源属性和状态进行更新。
请求 URL
PATCH https://<BMC_IPADDR>/redfish/v1/UpdateService
请求正文
字段 | 类型 | 描述 | |
---|---|---|---|
HttpPushUriTargets | 数组 | 项:字符串,项数:0-1 | |
HttpPushUriTargets[N] | 字符串 | 指示将更新映像应用到何处的 URI 数组。此值最初为空白,并且在 XCC 重置后不会保留客户端更新的值。 | |
HttpPushUriTargetsBusy | 布尔 | 指示是否有任何客户端保留了 HttpPushUriTargets 属性。此值最初为 false,并且在 XCC 重置后不保留。 |
响应
响应返回的内容与 GET 操作相同,但更新了属性。
状态代码
HTTP 状态代码 | 错误消息 ID |
---|---|
500 | InternalError |
示例
以下示例是 PATCH 正文
{
"HttpPushUriTargets" : [
"/redfish/v1/UpdateService/FirmwareInventory/BMC-Backup"
]
}
成功运行 PATCH 操作后,更新服务资源查询将返回以下示例 JSON 响应:
{
"MultipartHttpPushUri": "/mfwupdate",
"Id": "UpdateService",
"ServiceEnabled": true,
"HttpPushUri": "/fwupdate",
"HttpPushUriTargets": [
"/redfish/v1/UpdateService/FirmwareInventory/BMC-Backup"
],
"Description": "Lenovo firmware update service.",
"FirmwareInventory": {
"@odata.id": "/redfish/v1/UpdateService/FirmwareInventory"
},
"Status": {
"HealthRollup": "OK",
"Health": "OK",
"State": "Enabled"
},
"Name": "Update Service",
"HttpPushUriTargetsBusy": false,
"Oem": {
"Lenovo": {
"FirmwareServices": {
"@odata.id": "/redfish/v1/UpdateService/Oem/Lenovo/FirmwareServices"
},
"@odata.type": "#LenovoUpdateService.v1_0_0.LenovoUpdateService"
}
},
"@odata.type": "#UpdateService.v1_6_0.UpdateService",
"HttpPushUriOptions": {
"HttpPushUriApplyTime": {
"ApplyTime": "Immediate"
}
},
"MaxImageSizeBytes": 250000000,
"@odata.etag": "\"7dd4c1a358b13e95cc1c93d70426ad56\"",
"Actions": {
"#UpdateService.SimpleUpdate": {
"target": "/redfish/v1/UpdateService/Actions/UpdateService.SimpleUpdate",
"title": "SimpleUpdate",
"TransferProtocol@Redfish.AllowableValues": [
"TFTP",
"SFTP"
],
"Targets@Redfish.AllowableValues": [
"/redfish/v1/UpdateService/FirmwareInventory/BMC-Backup"
],
"@Redfish.ActionInfo": "/redfish/v1/UpdateService/SimpleUpdateActionInfo"
}
},
"@odata.id": "/redfish/v1/UpdateService"
}
提供反馈