Changes between Version 34 and Version 35 of vnc3d

Timestamp:

04/05/16 10:31:19 (8 years ago)

Author:

Jens Henrik Goebbert

Comment:

--

vnc3d

@@ -62 +62 @@
 (attention: __without__ VirtualGL software, rendering using the CPU instead of the GPU must be used (if available), which is much slower).
 
-
-The following steps are necessary to start a VNC session for remote rendering with !VisIt on JURECA. \\
-Please notice that the VNC server is only available on vis-nodes!
-
-=== 1. Start VNC server on a vis node
-Open an ssh shell on any login node of JURECA the usual way.\\
-
-salloc is used to request an allocation. When the job is started, a shell (or other program specified on the command line) is started on the submission host (login node). From the shell srun can be used to interactively spawn parallel applications. The allocation is released when the user exits the shell.
+==== ok, what do I have to do?
+Using VNC requires two general steps.
+1. '''Start a VNC server''' on a JURECA node.
+2. '''Tunnel VNC traffic''' to your workstation.
+
+\\
+=== 1. Start VNC server ...
+The following steps are necessary to start a VNC server on JURECA. \\
+Please notice that you have two general options:
+
+You can start the VNC server ...
+* ... on an '''interactive vis login node'''
+ * + no batch system == instant access
+ * -- system is shared with other users
+* ... on a '''dedicated vis node'''
+ * + system is not shared (exclusive use)
+ * -- access through batch system
+
+In case the VNC server could successfully be started (details in 1a,b), you will find a simular line in the output:
+{{{ #!sh
+Desktop 'TurboVNC: jrc1391.zam.kfa-juelich.de:1 (<USERID>)' started on display jrc1391.fz-juelich.de:1
+}}}
+
+Two important informations have to be taken from this output \\
+to setup the required SSH tunnel (with the correct network port) to the allocated node in step 2:
+1. The allocated node is '''jrc1391'''
+2. The number of the VNC display is ''':1'''
+
+It is very important to know that the network port of the VNC server depends on this display number. \\
+The actual port number is 5900+<VNC display>, therefore port '''5901''' must be tunneled in this case.
+
+Important notes:
+* To ensure VNC sessions are not forgotten and keep on running forever, they will be '''killed after 24 hours ''' (WITHOUT warning).
+* Logout from your VNC session, after you have finished your work. This will save resources and close the VNC server. \\
+* If you start the VNC server the first time, you will be asked for a password (which is stored in ~/.vnc/passwd). \\
+  You will be asked for this password by the VNC viewer, when you connect to the VNC server. \\
+  To reset the password just delete the file ~/.vnc/passwd.
+
+==== a. ... on an interactive vis login node
+Open a SSH shell on an interactive vis login node (jurecavis.fz-juelich.de):
+{{{ #!sh
+ssh <USERID>@jurecavis.fz-juelich.de
+}}}
+
+Start your own VNC server on jurecavis.
+Usefull vncserver parameters are:
+* -profile        -> choose a profile (eg. -profile vis)
+* -geometry       -> set the screen size (eg. -geometry 1920x1080)
+{{{ #!sh
+vncserver
+}}}
+
+==== b. ... on a dedicated vis node
+Open an SSH shell on any login node of JURECA the usual way:
+
+{{{ #!sh
+ssh <USERID>@jureca.fz-juelich.de
+}}}
+
+salloc is used to request an allocation.\\
+When the job is started, a shell (or other program specified on the command line) is started on the submission host (login node). \\
+From the shell srun can be used to interactively spawn parallel applications. \\
+The allocation is released when the user exits the shell.
 
 To allocate a vis node with 512 GByte main memory for one hour, use:
@@ -77 +132 @@
 srun -n 1 --cpu_bind=none --gres=gpu:1 vncserver -fg -profile vis -geometry 1920x1080 
 }}}
+
 salloc/srun options
 * -N 1            -> Set number of requested nodes.
@@ -86 +142 @@
 * Please check 'salloc --help' and 'srun --help' for more details.
 
-vncserver options
-* -fg             -> start VNC server in the foreground (ensure the end of job-script is not reached, as this will stop the job)
-* -profile        -> choose a profile (eg. default, vis)
-* -geometry       -> set the screen size (optional)
-
-In case the VNC server could successfully be started, you will get an output like:
-{{{ #!sh
-Desktop 'TurboVNC: jrc1384.zam.kfa-juelich.de:1 (<USERID>)' started on display jurecavis01.fz-juelich.de:1
-}}}
-
-As you have to setup an ssh tunnel (with the correct network port) to the allocated node in step 2, \\
-two important informations have to be taken from this output:
-1. The allocated node is '''jrc1391'''
-1. The number of the VNC display is ''':1'''
-
-It is very important to know that the network port of the VNC server depends on this display number. \\
-The actual port number is 5900+<VNC display>, therefore port '''5901''' must be tunneled in this case.
 
 === 2. Tunnel VNC traffic to workstation
-Now you have to open an ssh tunnel from your workstation to this node. \\
+Now you have to open an SSH tunnel from your workstation to node on which your VNC server is running. \\
 The steps to be done depend strongly on your operating system and your setup.
 
@@ -148 +187 @@
 
 # load ParaView dependency
-module load intel-para/2015.07
+module load intel-para
 
 # load ParaView
-module load ParaView/4.3.1
+module load ParaView
 }}}