| commit | dffc8a8c49797822d60c52550943257aea3ee2a4 | [log] [tgz] |
|---|---|---|
| author | Janet Adkins <janeta@us.ibm.com> | Wed Jul 30 16:59:21 2025 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Sep 08 19:19:55 2025 +0000 |
| tree | 3ab0c58161919dcb90ae49517d97bac1096ff843 | |
| parent | 6cfabdfe936b3bbcac15eec2bb060fafb9c8ba41 [diff] |
State: Add min and max to Redundancy interface Add RedundancyMinimum and RedundancyMaximum properties to the Redundancy interface to specify how many BMC objects can be part of the redundant group. These properties can be utilized by bmcweb to support the Redundancy property of the Manager Redfish schema.[1] The Redfish definition for Redundancy requires minimum to be reported.[2] [1] http://redfish.dmtf.org/schemas/v1/Manager.v1_22_0.json#/definitions/Manager [2] http://redfish.dmtf.org/schemas/v1/Redundancy.v1_5_0.json#/definitions/Redundancy Change-Id: I02db0fb7259b2922711fb56cdb1455185d4a609a Signed-off-by: Janet Adkins <janeta@us.ibm.com>
diff --git a/yaml/xyz/openbmc_project/State/BMC/Redundancy.interface.yaml b/yaml/xyz/openbmc_project/State/BMC/Redundancy.interface.yaml index a9d8b85..bfa8d91 100644 --- a/yaml/xyz/openbmc_project/State/BMC/Redundancy.interface.yaml +++ b/yaml/xyz/openbmc_project/State/BMC/Redundancy.interface.yaml
@@ -49,6 +49,21 @@ not trigger any intervention that could be necessary when redundancy is lost just due to a BMC reboot. Any time the passive BMC goes offline a full file sync would be necessary when it comes back. + - name: RedundancyMinimum + type: size + flags: + - readonly + default: 2 + description: > + The minimum number of BMC objects needed for redundancy to be enabled. + - name: RedundancyMaximum + type: size + flags: + - readonly + default: maxint + description: > + The maximum number of BMC objects allowed to be part of the redundancy + group. enumerations: - name: Role