Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-virtual-sensor / 04605fa2ad256f0bdedcfc1f9bcd1f24fdc4cd93
commit04605fa2ad256f0bdedcfc1f9bcd1f24fdc4cd93[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Wed May 28 16:54:49 2025 -0400
committerPatrick Williams <patrick@stwcx.xyz>Thu May 29 11:00:11 2025 +0000
tree7c6ed04416fcff3bd4477a74482028f0ea0db6df
parent4b98de56a69895d0c26e9abd6e236a73a236263a [diff]
move daemons to libexec

Per the organization anti-pattern, executables are expected to be
installed into libexec instead of bin[1].  Update service files and
meson to install there.

[1]: https://github.com/openbmc/docs/blob/master/anti-patterns.md#incorrect-placement-of-executables-in-sbin-usrsbin-or-bin-usrbin

Change-Id: Ibb102f387c27593c81f41aa0adc3b994ca9185e2
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
2 files changed
tree: 7c6ed04416fcff3bd4477a74482028f0ea0db6df
  1. subprojects/
  2. test/
  3. .clang-format
  4. .clang-tidy
  5. .editorconfig
  6. .gitignore
  7. .prettierrc.yaml
  8. calculate.cpp
  9. calculate.hpp
  10. dbusSensor.cpp
  11. dbusSensor.hpp
  12. dbusUtils.cpp
  13. dbusUtils.hpp
  14. exprtkTools.hpp
  15. LICENSE
  16. main.cpp
  17. meson.build
  18. meson.options
  19. OWNERS
  20. phosphor-virtual-sensor.service.in
  21. README.md
  22. thresholds.hpp
  23. virtual_sensor_config.json
  24. virtualSensor.cpp
  25. virtualSensor.hpp
README.md

phosphor-virtual-sensor

phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json from one of three locations:

  1. The current directory.
  2. /var/lib/phosphor-virtual-sensor
  3. /usr/share/phosphor-virtual-sensor

By default the repository will install a sample config into (3).

There are two types of data in this file.

virtual sensor configuration information

See virtual_sensor_config.json in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.

information to get a virtual sensor configuration from D-Bus

For example:

{
  "Desc": {
    "Config": "D-Bus"
  }
}

Sensors added this way can only use a set of restricted calculations. Currently supported types are Average, Maximum, Minimum, Sum and ModifiedMedian.

The virtual sensor configuration information needs to be added into the relevant hardware configuration file in entity-manager. This method of adding a virtual sensor allows a recipe that builds for different hardware configurations to have different virtual sensors for each configuration.

The virtual sensor configuration in entity manager follows a different format to the JSON in virtual_sensor_config.json (specified in entity-manager/schemas/VirtualSensor.json).