Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-inventory-manager / b666e539af3e70bf73f3aa459e54190c71c878f0
commitb666e539af3e70bf73f3aa459e54190c71c878f0[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Tue Dec 11 16:36:02 2018 -0500
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Mon Dec 17 13:10:10 2018 +0000
tree6ae1f9b54776b85da656c5e03e11174efec4fbbc
parent783d1f98e32a7ee77db645196ba6843c0b0d9419 [diff]
types: minor build improvements

We don't need all of message.hpp to be included from types.hpp since
all we need is the variant definition.  Instead, just get
sdbusplus/message/types.hpp, which has the variant definition.

message.hpp picks up <memory> so add that where it is now missing
(events.hpp).

Add a missing cstdint include.

Change-Id: Ic033ceafcd982dba3e39592a4d8f64e5b4e65f2e
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2 files changed
tree: 6ae1f9b54776b85da656c5e03e11174efec4fbbc
  1. example/
  2. test/
  3. .clang-format
  4. .gitignore
  5. app.cpp
  6. argument.mako.cpp
  7. bootstrap.sh
  8. configure.ac
  9. errors.cpp
  10. errors.hpp
  11. events.hpp
  12. functor.cpp
  13. functor.hpp
  14. gen_serialization.mako.hpp
  15. generate_makefile.sh
  16. generated.mako.cpp
  17. LICENSE
  18. MAINTAINERS
  19. Makefile.am
  20. Makefile.extra.in
  21. manager.cpp
  22. manager.hpp
  23. method.mako.cpp
  24. pimgen.py
  25. README.md
  26. serialize.hpp
  27. signature.mako.cpp
  28. types.hpp
  29. utils.hpp
README.md

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.

YAML

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:

  • description - An optional description of the file.
  • events - One or more events that PIM should monitor.

events

Supported event tags are:

  • name - A globally unique event name.
  • description - An optional description of the event.
  • type - The event type. Supported types are: match and startup.
  • actions - The responses to the event.

Subsequent tags are defined by the event type.

match

Supported match tags are:

  • signatures - A DBus match specification.
  • filters - Filters to apply when a match occurs.

startup

Supported startup tags are:

  • filters - Filters to apply at startup.

filters

Supported filter tags are:

  • name - The filter to use.

Subsequent tags are defined by the filter type.

The available filters provided by PIM are:

  • propertyChangedTo - Only match events when the specified property has the specified value.
  • propertyIs - Only match events when the specified property has the specified value.

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:

  • interface - The interface hosting the property to be checked.
  • property - The property to check.
  • value - The value to check.

propertyIs

The property under test is obtained by invoking org.freedesktop.Properties.Get on the specified interface.

Supported arguments for the propertyIs filter are:

  • path - The object hosting the property to be checked.
  • interface - The interface hosting the property to be checked.
  • property - The property to check.
  • value - The value to check.
  • service - An optional DBus service name.

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:

  • name - The action to perform.

Subsequent tags are defined by the action type.

The available actions provided by PIM are:

  • destroyObject - Destroy the specified DBus object.
  • setProperty - Set the specified property on the specified DBus object.

destroyObject

Supported arguments for the destroyObject action are:

  • paths - The paths of the objects to remove from DBus.
  • conditions - An array of conditions.

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:

  • interface - The interface hosting the property to be set.
  • property - The property to set.
  • paths - The objects hosting the property to be set.
  • value - The value to set.
  • conditions - An array of conditions.

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:

  • objs - A dictionary of objects to create.

Building

After running pimgen.py, build PIM using the following steps:

    ./bootstrap.sh
    ./configure ${CONFIGURE_FLAGS}
    make

To clean the repository run:

 ./bootstrap.sh clean