Revision Date Author Comments
# 380bb024 09-Nov-2022 George Liu <liuxiwei@inspur.com>

Fix the association between Item and PowerSupply

PowerSupply should be associated with an Item, instead of Chassis.

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If2e7dbea6f1cf0eb2e598

Fix the association between Item and PowerSupply

PowerSupply should be associated with an Item, instead of Chassis.

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If2e7dbea6f1cf0eb2e5984bb83bea252fd7f94cf

show more ...


# 11efbb3c 26-Sep-2022 Chicago Duan <duanzhijia01@inspur.com>

PowerSupply, Chassis: add powering association

Create association documentation between Chassis and PowerSupply.
For a machine with multiple chassis, it is necessary to indicate which
chassis a Powe

PowerSupply, Chassis: add powering association

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>

show more ...


# b1b4d261 05-Jun-2021 William A. Kennington III <wak@google.com>

treewide: Create yaml directory

This allows the propagated yamldir paramter to work correctly in
subproject style builds. We don't want other files in the project
conflicting with tools that scan th

treewide: Create yaml directory

This allows the propagated yamldir paramter to work correctly in
subproject style builds. We don't want other files in the project
conflicting with tools that scan the yamldir.

Change-Id: Ie2759c7f3baf399392cdda0e507055ceb262d2e1
Signed-off-by: William A. Kennington III <wak@google.com>

show more ...