fwupd/plugins/redfish
Gary Lin 7f79aa9ea7 redfish: Upload the firmware blob through HttpPushUri
Create a multipart request to upload the firmware blob

Signed-off-by: Gary Lin <glin@suse.com>
2018-08-06 06:19:56 +01:00
..
fu-plugin-redfish.c redfish: Upload the firmware blob through HttpPushUri 2018-08-06 06:19:56 +01:00
fu-redfish-client.c redfish: Upload the firmware blob through HttpPushUri 2018-08-06 06:19:56 +01:00
fu-redfish-client.h redfish: Upload the firmware blob through HttpPushUri 2018-08-06 06:19:56 +01:00
fu-redfish-common.c redfish: Add a plugin that uses the Redfish API 2018-06-29 20:17:45 +01:00
fu-redfish-common.h redfish: Add a plugin that uses the Redfish API 2018-06-29 20:17:45 +01:00
fu-self-test.c redfish: Add a plugin that uses the Redfish API 2018-06-29 20:17:45 +01:00
meson.build redfish: Read options from redfish.conf 2018-08-06 06:19:56 +01:00
README.md redfish: Read options from redfish.conf 2018-08-06 06:19:56 +01:00
redfish.conf redfish: Read options from redfish.conf 2018-08-06 06:19:56 +01:00

Redfish Support

Introduction

Redfish is an open industry standard specification and schema that helps enable simple and secure management of modern scalable platform hardware.

By specifying a RESTful interface and utilizing JSON and OData, Redfish helps customers integrate solutions within their existing tool chains.

Setting Service IP Manually

The service IP may not be automatically discoverable due to the absence of Type 0x42 entry in SMBIOS. In this case, you have to specify the service IP to RedfishUri in /etc/fwupd/redfish.conf

Take HPE Gen10 for example, the service IP can be found with the following command:

# ilorest --nologo list --selector=EthernetInterface. -j

This command lists all network interfaces, and the Redfish service IP belongs to one of "Manager Network" Interfaces. For example:

{
  "@odata.context": "/redfish/v1/$metadata#EthernetInterface.EthernetInterface",
  "@odata.id": "/redfish/v1/Managers/1/EthernetInterfaces/1/",
  "@odata.type": "#EthernetInterface.v1_0_3.EthernetInterface",
  "Description": "Configuration of this Manager Network Interface",
  "HostName": "myredfish",
  "IPv4Addresses": [
    {
      "SubnetMask": "255.255.255.0",
      "AddressOrigin": "DHCP",
      "Gateway": "192.168.0.1",
      "Address": "192.168.0.133"
    }
  ],
  ...

In this example, the service IP is "192.168.0.133".

Since the conventional HTTP port is 80 and HTTPS port is 443, we can set RedfishUri to either "http://192.168.0.133:80" or "https://192.168.0.133:443" and verify the uri with

$ curl http://192.168.0.133:80/redfish/v1/

or

$ curl -k https://192.168.0.133:443/redfish/v1/