Suggestions required for sending the RF events in case of change happens on the backend-repos

[Patrick Williams]

On Wed, Nov 29, 2023 at 11:33:30PM +0530, Chandramohan wrote:
> H All,
> 
> I wanted to discuss various design approaches for, sending RF events from
> various OpenBMC services for resource create/delete/modify cases (but not
> limited to this),
> Please find the details below:

I'm not fully grasping what you're trying to solve.  Do you have more
details on what your use-case is?

Generally we _don't_ want all the repositories to know "Redfish".  If
what you're proposing is some special Redfish-oriented handling in every
repository, I don't think this will fly.

For Redfish Events, I suspect someone would need to start a dbus monitor
in BMC web to observe interesting changes and to turn them into Redfish
Events inside bmcweb itself.

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20231201/6137d554/attachment.sig>