VNC: Difference between revisions

65 bytes removed ,  3 months ago
copy editing
(Marked this version for translation)
(copy editing)
Line 67: Line 67:
Now you need a VNC server to connect to.  This can be either a persistent vncserver running on dedicated VDI nodes which are part of [[Graham]], or a temporary vncserver you start on a cluster compute node.  VNC is not a heavyweight server, so you can certainly run lightweight sessions on cluster login nodes.
Now you need a VNC server to connect to.  This can be either a persistent vncserver running on dedicated VDI nodes which are part of [[Graham]], or a temporary vncserver you start on a cluster compute node.  VNC is not a heavyweight server, so you can certainly run lightweight sessions on cluster login nodes.


== VDI nodes == <!--T:30-->
== Virtual Desktop Infrastructure (VDI) nodes == <!--T:30-->


<!--T:32-->
<!--T:32-->
Line 73: Line 73:


<!--T:34-->
<!--T:34-->
Graham has dedicated VDI nodes collectively known as gra-vdi.  These nodes provide a full graphical desktop, accelerated OpenGL, and shared access to Graham's <code>/home, /project,</code> and <code>/scratch</code> filesystems.
Graham has dedicated VDI nodes collectively known as gra-vdi.  These nodes provide a full graphical desktop, accelerated OpenGL, and shared access to Graham's <code>/home, /project,</code> and <code>/scratch</code> filesystems.


<!--T:36-->
<!--T:36-->
Line 79: Line 79:


<!--T:179-->
<!--T:179-->
As an aside, to connect to either machine directly you could instead enter <code>VNC server: '''gra-vdi3.sharcnet.ca'''</code> or enter <code>VNC server: '''gra-vdi4.sharcnet.ca'''</code>.  This could be useful if either server is under a heavy load and your planning to run some intensive calculations or you want to use your local $SCRATCH directory on either server (which points to /local/tmp/$USER on each machine).  This is notably different than the clusters where $SCRATCH points to the shared directory /scratch/$USER location on all compute and login nodes.  Similar to the clusters however any data left under $SCRATCH on gra-vdi will eventually be deleted since the disc space is limited as it is fast.
You also have the option to connect to either machine directly by entering <code>VNC server: '''gra-vdi3.sharcnet.ca'''</code> or enter <code>VNC server: '''gra-vdi4.sharcnet.ca'''</code>.  You might choose to do this if you find one machine is responding poorly due to heavy load, or if you want to use your local $SCRATCH directory on either server.  $SCRATCH points to /local/tmp/$USER on each machine.  This is notably different than the clusters where $SCRATCH points to the shared directory /scratch/$USER location on all compute and login nodes.  Similar to the clusters, however, any data left under $SCRATCH on gra-vdi will eventually be deleted since the disc space is limited.


<!--T:38-->
<!--T:38-->
As with regular login nodes, the VDI nodes are a shared resource and not intended for doing batch computation (that is what the compute nodes are for) so please only use them for graphics-related tasks.  For example graphical pre-processing such as mesh generation, graphical post-processing such as visualization, or graphical integrated development environments.
As with regular login nodes, the VDI nodes are a shared resource and not intended for doing batch computation. That is what the compute nodes are for.  Please only use them for graphics-related tasks, such as mesh generation, visualization, or using an integrated development environment (IDE).


<!--T:40-->
<!--T:40-->
Bureaucrats, cc_docs_admin, cc_staff
2,879

edits