search

OSC / ondemand

Supercomputing. Seamlessly. Open, Interactive HPC Via the Web
https://openondemand.org/
MIT License
275 stars 102 forks source link

noVNC is inaccessible #675

Open johrstrom opened 3 years ago

johrstrom commented 3 years ago

noVNC is basically completely inaccessible because it's a <canvas> element with no text alternative.

It would be a huge undertaking to fix it or port to a different solution. So this ticket is likely just going to be a discussion forum for the team & community to chime in on what alternatives we could take (if any).

┆Issue is synchronized with this Asana task by Unito

johrstrom commented 2 years ago

Native VNC clients should be used if they're accessible. This means that we should probably update the native tabs to provide a link with the correct URL. We provide osc:// for our osc VNC viewer, but I wonder if say Windows/Mac will open tigerVNC when vnc:// URLs are clicked.

johrstrom commented 2 years ago

If they have the network connectivity to a compute node.

The OSC VNC client was a bit before my time, but we may have to dig into how it worked because we do not now have connectivity to compute nodes so I don't believe it would even work now unless we proxy the tcp connection through apache...

johrstrom commented 2 years ago

a quick read of the osc-connect docs indicates it uses an ssh tunnel so I suppose the current panels are actually as correct as they can be.

https://github.com/OSC/osc-connect/

johrstrom commented 2 years ago

Apparently VNC clients like TigerVNC or REAL VNC are also inaccessible. Another option to investigate is X11 forwarding.