Skip to content

Commit

Permalink
PowerSupply, Chassis: add powering association
Browse files Browse the repository at this point in the history
Create association documentation between Chassis and PowerSupply.
For a machine with multiple chassis, it is necessary to indicate which
chassis a PowerSupply is managed by.
One example is that the ChassisID and PowerSupplyID in the Redfish URL
need to match, so we can confirm it through this association.

Signed-off-by: Chicago Duan <duanzhijia01@inspur.com>
Change-Id: I6beb18fd0b621cec6cd4a38606e009cda40f9761
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
  • Loading branch information
ChicagoDuan authored and williamspatrick committed Oct 7, 2022
1 parent e8821cc commit 11efbb3
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 0 deletions.
10 changes: 10 additions & 0 deletions yaml/xyz/openbmc_project/Inventory/Item/Chassis.interface.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -43,3 +43,13 @@ enumerations:
description: >
A logical division or portion of a physical chassis that contains
multiple devices or systems that cannot be physically separated.
associations:
- name: powered_by
description: >
Objects that implement Chassis can optionally implement the
'powered_by' association to provide a link to one or more
power supplies.
reverse_name: powering
required_endpoint_interfaces:
- xyz.openbmc_project.Inventory.Item.PowerSupply
Original file line number Diff line number Diff line change
@@ -1,2 +1,11 @@
description: >
Implement to provide PowerSupply attributes.
associations:
- name: powering
description: >
Objects that implement PowerSupply can optionally implement the
'powering' association to provide a link back to a Chassis.
reverse_name: powered_by
required_endpoint_interfaces:
- xyz.openbmc_project.Inventory.Item.Chassis

0 comments on commit 11efbb3

Please sign in to comment.