openbmc/bmcweb/AGGREGATION.md

3 With Redfish aggregation the host BMC aggregates resources from specified
9 BMC handles the additional processing required to allow the aggregating BMC and
10 satellite BMCs to be observable as a singular combined BMC.
23 satellite BMC. The following is an example entity-manager json config for a
43 ## Satellite BMC Restrictions
45 - Can only aggregate a single satellite BMC
46 - HTTP only connection to satellite BMC
47 - No authentication on satellite BMC
65 versions could differ from the schema versions on the aggregating BMC. Instead
70 aggregating BMC is compatible with all aggregated satellite resources.
75 resources on the satellite BMC, but a link for the unsupported collection will
81 distinguish them from resources that are local to the aggregating BMC. The
83 BMC. This should result in the aggregation prefix being unique to each
84 aggregating BMC.
92 When support is added for aggregating more than one satellite BMC, then each
98 aggregating BMC. In addition, the request is forwarded to the satellite BMCs as
104 aggregating BMC.
109 aggregating BMC. Similarly, we ignore any satellite responses that do not return
141 BMC. These requests are identified by the presence of the aggregation prefix in
146 1. Determine the target satellite BMC based on the prefix
148 3. Forward the request to the satellite BMC
150 5. Return the updated response from the satellite BMC
167 We consider any response to be a valid response code from the satellite BMC. The
172 the retry policy. Exhausting the retry policy will result in the aggregating BMC
183 3. Aggregate more than one satellite BMC
184 4. Support HTTPS connection to satellite BMC