Difference between revisions of "HPC cluster 2"
Line 17: | Line 17: | ||
| gpu4 || 147.8.100.186 || 48 || A30x4 || 128 || 5.2 || `/` || NA | | gpu4 || 147.8.100.186 || 48 || A30x4 || 128 || 5.2 || `/` || NA | ||
|- | |- | ||
− | | storage1 || 147.8.100.164 || 18 || NA || 16 || 100 || exported as nfs to `/home/[username]/share` || | + | | storage1 || 147.8.100.164 || 18 || NA || 16 || 100 || exported as nfs to `/home/[username]/share` || NA |
|} | |} | ||
Revision as of 16:27, 20 April 2022
The department of Diagnostic Radiology manages another five servers colloquially referred to as the "GPU cluster 2".
They were set up and handed over in April 2022. The rack is physically located at the laboratory building, LG3/F.
Contents
Hardware Specifications
The servers are typically called nodes. There are four GPU computing nodes and one windows storage node.
Name | Public IP address | Physical CPU cores | GPU | RAM(GB) | Storage (TB) | Storage mount point | URL |
---|---|---|---|---|---|---|---|
gpu1 | 147.8.100.183 | 48 | A30x4 | 128 | 5.2 | / |
NA |
gpu2 | 147.8.100.184 | 48 | A30x4 | 128 | 5.2 | / |
NA |
gpu3 | 147.8.100.185 | 48 | A30x4 | 128 | 5.2 | / |
NA |
gpu4 | 147.8.100.186 | 48 | A30x4 | 128 | 5.2 | / |
NA |
storage1 | 147.8.100.164 | 18 | NA | 16 | 100 | exported as nfs to /home/[username]/share |
NA |
Realtime performance and usage metrics can be found at HPC Diagnostics and Statistics
Usage
Users are currently expected to use the GPU cluster in the following ways:
- Access to this wiki
- Access to a GitLab account for code sharing and collaboration
- Shell access to the compute nodes
- Users get their own user-specific home folder.
A few introductory guides are available to help users. Other software may be installed upon request, but users should note they can manually install any software in their own home directory without needing admin privileges.
- To use the shell access features of the GPU cluster, users need to get a server account.
- All users must be on the HKU network / VPN to access anything.
Choosing a server
Refer to the specs table for IP address information.
storage1
is not intended for direct shell access, so password login for non-admins is disabled. The storage node transparently makes its storage capacity available to all nodes as the /home/[username]/share
directory.
For running code and scripts
Choose any of the 4 gpu servers. Optionally check the local resource usage with command top
, ps
or nvidia-smi
.
For file transfer/storage
It doesn't matter which server you choose, since the user home folder (/home/[username]/share
) is a nfs mounted from the storage server. So it is suggested all of your files or folders should be saved in this directory. To evaluate available storage see the df
or du
commands.
Security
Users may have several sets of login credentials:
- One for the Linux shell
- One for this wiki
- One for their Gitlab
All the passwords used in the above are stored in a salted hash format. This means, in the event of a data breach, user passwords won't be compromised. It also means they are not retrievable, not even by admins. Password resets are (ideally) handled by automated email.
- Please use a strong password and protect it.
- Non-anonymous patient data should be stored in encrypted format.
Ports
Users may run servers listening on ports, e.g. a VNC/X11 server or Jupyter notebook. Such connections should use an SSH tunnel to ensure security and pass the firewall.
Connections to websites on hpc.radiology.hku.hk should use SSL/TLS (i.e. https in the browser). This means traffic to the (proxy) server is encrypted.