Changes between Version 5 and Version 6 of vnc3d/manual

Timestamp:

05/19/16 16:29:45 (8 years ago)

Author:

Herwig Zilken

Comment:

--

vnc3d/manual

@@ -81 +81 @@
 ssh <USERID>@jureca.fz-juelich.de
 }}}
+sbatch is used to start a job script. In this case the job script should start the vnc server and could look like:
+{{{
+#!/bin/bash
 
-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:
-{{{ #!sh
-# request allocation and spawn VNC server on visualization node
-salloc -N 1 -p vis --gres=mem512,gpu:1 --start-xserver --time=1:00:00
-srun -n 1 --cpu_bind=none --gres=gpu:1 vncserver -fg -profile vis -geometry 1920x1080 
-
-...
-Desktop 'TurboVNC: <NODE>:<DISPLAY> (profile <PROFILE>)'
- started on display <NODE>:<DISPLAY> (<NODE>:<DISPLAY>)
-...
+#SBATCH --job-name=vnc
+#SBATCH --nodes=1
+#SBATCH --ntasks-per-node=24
+#SBATCH --gres=gpu:2
+#SBATCH --partition=vis
+#SBATCH --time=24:00:00
+#SBATCH --mem=512000
+vncserver -fg -profile vis -geometry 1920x1080
 }}}
 
-salloc/srun options
-* -N 1            -> Set number of requested nodes.
-* -p vis          -> Limit request to nodes from the visualization partition.
-* --gres=mem512   -> Set the size of main memory per node (mem512 or mem1024).
-* --gres=gpu:2    -> Set the number of requested GPUs in the range of 0-2.
-* --start-xserver -> Start an Xserver for usage with VirtualGL. 
-* --time=1:00:00  -> Set the default wallclock time to 1 hour (the maximum is 24 hours).
-* Please check 'salloc --help' and 'srun --help' for more details.
+Once you have created this batch script, you can start it by
 
+{{{ #!sh
+sbatch --start-xserver ''name_of_jobscript''
+}}}
+
+The option  '--start-xserver' tells sbatch that it should start X-server on the allocated nodes, which is important if you want to do hardware rendering on a GPU.
+Once the job ist started, you have to find out the name of the node on which the job running and the number of the vnc display. To do this you have to look at the output file generated by slurm, e.g.:
+
+{{{ #!sh
+cat slurm-2063855.out
+
+Desktop 'TurboVNC: jrc1386:2 (profile vis)' started on display jrc1386:2 (jrc1386:2)
+
+Starting applications specified in /etc/turbovnc/xstartup.turbovnc
+Log file is /homeb/.../your_user_name/.vnc/jrc1386:2.log
+}}}
+
+In this case the node is '''jrc1386''' and the display number is '''2'''. This information is needed to set up the ssh tunnel (see step 3).
 
 === 3. Tunnel VNC traffic to workstation
@@ -123 +129 @@
 {{{ #!ShellExample
 ssh -N -L <5900+DISPLAY>:<NODE>:<5900+DISPLAY> <USERID>@jureca.fz-juelich.de
-# example: ssh -N -L 5902:jrc1327:5902 jjuser@jureca.fz-juelich.de
+# example: ssh -N -L 5902:jrc1386:5902 jjuser@jureca.fz-juelich.de
 }}}