tree ed2f01ae6f84022e7cf8b3e807aa3b2c993909ab
parent a23af1206bc4c835516909c87c71be0e7428264c
author Kumar Thangavel <thangavel.k@hcl.com> 1649658093 +0530
committer Kumar Thangavel <thangavel.k@hcl.com> 1663594659 +0000

Add multi-host support to handle IPMI restriction mode.

Added multi-host and IPMI based devices to support the IPMI
whitelist restriction mode in ipmid.

The machine specific .yml file has the default restriction
mode dbus path. Ex. Whitelist. These restriction modes dbus
paths added for all the hosts and other IPMI devices Ex.
ocp_debug_card. These information will be displayed in the
setting manager dbus objects.

Ipmid reads hostIdx from the command request. These hostIdx
values are getting from ipmb-channels.json. This ipmb-channels
entires can configure from machine layer.

busctl tree xyz.openbmc_project.Settings | grep restriction
| | |-/xyz/openbmc_project/control/host1/restriction_mode
| | |-/xyz/openbmc_project/control/host2/restriction_mode
| | |-/xyz/openbmc_project/control/host3/restriction_mode
| | |-/xyz/openbmc_project/control/host4/restriction_mode
|-/xyz/openbmc_project/control/ocp_debug_card/restriction_mode

The mapping between IPMI based devices and restriction mode
dbus objects from settings manager is filtered with restriction
mode dbus interface as like above. The mapping is based on the
config file(json, yml) file entries.

Can configure .yml and .json entries based on the order and
IPMI devices and restriction mode dbus object mapping.

TESTED : Built Facebook YosemiteV2 images and loaded on the
target hardware. Verified restriction mode enabled for all
four hosts and ocp_debug_card.

Signed-off-by: Kumar Thangavel <thangavel.k@hcl.com>
Change-Id: I3d338b6cd37a817653ca981c5322a77e60d3f992