| commit | c0c007de496f738e9c23e12c5246335c7a1baf49 | [log] [tgz] |
|---|---|---|
| author | Souvik Roy <souvikroyofficial10@gmail.com> | Fri Aug 29 07:34:55 2025 +0000 |
| committer | SunnySrivastava <sunnsr25@in.ibm.com> | Wed Sep 03 13:58:03 2025 +0000 |
| tree | 60d37e2084f40b077c9f0b1857a5dafb34f14037 | |
| parent | ad0db9ee4c47d3b5ae8fd3dfca822063e715aa26 [diff] |
Trigger all FRU VPD collection from wait-vpd-parser This commit updates wait-vpd-parser to trigger FRU VPD collection. As part of PST VPD collection flow, FRU VPD collection needs to be triggered as a part of systemd target, instead of being triggered internally by vpd-manager. wait-vpd-parser service is triggered by systemd and then it uses vpd-manager's CollectAllFruVpd Dbus API to trigger FRU VPD collection. Test: ``` - Patch wait-vpd-parser executable and wait-vpd-parsers.service into rainiest simics - Restart wait-vpd-parsers.service - Observe FRU VPD collection is triggered - While FRU VPD collection is in progress, observe wait-vpd-parsers.service goes into retry loop and checks VPD CollectionStatus - Once FRU VPD collection is successful, observe wait-vpd-parsers.service exits with code 0 ``` Change-Id: I6aa5bc302429265faa0563d5e646c3bebd2fc38b Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
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:
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 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.
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:
# and are > 255 bytes in length).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.