diff options
| author | Andrew Geissler <geissonator@yahoo.com> | 2019-03-05 04:11:54 +0300 |
|---|---|---|
| committer | Ed Tanous <ed.tanous@intel.com> | 2019-04-11 00:42:09 +0300 |
| commit | 0e7de46f9b6365bad4e79a3933112750c5bf7853 (patch) | |
| tree | 7dc54d68dfaec9639b5e16f537ff7f648f043599 /include/webassets.hpp | |
| parent | 87d847298c57168b1af9bc8bbf201073ef3e76fe (diff) | |
| download | bmcweb-0e7de46f9b6365bad4e79a3933112750c5bf7853.tar.xz | |
fw-update: Support host image update
Per the Redfish schema for the UpdateService, it supports all
SoftwareInventory targets. On OpenBMC this is currently the BMC and the
Host (BIOS) firmware.
Introduced a new fwUpdateInProgress static variable so that the signal
subscription could be disabled once the required interface was added.
This prevented multiple call backs and multiple activations of the same
image.
Tested: Verified that a host and BMC image update worked as expected on
a witherspoon system.
$ curl -k -H "X-Auth-Token: $TOKEN" -H "Content-Type: application/octet-stream" -X POST -T ./obmc-phosphor-image-witherspoon.ubi.mtd.tar https://${BMC_IP}/redfish/v1/UpdateService
{
"@Message.ExtendedInfo": [
{
"@odata.type": "/redfish/v1/$metadata#Message.v1_0_0.Message",
"Message": "Successfully Completed Request",
"MessageArgs": [],
"MessageId": "Base.1.4.0.Success",
"Resolution": "None",
"Severity": "OK"
}
]
}
Change-Id: I7bb9381f1b79bf65604464b628ef98646951d840
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'include/webassets.hpp')
0 files changed, 0 insertions, 0 deletions