| commit | 38ee9c8d8099e3364e8769c61d0647e39f4fc332 | [log] [tgz] |
|---|---|---|
| author | Kantesh Nagaradder <kantesh.nagaradder@ibm.com> | Fri Apr 07 00:58:12 2023 -0500 |
| committer | SunnySrivastava <sunnsr25@in.ibm.com> | Mon Jul 17 09:07:26 2023 +0000 |
| tree | 3ef6a98b4d8e5b1646730968f5c180a7925b2ecb | |
| parent | 051b34fb4923b970041ffb58d84f8359d3423d31 [diff] |
Backup & restore changes for bonnell's system VPD This commit implements the changes of system backplane VPD backup on the base banel VPD and restoring it from the base panel VPD The bonnell BMC is embedded in the system backplane, so if either fails, the backplane should be replaced as a whole. So the changes have been made to backup the system backplane critical keywords on the operator panel base EEPROM under the VSBK record. Test: Case 1: A PEL with error severity is created when the base panel EEPROM file doesn't exist. Case 2: A PEL with error severity is created when the base panel VPD has ecc exceptions. Case 3: A PEL with error severity is created when the base panel EEPROM doesn't contain VSBK record. Case 4: System VPD's critical keywords are backing up in the base panel VPD Case 5: System VPD's critical keywords are restoring from the base panel VPD Case 6: The VSBK record creation and population of properties on dbus Case 7: A PEL with warning serverity is created when there is a mismatch between system VPD & base panel keyword values. Case 8: A PEL with error serverity is created when both the system VPD & base panel keyword values are default. Tests above works as expected. Change-Id: Ieea6ff4e267518f010c924e2d51a2b080b47e91c Signed-off-by: Kantesh Nagaradder <kantesh.nagaradder@ibm.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 here.
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.