Commit dc868ae9 authored by Lukáš Krupčík's avatar Lukáš Krupčík
Browse files

version 0.53

parent f1cf74e0
Pipeline #1049 failed with stage
in 11 seconds
......@@ -29,6 +29,7 @@ Pro svou práci si naklonujete Gitem repozitář do svého pracovního adresář
|0.47|11m7s|přidání filtrů pro opravu a nahrazení tabulek, vylepšení filtrace, ...|
|0.51|16m37s|export do pdf, export do epub, filtry, ...|
|0.52|16m37s|oprava exportu do pdf, nový filtr pro poslední opravu formátování a chyb, ...|
|0.53|17m37s|oprava exportu do pdf a epub|
> * interní a externí odkazy
Outgoing connections
Connection restrictions
Outgoing connections, from Anselm Cluster login nodes to the outside
world, are restricted to following ports:
Please use **ssh port forwarding** and proxy servers to connect from
Anselm to all other remote ports.
Outgoing connections, from Anselm Cluster compute nodes are restricted
to the internal network. Direct connections form compute nodes to
outside world are cut.
Port forwarding
### Port forwarding from login nodes
Port forwarding allows an application running on Anselm to connect to
arbitrary remote host and port.
It works by tunneling the connection from Anselm back to users
workstation and forwarding from the workstation to the remote host.
Pick some unused port on Anselm login node  (for example 6000) and
establish the port forwarding:
local $ ssh -R
In this example, we establish port forwarding between port 6000 on
Anselm and  port 1234 on the By accessing
localhost:6000 on Anselm, an application will see response of The traffic will run via users local workstation.
Port forwarding may be done **using PuTTY** as well. On the PuTTY
Configuration screen, load your Anselm configuration first. Then go to
Connection->SSH->Tunnels to set up the port forwarding. Click
Remote radio button. Insert 6000 to Source port textbox. Insert Click Add button, then Open.
Port forwarding may be established directly to the remote host. However,
this requires that user has ssh access to
$ ssh -L 6000:localhost:1234
Note: Port number 6000 is chosen as an example only. Pick any free port.
### Port forwarding from compute nodes
Remote port forwarding from compute nodes allows applications running on
the compute nodes to access hosts outside Anselm Cluster.
First, establish the remote port forwarding form the login node, as
Second, invoke port forwarding from the compute node to the login node.
Insert following line into your jobscript or interactive shell
$ ssh  -TN -f -L 6000:localhost:6000 login1
In this example, we assume that port forwarding from login1:6000 to has been established beforehand. By accessing
localhost:6000, an application running on a compute node will see
response of
### Using proxy servers
Port forwarding is static, each single port is mapped to a particular
port on remote host. Connection to other remote host, requires new
Applications with inbuilt proxy support, experience unlimited access to
remote hosts, via single proxy server.
To establish local proxy server on your workstation, install and run
SOCKS proxy server software. On Linux, sshd demon provides the
functionality. To establish SOCKS proxy server listening on port 1080
local $ ssh -D 1080 localhost
On Windows, install and run the free, open source [Sock
Puppet]( server.
Once the proxy server is running, establish ssh port forwarding from
Anselm to the proxy server, port 1080, exactly as [described
local $ ssh -R 6000:localhost:1080
Now, configure the applications proxy settings to **localhost:6000**.
Use port forwarding  to access the [proxy server from compute
as well .
Shell access and data transfer
Interactive Login
The Anselm cluster is accessed by SSH protocol via login nodes login1
and login2 at address The login nodes may be addressed
specifically, by prepending the login node name to the address.
Login address |Port|Protocol| Login node
----------------------- |---|---| ---------------------------------------------- |22|ssh| round-robin DNS record for login1 and login2 |22|ssh| login1 |22|ssh| login2
The authentication is by the [private
Please verify SSH fingerprints during the first logon. They are
identical on all login nodes:
29:b3:f4:64:b0:73:f5:6f:a7:85:0f:e0:0d:be:76:bf (DSA)
d4:6f:5c:18:f4:3f:70:ef:bc:fc:cc:2b:fd:13:36:b7 (RSA)
Private key (`id_rsa/id_rsa.ppk` ): `600 (-rw-------)`s authentication:
On **Linux** or **Mac**, use
local $ ssh -i /path/to/id_rsa
If you see warning message "UNPROTECTED PRIVATE KEY FILE!", use this
command to set lower permissions to private key file.
local $ chmod 600 /path/to/id_rsa
On **Windows**, use [PuTTY ssh
After logging in, you will see the command prompt:
/ | |
/ _ __ ___ ___| |_ __ ___
/ / | '_ / __|/ _ | '_ ` _
/ ____ | | | __ __/ | | | | | |
/_/ __| |_|___/___|_|_| |_| |_|
Last login: Tue Jul 9 15:57:38 2013 from
[username@login2.anselm ~]$
The environment is **not** shared between login nodes, except for
[shared filesystems](../storage-1.html#section-1).
Data Transfer
Data in and out of the system may be transferred by the
[scp]( and sftp
protocols.  (Not available yet.) In case large
volumes of data are transferred, use dedicated data mover node for increased performance.
-------------------- |---|---|- -----------------------------------------
||22|scp, sftp|
||22|scp, sftp|
||22|scp, sftp|
||22|scp, sftp|
 The authentication is by the [private
Data transfer rates up to **160MB/s** can be achieved with scp or sftp.
may be transferred in 1:50h.
To achieve 160MB/s transfer rates, the end user must be connected by 10G
line all the way to IT4Innovations and use computer with fast processor
for the transfer. Using Gigabit ethernet connection, up to 110MB/s may
be expected.  Fast cipher (aes128-ctr) should be used.
If you experience degraded data transfer performance, consult your local
network provider.
On linux or Mac, use scp or sftp client to transfer the data to Anselm:
local $ scp -i /path/to/id_rsa my-local-file
local $ scp -i /path/to/id_rsa -r my-local-dir
local $ sftp -o IdentityFile=/path/to/id_rsa
Very convenient way to transfer files in and out of the Anselm computer
is via the fuse filesystem
local $ sshfs -o IdentityFile=/path/to/id_rsa mountpoint
Using sshfs, the users Anselm home directory will be mounted on your
local computer, just like an external disk.
Learn more on ssh, scp and sshfs by reading the manpages
$ man ssh
$ man scp
$ man sshfs
On Windows, use [WinSCP
client]( to transfer
the data. The [win-sshfs
client]( provides a
way to mount the Anselm filesystems directly as an external disc.
More information about the shared file systems is available
VPN Access
Accessing IT4Innovations internal resources via VPN
**Failed to initialize connection subsystem Win 8.1 - 02-10-15 MS
Workaround can be found at
For using resources and licenses which are located at IT4Innovations
local network, it is necessary to VPN connect to this network.
We use Cisco AnyConnect Secure Mobility Client, which is supported on
the following operating systems:
- >Windows XP
- >Windows Vista
- >Windows 7
- >Windows 8
- >Linux
- >MacOS
It is impossible to connect to VPN from other operating systems.
VPN client installation
You can install VPN client from web interface after successful login
with LDAP credentials on address <>
According to the Java settings after login, the client either
automatically installs, or downloads installation file for your
operating system. It is necessary to allow start of installation tool
for automatic installation.
access](../executionaccess.jpg/@@images/4d6e7cb7-9aa7-419c-9583-6dfd92b2c015.jpeg "Execution access")
After successful installation, VPN connection will be established and
you can use available resources from IT4I network.
If your Java setting doesn't allow automatic installation, you can
download installation file and install VPN client manually.
After you click on the link, download of installation file will start.
After successful download of installation file, you have to execute this
tool with administrator's rights and install VPN client manually.
Working with VPN client
You can use graphical user interface or command line interface to run
VPN client on all supported operating systems. We suggest using GUI.
Before the first login to VPN, you have to fill
URL **** into the text field.
After you click on the Connect button, you must fill your login
After a successful login, the client will minimize to the system tray.
If everything works, you can see a lock in the Cisco tray icon.
If you right-click on this icon, you will see a context menu in which
you can control the VPN connection.
When you connect to the VPN for the first time, the client downloads the
profile and creates a new item "ANSELM" in the connection list. For
subsequent connections, it is not necessary to re-enter the URL address,
but just select the corresponding item.
Then AnyConnect automatically proceeds like in the case of first logon.
After a successful logon, you can see a green circle with a tick mark on
the lock icon.
For disconnecting, right-click on the AnyConnect client icon in the
system tray and select **VPN Disconnect**.
Compute Nodes
Nodes Configuration
Anselm is cluster of x86-64 Intel based nodes built on Bull Extreme
Computing bullx technology. The cluster contains four types of compute
###Compute Nodes Without Accelerator
180 nodes
2880 cores in total
two Intel Sandy Bridge E5-2665, 8-core, 2.4GHz processors per node
64 GB of physical memory per node
- one 500GB SATA 2,5” 7,2 krpm HDD per node
bullx B510 blade servers
###Compute Nodes With GPU Accelerator
23 nodes
368 cores in total
two Intel Sandy Bridge E5-2470, 8-core, 2.3GHz processors per node
96 GB of physical memory per node
- one 500GB SATA 2,5” 7,2 krpm HDD per node
GPU accelerator 1x NVIDIA Tesla Kepler K20 per node
bullx B515 blade servers
###Compute Nodes With MIC Accelerator
4 nodes
64 cores in total
two Intel Sandy Bridge E5-2470, 8-core, 2.3GHz processors per node
96 GB of physical memory per node
- one 500GB SATA 2,5” 7,2 krpm HDD per node
MIC accelerator 1x Intel Phi 5110P per node
bullx B515 blade servers
###Fat Compute Nodes
2 nodes
32 cores in total
2 Intel Sandy Bridge E5-2665, 8-core, 2.4GHz processors per node
512 GB of physical memory per node
- two 300GB SAS 3,5”15krpm HDD (RAID1) per node
two 100GB SLC SSD per node
bullx R423-E3 servers