Re: Redfish Host Interface
toggle quoted messageShow quoted text
-----Original Message-----Redfish Host Interface is built for OS to communicate with Redfish service on either BMC or out-of-band service (I don’t see this use case yet). UEFI use case is similar to how OS communicates with Redfish service through Redfish HI.
That is, the Redfish service would be provided by UEFI itself (via an IPThis is interesting , however you will need edk2 web server and the implementation of Redfish service on edk2 as well. Not sure how this use case works for OS <-> in-band Redfish service on edk2. Or you just would like to build up an stand along Redfish service on edk2 and other Redfish clients can connect to it?
Redfish HI just provides the Redfish information to Redfish clients, the majority users are OS and firmware. Client sends the request to service for the property through HTTP. Rare use cases that service asks client for something on its own initiative, Redfish event service is one of the service-to-client action however client has to registers even first.For example, if a BMC wanted to access EFI variables directly from UEFI viaan IP interface with no functional OS present.
So BMC accesses to EFI variable through Redfish HI seems to me not an use case of generic Redfish services.
Laszlo, thanks for providing below information.idea... but I would need to do some work?