commit | 2db8d41fe0e819a38a6c8450ba97048ce7007a69 | [log] [tgz] |
---|---|---|
author | George Liu <liuxiwei@inspur.com> | Mon Aug 21 16:41:04 2023 +0800 |
committer | George Liu <liuxiwei@inspur.com> | Thu Aug 24 08:06:43 2023 +0800 |
tree | 5b62afd2f90efcb821364e995d039e584176ed4d | |
parent | 9492149041be80c06a46ffd54c7166e00e74dbd4 [diff] |
Optimize the createVirtualSensorsFromDBus method logic Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I56a7a229a8d5a6f414b2ba036627e4e7a8185bbd
phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json
from one of three locations:
/var/lib/phosphor-virtual-sensor
/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.
See virtual_sensor_config.json
in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.
For example:
{ "Desc": { "Config": "D-Bus", "Type": "ModifiedMedian" } }
Sensors added this way can only use a set of restricted calculations. Currently the only type supported is 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).