1# Representing Inventory Items on DBus
2
3## Overview
4
5Inventory refers to physical objects. Some of the objects can be physically
6accessed, such as a board, a chassis and a drive. Some objects are embedded in
7other objects, such as a BMC embedded in a board, or a core in a CPU. The DBus
8interfaces in this directory describe the DBus representation of those physical
9objects. A graph consisting of Inventory objects as vertexes and Association as
10edges can be constructed that represents the relationship between different
11parts (such as chassis, drive, sensors, etc) of the system.
12
13## Inventory Association
14
15DBus objects with `xyz.opebmc_project.Inventory.Item.${ItemType}` interface
16might be associated with other inventory objects. Such association can be
17translated to Redfish schemas and then indicate the system topology.
18
19Document ObjectMapper association forward and reverse names as follows:
20
21- Item and Item: `{containing, contained_by}`
22- Sensor.Value and Bmc: `{monitoring, monitored_by}`
23- Fan and Item: `{cooling, cooled_by}`
24- Led.Group and Item: `{identifying, identified_by}`
25  `{fault_identifying, fault_identified_by}`
26- PowerSupply and Item: `{powering, powered_by}`
27- FabricAdapter and Connector.Port: `{connecting, connected_to}`
28- Cpu and PCIeSlot: `{connecting, connected_to}`
29