commit | 9cc42abf0e7ca1d4cc83489afb4b467cb13ee72c | [log] [tgz] |
---|---|---|
author | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed Dec 12 16:36:51 2018 -0500 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Mon Jan 07 15:59:43 2019 -0500 |
tree | 20a1675eb11e79bc3cbc676a77639d355b0e829f | |
parent | ca2a8416f418c045667975e56bc5a8d141abd1e4 [diff] |
manager: refactor interface templates Many of the templates in manager.hpp are _almost_ testable. Enable testing by porting to a new header - interface_ops.hpp - to be activated later. Enhancements include: Dropped 'PropertiesVariant' wrapper template for reduced comprehensional complexity. More intuitive HasProperties implementation. HasProperties is a type traits template that simply checks for the presence of a nested PropertiesVariant typename. These are provided by sdbusplus generated server bindings for dbus interfaces that have properties. Standalone templates for make, assign, serialize and deserialize interface. There was no good reason to couple these, and the resulting types and method names are more intuitive. Templated serialize/deserialize operations so the dependency on cereal can be abstracted away. Change-Id: Ia449628eeaa9732bbbc51b0609bd449f43ebcb7c Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Phosphor Inventory Manager (PIM) is an implementation of the xyz.openbmc_project.Inventory.Manager DBus interface, and supporting tools. PIM uses a combination of build-time YAML files and run-time calls to the Notify method of the Manager interface to provide a generalized inventory state management solution.
PIM includes a YAML parser (pimgen.py). For PIM to do anything useful, a set of YAML files must be provided externally that tell it what to do. Examples can be found in the examples directory.
The following top level YAML tags are supported:
events
Supported event tags are:
Subsequent tags are defined by the event type.
match
Supported match tags are:
startup
Supported startup tags are:
filters
Supported filter tags are:
Subsequent tags are defined by the filter type.
The available filters provided by PIM are:
propertyChangedTo
The property under test is obtained from an sdbus message generated from an org.freedesktop.DBus.Properties.PropertiesChanged signal payload.
Supported arguments for the propertyChangedTo filter are:
propertyIs
The property under test is obtained by invoking org.freedesktop.Properties.Get on the specified interface.
Supported arguments for the propertyIs filter are:
The service argument is optional. If provided that service will be called explicitly. If omitted, the service will be obtained with an xyz.openbmc_project.ObjectMapper lookup.
propertyIs can be used in an action condition context when the action operates on a dbus object path.
actions
Supported action tags are:
Subsequent tags are defined by the action type.
The available actions provided by PIM are:
destroyObject
Supported arguments for the destroyObject action are:
Conditions are tested and logically ANDed. If the conditions do not pass, the object is not destroyed. Any condition that accepts a path parameter is supported.
setProperty
Supported arguments for the setProperty action are:
Conditions are tested and logically ANDed. If the conditions do not pass, the property is not set. Any condition that accepts a path parameter is supported.
createObjects
Supported arguments for the createObjects action are:
After running pimgen.py, build PIM using the following steps:
./bootstrap.sh ./configure ${CONFIGURE_FLAGS} make
To clean the repository run:
./bootstrap.sh clean