Skip to main content

Minotauro

System Overview​

MinoTauro was a heterogeneous cluster with 2 configurations until recently, but it has undergone changes and one of its configurations has been deprecated (removing all the nodes using the M2090 GPU cards). This is the actual configuration:

  • 38 bullx R421-E4 servers, each server with:
    • 2 Intel Xeon E5-2630 v3 (Haswell) 8-core processors, (each core at 2.4 GHz,and with 20 MB L3 cache)
    • 2 K80 NVIDIA GPU Cards
    • 128 GB of Main memory, distributed in 8 DIMMs of 16 GB -- DDR4 @ 2133 MHz - ECC SDRAM --
    • Peak Performance: 250.94 TFlops
    • 120 GB SSD (Solid State Disk) as local storage
    • 1 PCIe 3.0 x8 8GT/s, Mellanox ConnectX®-3FDR 56 Gbit
    • 4 Gigabit Ethernet ports.

The operating system is RedHat Linux 6.7.

Connecting to MinoTauro​

The first thing you should know is your username and password. Once you have a login and its associated password you can get into the cluster through the following login node:

  • mt1.bsc.es

You must use Secure Shell (ssh) tools to login into or transfer files into the cluster. We do not accept incoming connections from protocols like telnet, ftp, rlogin, rcp, or rsh commands. Once you have logged into the cluster you cannot make outgoing connections for security reasons.

To get more information about the supported secure shell version and how to get ssh for your system (including windows systems) see Appendices.

Once connected to the machine, you will be presented with a UNIX shell prompt and you will normally be in your home ($HOME) directory. If you are new to UNIX, you will need to learn the basics before doing anything useful.

If you have used MinoTauro before, it's possible you will see a message similar to:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.

This message is displayed because the public SSH keys have changed, but the name of the logins has not. To solve this issue please execute (in your local machine):

ssh-keygen -f ~/.ssh/known_hosts -R 84.88.53.228 
ssh-keygen -f ~/.ssh/known_hosts -R 84.88.53.229
ssh-keygen -f ~/.ssh/known_hosts -R mt1.bsc.es 
ssh-keygen -f ~/.ssh/known_hosts -R mt1
ssh-keygen -f ~/.ssh/known_hosts -R mt2.bsc.es
ssh-keygen -f ~/.ssh/known_hosts -R mt2