summaryrefslogtreecommitdiffstats
path: root/gen_ipmi_fru.pl
Commit message (Collapse)AuthorAgeFilesLines
* Add entityID and entityInstance in the generated YAMLRatan Gupta2018-02-131-3/+27
| | | | | | | | | | | EntityID will be given by the config yaml and unique instance id would be generated for each entityID. eg: if proc is having entityID is x and if there is y instances of type x then this commit would generate y unique id for type x. Change-Id: Ie7d848d96a6f335999eb226a4267b347f0e4ab2b Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
* Inventory: Implementing the association of objects.Ratan Gupta2017-02-221-43/+40
| | | | | | | | This script will look at the associated types in the config file and make the association. Change-Id: I25bafb1308bbcb1febc2c24d8154643a1f154cdb Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
* gen_openpower_fru.pl : Fetch inventory pathsDeepak Kodihalli2017-02-141-17/+2
| | | | | | | | | | | | | | In preparation for the openpower-vpd-parser recipe, this script will, from an input openpower vpd-config YAML file, determine which inventory objects we're interested in, and will fetch from the MRW pathnames these objects should have. The script will output a file in a format that can serve as an environment file for a systemd service, which in turn will launch the openpower-vpd-parser application with this information. Change-Id: I7c4fa70af002f63bd5501093802c1d41bd503e88 Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
* ipmi-fru-parser: Use YAML::TINYBrad Bishop2017-01-301-1/+1
| | | | | | | YAML::XS is not required and not available. Change-Id: Ia0250c08ff72dfc067291719183833fdb4204d03 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* gen_ipmi_fru.pl : retrieve children of FRUsRatan Gupta2017-01-261-2/+62
| | | | | | | | For IPMI FRUs, figure out if they have children (non-FRU) that are of interest, and if yes, generate metadata for those children. Change-Id: Iecc54dd39633f869b2210de83df9cb3292ab483a Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
* gen_ipmi_fru.pl: construct FRU metadataRatan Gupta2017-01-261-10/+59
| | | | | | | | | | | | | For IPMI FRUs, generate a file to depict which dbus properties are implemented for a FRU, and what IPMI FRU properties those dbus properties map to. This commit defines a YAML file which helps figure out the supported dbus inteface/properties for a FRU, and what the corresponding IPMI FRU properties are. Change-Id: I26de1aa26e3a74fd8cc95bb0d479d9b036eb5683 Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
* gen_ipmi_fru.pl : Fetch FRU information from MRWRatan Gupta2017-01-231-0/+71
This commit serves as a building block since the script can now just print certain attributes (see output example below) for FRU elements defined in the MRW. Typically, FRUs of interest to IPMI will have a non-zero FRU id defined. Output example: FRUID => 1, FRUType => SYS, ObjectPath => /system FRUID => 2, FRUType => NODE, ObjectPath => /system/chassis Change-Id: I3f27f905b2a366277e8a6120142c3fb136a44ad5 Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
OpenPOWER on IntegriCloud