docs/designs/vpd-collection.md

18 - Some of the VPD information such as FRU part number, serial number need to be
30 The VPD data itself may reside on an EEPROM (typical) or may be synthesized out
40 Each keyword can be used to contain specific data about the FRU. For example,
42 instance of a part. Keywords themselves can be combined or grouped into records.
43 For example, a single record can be used to group keywords that have similar
71   BMC applications need to be able to read VPD for FRUs to determine, for ex.,
74   Some of the VPD will need to be exchanged with the host.
82 - If a FRU does not have a VPD store such as an EEPROM, the BMC should be able
83   to synthesize VPD for such FRUs. Details on VPD synthesis will be in its own
86 - The BMC should be able to recollect VPD for FRUs that can be hotplugged or
89 - The BMC must log errors if any of the VPD cannot be properly parsed or fails
104 - There needs to be a tool/API that allows viewing and updating VPD for any
106   (such as FRUs that can be accessed both by the BMC and the host, but the host
128 updates will be made:
130 - Two new services will be created to handle the new VPD formats. ipz-vpd-parser
131   and a keyword-vpd-parser. These services shall be templated to allow for
132   multiple instances to be run.
134 - Another service will be created to update the inventory with location code
136   service can only be launched after the system VPD (stored on the backplane) is
139 - There will be one udev rule per EEPROM on the system from which the BMC has to
143 - Each udev rule will be setup to launch an instance of one of the VPD parser
152   VPD in the following format: There will be one interface per record (ex, VINI
169 - In case of keyword format VPD, all keywords shall be placed as properties
173   before updating the properties noted above, the properties shall be stored as
178 - To handle VPD writes, another systemd service will be launched once all the
179   VPD read services have completed. This service shall be a daemon that will
183 - Generation of the udev rules and configs shall be layered such that they can
184   be tweaked on a per-system basis.
191   when the host is up and running) will be handled. That will be presented in
201 the BMC that collects all of the VPD by BMC standby. The application has to be a
210 The application would be driven off of a configuration file that lists the FRUs
216   VPD formats. Although the application could be written in a way that allows
229 The application could be enhanced to:
253   the BMC boot flow. The impact should be kept to a minimum by achieving maximum
255 - Applications that need to read VPD keywords will be impacted in the sense that
261 VPD parsing function can be tested by faking out the VPD EEPROMs as files on the
267 VPD writes can be tested by writing a small command line utility that can invoke