[OOD-users] evaluating ood and noVNC
efranz at osc.edu
Thu Nov 8 16:02:56 EST 2018
> Our compute nodes have turbovnc-2.2-20180927.x86_64 and
> python-websockify-0.6.0-2.el7.noarch installed and are similarly
> provisioned with RAM/cores/os.
We are using websockify 0.8.0+. We do have a websockify rpm if you want to use that: https://yum.osc.edu/ondemand/1.3/compute/el7/x86_64/. Also we are using an older version of turbovnc (2.0.91, 2.1.1, and now 2.1.90).
I doubt that the version differences would introduce the problem you are seeing though.
Eric Franz, Senior Web & Interface App Engineer
Ohio Supercomputer Center
An Ohio Technology Consortium (OH-TECH) Member
1224 Kinnear Road
Columbus, OH 43212
email: efranz at osc.edu
On 11/2/18, 4:59 PM, "OOD-users on behalf of John-Paul Robinson via OOD-users" <ood-users-bounces at lists.osc.edu on behalf of ood-users at lists.osc.edu> wrote:
We've been evaluating ood and now have a beta instance deployed on our
cluster. Over all, the application works great. It is exactly what
we want to see as a modernization of the HPC user experience.
Our tests with noVNC are seeing a lot of promise but we've noticed some
rendering/responsiveness issues with this interface. In particular,
sometimes we see a lack of updates to text typed in a terminal on the
VNC desktop and no updates visible until we click on a desktop outside
the terminal. We are also seeing issues with Matlab rendering updates
(matlab has been problematic in the past even with traditional vnc
clients, so i'm just putting this one out there). It seems to me that
the problems are due to a refresh-rate/detection issue between the X
server and the VNC server agent. If I connect with a traditional VNC
client to the hpc desktop, I see the same update issues as i'm seeing on
the noVNC client side. We are testing with xfce.
Thanks for all the work on this great product,
OOD-users mailing list
OOD-users at lists.osc.edu
More information about the OOD-users