[torqueusers] VNC service on cluster nodes with torque

Paul McIntosh paul.mcintosh at monash.edu
Sun Jun 23 16:44:10 MDT 2013


resending as this didn't seem to come through...

----- Original Message -----
> From: "Paul McIntosh" <paul.mcintosh at monash.edu>
> To: torqueusers at supercluster.org
> Sent: Tuesday, 18 June, 2013 10:02:28 PM
> Subject: [torqueusers] VNC service on cluster nodes with torque
> 
> Hi Chris,
> 
> Gareth pointed me to this thread - you might be interested in the
> open source project we have in current development
> https://confluence-vre.its.monash.edu.au/display/CVL/Easy+Login
> 
> Currently being used on our HPC system
> https://www.massive.org.au/userguide/cluster-instructions/massive-launcher
> 
> If you want to give it a whirl drop me an email paul dot mcintosh @
> monash do edu
> 
> Cheers,
> 
> Paul
> 
> > -----Original Message-----
> > From: Chris Hunter [mailto:chris.hunter at yale.edu]
> > Sent: Saturday, 15 June 2013 2:43 AM
> > To: torqueusers at supercluster.org
> > Subject: [torqueusers] VNC service on cluster nodes with torque
> > 
> > I am working on a method to provide easy remote VNC access to
> > cluster
> > nodes using regular torque "qsub" job submission. The objective is
> > to
> > allow cluster users to run GUI based software (eg. matlab, visit,
> > paraview, etc.) on cluster nodes via remote access. We have run
> > into
> > several practical difficulties not directly related torque.
> > 
> > For example, users submit jobs on a public-facing server but the
> > VNC
> > service starts on a cluster node on a private network. We need to
> > create a network path between the remote user and the cluster node,
> > using the public-facing server as the intermediate bridge. We have
> > found no good method to automate this as part of the job
> > submission. We
> > tested various port forwarding schemes that require manual
> > intervention
> > but nothing that is fully automated.
> > 
> > Another issue is VNC traffic is unencrypted. We would like to
> > encrypt
> > traffic (ie. using a SSH tunnel) to the remote user. However,
> > installing and configuring the required VNC & SSH client software
> > on a
> > remote PC is a support nightmare (eg. supporting unmanaged windows,
> > mac
> > & linux desktop & laptops).
> > 
> > Does any manage a cluster where users submit jobs to use VNC ?
> > Are you able to fully automate the VNC setup and connection ?
> > Any advice on avoiding common pitfalls ? Is a fully automated VNC
> > service unrealistic ?
> > 
> > regards,
> > chris hunter
> > chris.hunter at yale.edu
> > 
> 
> 
> --
> Dr Paul McIntosh
>   Senior HPC Consultant, Technical Lead,
>     Multi-modal Australian ScienceS Imaging and Visualisation
>     Environment (www.massive.org.au)
>        Monash University, Ph: 9902 0439 Mob: 0434 524935
> 

-- 
Dr Paul McIntosh
  Senior HPC Consultant, Technical Lead,
    Multi-modal Australian ScienceS Imaging and Visualisation Environment (www.massive.org.au)
       Monash University, Ph: 9902 0439 Mob: 0434 524935


More information about the torqueusers mailing list