| commit | 8042bbf27edb16536e05ba4788b22acf8aee289b | [log] [tgz] |
|---|---|---|
| author | Souvik Roy <souvikroyofficial10@gmail.com> | Mon Oct 06 09:16:50 2025 +0000 |
| committer | Souvik Roy <souvikroyofficial10@gmail.com> | Tue Oct 14 05:58:26 2025 +0000 |
| tree | 5ef534e77c83d6c90693d2969256d1ea6fa24058 | |
| parent | 68a70431cb6c98b83bf1c80abdcb1184c99ac6fb [diff] |
Log each FRU VPD collection in separate files For VPD collection logs, we need to maintain logs of last 3 FRU VPD collections and each FRU VPD collection flow should be logged in separate files. This commit implements these requirements. Test: ``` - Boot rainiest, wait for FRU VPD collection to be triggered by wait-vpd-parser.service - observe /var/lib/vpd directory and see collection_0.log file is created with log messages of FRU VPD collection - Trigger another FRU VPD collection using vpd-manager "CollectAllFRUVPD" D-bus method - Observe collection_1.log file getting created "CollectAllFRUVPD" D-bus method - Repeat above steps until collection_2.log is created - Trigger another FRU VPD Collection, observe collection_0.log file is overwritten with logs of latest FRU VPD collection ``` Change-Id: I5ef1f9eb339fbf1597955488b00b784a173c7e70 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.