|
Post by kilgorep on Feb 7, 2023 19:56:47 GMT
I'm looking at implementing a Battery resource to represent the backup power source for a StorageController resource. I can see that mutual linkages have been added to the schemas with Links.StorageControllers for Battery and Links.Batteries for StorageController. The piece I'm wanting to make sure I'm clear about is the the Battery resource URI as listed in DSP2046: /redfish/v1/Chassis/{ChassisId}/PowerSubsystem/Batteries/{BatteryId}.
From parsing this URI, I take it I'd need to also implement a minimal Chassis with ChassisType=Card to represent the controller as well as its PowerSubsystem child. It doesn't look like there's a method in the Chassis schema to directly link this Chassis to the StorageController though, only a Link.Storage to the Storage resource owning the StorageControllerCollection that my StorageController is a member of.
Does this arrangement make sense, or is there a more straightforward method to expose this Battery resource?
|
|
|
Post by jautor on Feb 8, 2023 18:22:24 GMT
I think you've crossed the "complex card/adapter" boundary where we would say, yes, it's time to implement a Chassis resource to cover those types of dedicated infrastructure devices. We'd give the same guidance today if you had dedicated fans on the board.
So you'd do a (minimal) Chassis resource with the PowerSubsystem and Battery collection there - those can all be simple and static resources until you get to your Battery instance. That is a bit of overhead, but at this point I would be very reluctant to add "dupliate" paths to essentially re-create those subsystems for a "card" - because clients will then have to learn and check a bunch of places to "find the batteries in a system".
Jeff
|
|