dbus-sensors: RedfishSensor: Sync with upstream

This is a large change, but it adds another daemon to the suite of
existing dbus-sensors daemons, namely RedfishSensor.

This provides a service to read sensor data from a remote Redfish
server, in much the same way as other dbus-sensors daemons read their
sensor data from local hardware.

Input is D-Bus Inventory from entity-manager, for configuration.
Output is D-Bus Sensor objects, as with other dbus-sensors daemons.

Design doc:
https://gerrit.openbmc.org/c/openbmc/docs/+/58954

Configuration doc (instructions how to configure):
https://gerrit.openbmc.org/c/openbmc/docs/+/58955

Tested: Appropriately configured, it works. It pulls sensor data from
a live Redfish server, and makes it available locally. The data is
refreshed in a timely manner, and is suitable for use by consumers of
dbus-sensors Sensor objects, such as phosphor-pid-control for cooling.

Patch Tracking Bug: b/266550783
Upstream info / review: https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/60429
Upstream-Status: Submitted
Justification: In midst of iterative changes to address upstream concerns

Google-Bug-Id: 266550783
Signed-off-by: Josh Lehan <krellan@google.com>
Change-Id: Ia64cf33f447be339bec7b279351dcba0208a4281
(cherry picked from commit 4ba62792b108e221982c8bd319794afc6e93b3d9)
Signed-off-by: Josh Lehan <krellan@google.com>
2 files changed
tree: 599abe2ca3e431a058ebbcc1c6c00742c4ac577c
  1. conf/
  2. dynamic-layers/
  3. meta-nuvoton-npcm8xx/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-google/
  7. recipes-kernel/
  8. recipes-phosphor/
  9. LICENSE
  10. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.