Feature Enhancement - Virtual Media over HTML5

[i.kononenko]

On 10.01.2022 13:25, Dhines Kumar Eswaran wrote:
> Hi All,
> 
> We are planning to support multiple Virtual media redirection support simultaneously.
> The below is the proposed design.
> 

Do you already saw the current work upon redesigning the jsnbd? What backend you are want to use?
The current progress of the nbd-proxy(jsnbd) might conflict with your design if it is based on the current nbd-proxy.
Please, refer to the appropriate gerrit change (1). 

> Existing Virtual media implementation:
> 
> WebUI is having single browse slot. It is used to redirect any kind of media, which can be either CD or HDD media instance.
> It is mapped with "/vm/0/0" API endpoint, and media endpoint is hardcoded to 0(Zero).
> 
> Virtual media is using "/dev/nbd0" device, and Dump offload is using "/dev/nbd1" device. It is parsing from the jsnbd configuration file.
> 
> Enhancement: Multiple simultaneous media redirections feature in single WebUI session.
> 
> WebUI will have two different browse slots to select the file, (i.e., ) Virtual media device - HDD and Virtual media device - CD. Both slots will support media redirection concurrently.
> 

We already have worked in the past to make able configure virtual-media device type by client request. E.g. in the usb-ctrl, we have a flag to specify whether USB, USB-RO, HDD, CD(DVD) VM-type.
Is it really required to have separate VM-endpoints for the CD and HDD types?

> Virtual media device - HDD slot is mapped through "/vm/0/0" API endpoint and media endpoint is 0(zero) which is used for initiating the proxy handler, which is present in bmcweb package.
> HDD slot will use "/dev/nbd0" device for HDD media instance redirection.
> 
> Virtual media device - CD slot is mapped through "/vm/0/1" API endpoint and media endpoint is 1(one) which is used for initiating the proxy handler, which is present in bmcweb package.
> CD slot will use "/dev/nbd1" device for CD media instance redirection.
> 
> Dump offload will use "/dev/nbd2" device. It is also parsing the nbd device from jsnbd configuration file.
> 
> Configuration file looks like,
> [cid:image001.jpg at 01D80639.FCBD3330]
> 
> This is an extension with what the community has implemented and I hope, it does not have any regression or conflict with others who are using virtual media and nbd devices.
> Please help to review the proposed implementation, so that, I can go ahead with implementing the enhancement.
> 
> Thanks,
> Dinesh E
> 
> 
> 
> -The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
> 


Links:
[1] - https://gerrit.openbmc-project.xyz/c/openbmc/jsnbd/+/49944

-- 
Best regards,

Igor Kononenko