Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / ca738cf1acca2a0cb9f0189adbf9ea0c1505efff
commitca738cf1acca2a0cb9f0189adbf9ea0c1505efff[log] [tgz]
authorAnupama B R <anupama.b.r1@ibm.com>Fri Sep 19 06:40:54 2025 -0500
committerSunnySrivastava <sunnsr25@in.ibm.com>Wed Oct 15 13:44:45 2025 +0000
tree1041c749ab6a84f556b0a779a2b2d3ffb0e77933
parent8042bbf27edb16536e05ba4788b22acf8aee289b [diff]
Implementation of priming in wait-vpd-parsers

As part of PST priming system inventory and FRUs VPD collection will be
part of systemd target, instead of being triggered internally by
vpd-manager.

This commit implements priming system blueprint in wait-vpd-parsers
application and removes the priming from vpd-manager initialization
flow.

```
Testing performed:
1. Removed PIM cache path in the system.
2. Restarted PIM service.
systemctl  restart xyz.openbmc_project.Inventory.Manager
3. Observed inventory paths are removed under PIM using below command
busctl  tree xyz.openbmc_project.Inventory.Manager
3. Restarted wait-vpd-parsers service
systemctl  restart wait-vpd-parsers
4. Observed that system is primed again with all inventory object paths, using below command
busctl  tree xyz.openbmc_project.Inventory.Manager
```

Change-Id: Ic93f54e909a247587208082830c5ebbe48f69f50
Signed-off-by: Anupama B R <anupama.b.r1@ibm.com>
6 files changed
tree: 1041c749ab6a84f556b0a779a2b2d3ffb0e77933
  1. configuration/
  2. docs/
  3. service_files/
  4. test/
  5. vpd-manager/
  6. vpd-tool/
  7. vpdecc/
  8. wait-vpd-parser/
  9. .clang-format
  10. .gitignore
  11. LICENSE
  12. meson.build
  13. meson.options
  14. OWNERS
  15. README.md
README.md

Overview

This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found at a broken link.

The repository consists of two distinct applications, which are:

OpenPower VPD Parser

This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:

  • The supported records and keywords.
  • How VPD data is translated into D-Bus interfaces and properties.

The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.

IBM VPD Parser

This parser is can be built by passing in the --enable-ibm-parser configure option. This parser differs from the OpenPower VPD parser in the following ways:

  • It parses all the records and keywords from the VPD, including large keywords (Keywords that begin with a # and are > 255 bytes in length).
  • It relies on a runtime JSON configuration (see examples/inventory.json) to determine the D-Bus object path(s) that hold interfaces and properties representing the VPD for a given VPD file path.

Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.

TODOs and Future Improvements

  1. The long-term goal is to completely do away with the build time YAML driven configurations and instead reconcile the OpenPower VPD parser and the IBM VPD parser applications into a single runtime JSON driven application.
  2. Add details to the README on how to configure and build the application.
  3. More JSON documentation.
  4. Support for more IBM VPD formats.
  5. VPD Write and tool documentation.