|
|
Post by phawryle on Jan 24, 2020 1:00:51 GMT
Hi
We are implementing Virtual Media stack in OpenBMC following this design. In order to make connection in "proxy mode", we need to add new OEM property OEM->OpenBMC->WebSocketEndpoint holding socket name and location used to communicate between backend and web browser.
As current Virtual Media schema does not allow to set up connections in "proxy mode" manner, please consider to adjust schema accordingly. We are open to discuss about other options as well.
Best Regards, P
|
|
|
|
Post by jautor on Jan 27, 2020 19:55:50 GMT
We have a couple of related issues to allow the Virtual Media support to function in multi-node environments and are looking at several enhancements. Can you give us some more information about what exactly is needed? An example mockup and some descriptions would help.
Is this not covered by the "Port" property within "VirtualMedia" in ManagerNetworkProtocol? I suspect you're looking for a full URI as well?
Jeff
|
|
|
|
Post by phawryle on Jan 28, 2020 15:26:22 GMT
Communication is done via UNIX socket, not TCP/IP socket, so Port is not suitable. I do not understand usage of ManagerNetworkProtocol yet but it seems something different.
According to mentioned design we need just an entry which may be used to set up internal connection between WEBUI and Virtual Media service.
|
|
