docs/designs/physical-topology.md

27 Changes to phosphor-dbus-interfaces documenting new Associations have been
28 [proposed](https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/46806)
37 - Must represent one-to-many relationships from chassis inventory objects which:
38   - Connect to cables
39   - Contain other chassis and/or are contained by a chassis
40   - Contain storage drives
41   - Are cooled by fans
42   - Are powered by power supplies
43   - Contain processors such as CPUs
44   - Contain memory such as DIMMs
45 - Must support relationships which are predefined, detected at runtime, or a
47   - Runtime detection could include I2C bus scanning, USB enumeration, and/or
52 - Non-chassis inventory objects may also need one-to-many relationships
53   - CPUs have CPU cores and associated PCIe slots
54   - CPU cores have threads
59 phosphor-dbus-interfaces, inventory managers, and inventory consumers such as
62 ### phosphor-dbus-interfaces
70 #### phosphor-inventory-manager
72 phosphor-inventory-manager already has support for exporting custom
75 #### entity-manager  subsubsection
77 For entity-manager, we add new `Exposes` stanzas for the upstream and downstream
83 New code in entity-manager matches these properties and exposes associations on
84 D-Bus based on the types of the inventory objects involved. Two Chassis objects
126 choose to include the same Associations that phosphor-inventory-manager and
127 entity-manager use.
138 $ busctl get-property xyz.openbmc_project.ObjectMapper \
144 $ busctl get-property xyz.openbmc_project.ObjectMapper \
156 inventory items using D-Bus path names. As an example, a chassis object
176 phosphor-inventory-manager configurations can organize their D-Bus objects in
183 This new API will be documented in phosphor-dbus-interfaces as described above.
184 If no topology information is added to configuration files for entity-manager or
185 phosphor-inventory-manager, then the D-Bus interfaces exported by them will not
191 Does this repository require a new repository? No - all changes will go in
196 All new code in entity-manager and bmcweb will be unit tested using existing
197 frameworks and infrastructure. We will add new end-to-end tests in
198 openbmc-test-automation to ensure the Redfish output is correct.
204 - Update the example port type and name from `Connector` to `Port`
205 - Change the association names based on feedback from phosphor-dbus-interfaces
206   maintainers (chassisContains -> containing, chassisContainedBy ->