| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
phosphor-led-manager already has platform and partition system attention
indicator D-Bus objects implementing xyz.openbmc_project.Led.Group. but,
was not added to association json which this commit is doing.
Signed-off-by: Lakshminarayana R. Kammath <lkammath@in.ibm.com>
Change-Id: I3803cbb2d07626e3af6474ea8e74d987f4a963b0
|
|
Make altitude sensor visible via redfish, chassis, all-sensors.
Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Change-Id: I7e032e74ad8889e7e80e197dccc7b65a26482c0a
|
|
Earlier enclosure_identify and enclosure_fault associations were missing in the inventory manager.
With this checkin we are adding those associations.
busctl get-property xyz.openbmc_project.Inventory.Manager /xyz/openbmc_project/inventory/system/chassis xyz.openbmc_project.Association.Definitions Associations
a(sss) 24 "fault_led_group" "fault_inventory_object" "/xyz/openbmc_project/led/groups/enclosure_fault" "identify_led_group" "identify_inventory_object"
"/xyz/openbmc_project/led/groups/enclosure_identify" "chassis" "inventory" "/xyz/openbmc_project/inventory/system/chassis" ....
After closely looking into all the LED's it was identified that
enclosure_fault and enclosure_identify is missing in the association
and this commit is to enable same
Signed-off-by: Lakshminarayana R. Kammath <lkammath@in.ibm.com>
Change-Id: I42728d994e9110c56c607aeea98623fe2613af92
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Change Ie1a7c389edb6b7a048836a49283ceb62de51bba5 will be transitioning
the 'Type' property in Inventory.Item.Chassis to an enumeration.
In order to avoid crashing in PIM we need these default values in the
starting YAML to be fully-qualified enumeration names that will match
the values which will start in Ie1a7c.
This code is safe to merge as is without any PDI or PIM changes. Prior
to the PDI change, we must make a change to PIM that allows conversion
automatic from string->enum, leveraging library interfaces available in
sdbusplus. These will be submitted independently.
I checked the codebase for usage of this string. It appears that the
value is currently, effectively, write-only. There is code in bmcweb
that fills in the equivalent Redfish value but currently just hard-codes
the string 'RackMount'.
Tested: Booted Witherspoon in a QEMU model with this change and proposed
changes to sdbusplus + PIM. PIM no longer coredumps with the PDI change
and yields an expected persistence file:
```
$ pwd
/var/lib/phosphor-inventory-manager/xyz/openbmc_project/inventory/system/chassis
$ cat xyz.openbmc_project.Inventory.Item.Chassis
{
"value0": {
"cereal_class_version": 2,
"Type": 3
}
}
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Icaf9447f31ccdd945cdf74b3e017682e4aed686f
|
|
- ddimm
- capi connector
- nvme
- pcie slot
- pcie cable card top and bottom enclosures
- base op panel
Signed-off-by: Lakshminarayana R. Kammath <lkammath@in.ibm.com>
Change-Id: I7de498f83ab3bace4ce39deb98c31c71c40f2dd4
|
|
This commit adds associations for all the inventory that
gets represented as Assemblies in Redfish.
Change-Id: Id4e9e4ac870e5bed665462d161abde00c4b85554
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: Ib7a9802582e146b5e2e5edb7b2df1800dfe36b22
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Power supply, fans and pcie slots are tied to a particular
chassis and thus need the associations for redfish to use them.
Change-Id: I71b9596b811c910fac65c16af4f008954a934b30
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Rainier-4U systems have 4 power supply D-Bus objects and hence
updated the associations json to have a mapping for powersupply2
and powersupply3 led group D-Bus objects.
Change-Id: I21ea628928a5f6a7d2dc014eb25559c6d2e15722
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built rainier and verified files were installed:
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,everest_associations.json
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,rainier-4u_associations.json
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,rainier-2u_associations.json
Change-Id: I422374d25966e731147eebd1772d5cfc4f62f9d9
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
This commit adds below forward and reverse associations
"rType": "fault_inventory_object",
"fType": "fault_led_group"
"rType": "identify_inventory_object",
"fType": "identify_led_group"
Change-Id: Icaad89e6e690c3c0a635362e8c604874bc3f37fe
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
The phosphor-inventory-manager application supports creating
associations based on JSON files, where the JSON files have conditions
built into them that say which inventory-manager property values are
required for the associations files to be valid.
Add minimal associations files for the Rainier 2U, Rainier 4U, and
Everest systems that just contain the fan inventory associations for
now. The condition is the 'IM' property on the com.ipzvpd.VSBP
interface on the system/chassis/motherboard path.
Change-Id: Ib6807d8982a2efeb94692b917804c53965d6c98a
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
