Changes between Version 17 and Version 18 of vnc3d/manual


Ignore:
Timestamp:
06/23/20 11:03:01 (4 years ago)
Author:
Helmut Schumacher
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • vnc3d/manual

    v17 v18  
    22[[PageOutline]]
    33
    4 === Using VNC requires three general steps.
    5 1. '''Prepare your account''' on a JURECAVIS node.
    6 2. '''Start a VNC server''' on a JURECA node.
     4=== Using VNC requires four general steps.
     51. '''Prepare your account''' on a JUWELSVIS node.
     62. '''Start a VNC server''' on a JUWELSVIS node.
    773. '''Tunnel VNC traffic''' to your workstation.
    884. '''Start a VNC viewer''' on your workstation and connect to the VNC server.
    … …  
    1111=== 1. Prepare your account ...
    1212Before you use VNC '''for the first time''' you have to prepare your account:
    13 * login to a JURECAVIS node
     13* login to a JUWELSVIS node
    1414* create the directory ~/.vnc
    1515* define VNC password
    1616{{{ #!sh
    17 ssh <USERID>@jurecavis.fz-juelich.de
     17ssh <USERID>@juwelsvis.fz-juelich.de
    1818mkdir ~/.vnc
    1919vncpasswd
    … …  
    2222\\
    2323=== 2. Start VNC server ...
    24 The following steps are necessary to start a VNC server on JURECA. \\
     24The following steps are necessary to start a VNC server on JUWELS. \\
    2525Please notice that you have two general options:
    2626
    … …  
    3737In case the VNC server could successfully be started (details in 2a,b), you will find a simular line in the output:
    3838{{{ #!sh
    39 Desktop 'TurboVNC: jurecavis02.fz-juelich.de:1 (profile <PROFILE>)' started on display jrc1384:1 (jurecavis02.fz-juelich.de:1)
     39Desktop 'TurboVNC: juwelsvis02.fz-juelich.de:1 (profile <PROFILE>)' started on display juwelsvis02.ib.juwels.fzj.de:1 (juwelsvis02.fz-juelich.de:1)
    4040}}}
    4141
    4242Two important informations have to be taken from this output \\
    4343to setup the required SSH tunnel (with the correct network port) to the allocated node in step 2:
    44 1. The allocated node is '''jurecavis02'''
     441. The allocated node is '''juwelsvis02'''
    45452. The number of the VNC display is ''':1'''
    4646
    … …  
    5151* To ensure VNC sessions are not forgotten and keep on running forever, they will be '''killed after 24 hours ''' (WITHOUT warning).
    5252* Logout from your VNC session, after you have finished your work. This will save resources and close the VNC server. \\
    53 * If you start the VNC server the first time, you will be asked for a password (which is stored in ~/.vnc/passwd). \\
    54   You will be asked for this password by the VNC viewer, when you connect to the VNC server. \\
     53* If you start the VNC server the first time and you did not call vncpasswd in step 1, you will be asked for a password (which is stored in ~/.vnc/passwd). \\
     54  You will be asked for this password by the VNC Viewer each time, when you connect to the VNC server. \\
    5555  To reset the password just delete the file ~/.vnc/passwd.
    5656
    5757==== a. ... on an interactive vis login node
    58 Open a SSH shell on an interactive vis login node (jurecavis.fz-juelich.de):
     58Open a SSH shell on an interactive vis login node (juwelsvis.fz-juelich.de):
    5959{{{ #!sh
    60 ssh <USERID>@jurecavis.fz-juelich.de
     60ssh <USERID>@juwelsvis.fz-juelich.de
    6161}}}
    6262
    63 Start your own VNC server on jurecavis.
     63Start your VNC server on juwelsvis.
    6464Usefull vncserver parameters are:
    6565* -profile        -> choose a profile (eg. -profile vis)
    … …  
    7676
    7777==== b. ... on a dedicated vis node
    78 Open an SSH shell on any login node of JURECA the usual way:
     78Open an SSH shell on any login node of JUWELS the usual way:
    7979
    8080{{{ #!sh
    81 ssh <USERID>@jureca.fz-juelich.de
     81ssh <USERID>@juwels.fz-juelich.de
    8282}}}
    8383sbatch is used to start a job script. In this case the job script should start the vnc server and could look like:
    … …  
    102102
    103103The option  '--start-xserver' tells sbatch that it should start an X-server on the allocated node, which is important if you want to do hardware rendering on a GPU.\\
    104 Once the job ist started, you have to find out the name of the node on which the job is running and the number of the vnc display.\\
     104Once the job is started, you have to find out the name of the node on which the job is running and the number of the vnc display.\\
    105105To do this you have to look at the output file generated by slurm, e.g.:
    106106
    … …  
    117117
    118118=== 3. Tunnel VNC traffic to workstation
    119 Now you have to open an SSH tunnel from your workstation to node on which your VNC server is running. \\
    120 The steps to be done depend strongly on your operating system and your setup.
     119Now you have to open an SSH tunnel from your workstation to the node on which your VNC server is running. \\
     120The necessary steps strongly depend on your operating system and your setup.
    121121
    122122'''Linux:'''\\
    123 If your operating system is Linux use for interactive nodes (NODE is most likely jurecavis01... or jurecavis02...):
     123If your operating system is Linux use for interactive nodes (NODE is juwelsvis00... up to juwelsvis03...):
    124124{{{ #!ShellExample
    125125ssh -N -L <5900+DISPLAY>:<NODE>:<5900+DISPLAY> <USERID>@<NODE>.fz-juelich.de
    126 # example: ssh -N -L 5907:jurecavis01:5907 jjuser@jurecavis01.fz-juelich.de
     126# example: ssh -N -L 5907:juwelsvis01:5907 jjuser@juwelsvis01.fz-juelich.de
    127127}}}
    128128
    129129and for dedicated nodes:
    130130{{{ #!ShellExample
    131 ssh -N -L <5900+DISPLAY>:<NODE>:<5900+DISPLAY> <USERID>@jureca.fz-juelich.de
    132 # example: ssh -N -L 5902:jrc1386:5902 jjuser@jureca.fz-juelich.de
     131ssh -N -L <5900+DISPLAY>:<NODE>:<5900+DISPLAY> <USERID>@juwels.fz-juelich.de
     132# example: ssh -N -L 5902:juwelsvis01:5902 jjuser@juwels.fz-juelich.de
    133133}}}
    134134
    … …  
    139139Here a short overview on how-to setup a tunnel with [http://www.putty.org/ PuTTY] is given.
    140140
    141 It is assumed that PuTTY is already configured in a way that a general ssh connection to JURECA is possible. \\
     141It is assumed that PuTTY is already configured in a way that a general ssh connection to JUWELS is possible. \\
    142142That means that host name, user name and the private ssh key (using PuTTY's Pageant) are correctly set.
    143143
    144 To establish the ssh tunnel, enter the "SSH-->tunnels" tab in the PuTTY configuration window. \\
    145 You have to enter the source port (eg. <5900+DISPLAY> = 5902 if DISPLAY=2) and the destination (in this case localhost:<5900+DISPLAY>) and than press add. \\
     144You already made a first connection to JUWELS using PUTTY and started vncserver.
     145
     146To establish the ssh tunnel start a second PUTTY and enter the "SSH-->tunnels" tab in the PuTTY configuration window '''before connecting to JUWELS'''. \\
     147You have to enter the source port (eg. <5900+DISPLAY> = 5902 if DISPLAY=2) and the destination (in this case juwelsvis01.fz-juelich.de:<5900+DISPLAY>) and than press add. \\
    146148After pressing add, the tunnel should appear in the list of forwarded ports and you can establish the tunnel by pressing the open button:
    147149
    … …  
    175177vncviewer localhost:2
    176178}}}
    177 After typing in your VNC password (defined in step 1), you will have access to the remote graphical desktop running on the visualization node of JURECA.
     179After typing in your VNC password (defined in step 1), you will have access to the remote graphical desktop running on the visualization node of JUWELS.
    178180
    179181