Remote compute facilities #

There are a number of computers and clusters available for remote use. This page describes them, how they should be used and how to connect. If you have any questions, please contact us.

Contents #

• cafe
  • Tunnelling via cafe
  • Using cafe as a Jump Host
• CPU nodes
• GPU nodes
• Considerate use
• ARCHIE-WeSt

General guidelines #

• These computers are generally shared between lots of students and staff. Please use them considerately.
• While you can generally run third party software from your home or scratch directory, please make sure that this complies with university IT policy (in particular, software should be secure, up to date, and licensed for your use case (preferably FOSS)).
• Any services you run during development should listen only on interface 127.0.0.1 (localhost).
• All machines are firewalled from the Internet and must be accessed via the campus network, the VPN, or a tunnel via cafe.
• Cafe should only be used for lightweight tasks such as tunnelling to other machines and managing files in your home directory.
• Any of the remote compute machines (CPU/GPU nodes, cafe) may be rebooted by the CIS IT Support team at any time, in order to carry out essential maintenance and regular security updates. While we try to do this when there are no active users, security and operational concerns must take precedence. Consequently, all tasks (especially long-running jobs) on our infrastructure should be reproducible, resumable and should save their results regularly (i.e. you should design your tasks/code such that an unscheduled reboot should not cause you to lose valuable data).

Cafe #

Cafe (cafe.cis.strath.ac.uk) is our main SSH host, sometimes called a "login node" in other environments. It runs on a shared Faculty of Science blade in the university data centre.

You can ssh to cafe using your university DS credentials, e.g. ssh xxy12345@cafe.cis.strath.ac.uk.

You can access the ssh command from your terminal. Windows users should use Windows Terminal, which comes bundled with recent versions of Windows 10 and all versions of Windows 11.

As cafe runs in a fairly constrained virtual machine on a shared faculty server, you must not run heavy-weight compute tasks on cafe as this can severely disrupt access for other staff and students. In particular, this includes machine learning and deep learning workloads. If you're unsure about where to run a certain task, please contact us.

Tunnelling via cafe #

You can use cafe to tunnel to other servers, e.g. if you are running a development web server (such as Flask, or NodeJS) on cpunode1 on port 12888, you can establish a tunnel as follows ...

ssh -L 12888:cpunode1.cis.strath.ac.uk:12888 cafe.cis.strath.ac.uk

... which will allow you to access your cpunode1 service from your local machine by going to http://localhost:12888

A common use case is to be able to access a devweb database off-campus (using tools like DBeaver, mysql CLI, psql CLI or from an app being developed on your personal computer). The devweb database pages provide port mapping examples for each database server. The following list shows the ports of common services running in the department (assume all hosts are on the .cis.strath.ac.uk domain):

For example, to access MySQL while off campus you could run:

ssh -L 3306:devweb2024.cis.strath.ac.uk:3306 cafe.cis.strath.ac.uk

You'd then be able to connect your local MySQL client or app to localhost:3306, which would be tunnelled to devweb2024 via cafe.

Using cafe as a Jump Host #

You can also use cafe as a jump host (also known as a bastion host), for example to connect SSH on cpunode1 going via cafe, you could run:

ssh -J xxy12345@cafe.cis.strath.ac.uk xxy12345@cpunode1.cis.strath.ac.uk

This would open SSH connection to cpunode1 (automatically tunnelled via cafe).

CPU nodes #

Formerly known as Guacamole Linux Labs

We have a number of computers dedicated to CPU-bound loads and remote GUI access. These are generally more suitable than cafe for heavier workloads, although we do ask you to be considerate of other users who might be using them.

You can access the CPU nodes graphically by visiting Guacamole and choosing Linux Labs. This will connect you to an available CPU node.

Please note that when you disconnect (or if your connection is unstable and drops too many packets), your login session is destroyed. We recommend using the remote graphical login facility only from a stable network.

You can also connect via SSH, to any of the CPU nodes listed below. You'll need to connect via either the campus network, the VPN or by using cafe as a jump host.

CPU node list and specification #

GPU nodes #

In addition to the CPU nodes, we operate a number of GPU nodes - higher performance workstations with GPUs suitable for moderate ML/DL workloads (where other resources like Wee Archie or ARCHIE WeSt are unsuitable). Graphical access is available via Guacamole; if granted access, you will see a new connection labelled GPU Nodes.

GPU node list and specification #

Access to these machines is by arrangement only and is offered to students who require this for their project work. If you think that this facility would be useful, please contact us. Please note that these resources are very limited so access is granted on first-come-first-served basis, in cases where we determine that this is the most appropriate place to run your workload.

Considerate use #

Cafe should be used for login, tunnelling and light tasks (like file management and editing) only.

Our CPU and GPU nodes can be used for more intensive workloads, but please be considerate of other users who may be using these machines at the same time. In general, heavy-weight, experimental and intensive programs:

• must be cpu niced to level +19 (e.g. nice +19)
• must be io niced to "idle" (e.g. ionice -c 3)

You can nice a process by using the nice command and ionice command (or renice command if it is already running). For example, to nice a program called myresearch you would run nice +19 ionice -c 3 myresearch

Your home directory resides on an NFS server on a network which is shared across a large number of machines; it is not optimised for high throughput experimental IO. Therefore, programs should not write large amounts of data to your home directory. If there is a need to write large amounts of data during your experiment then please create yourself a directory (using your userid as the name) in /scratch and write your experimental data there. /scratch resides on fast, local SSD disks but is not designed for long-term persistent storage (it's not backed up and is liable to be destroyed during regular server maintenance). As such, you must regularly back-up any non-reproducible data to your home directory.

The department reserves the right to stop your experiment if it is impairing the use of the computer or the network, but we will endeavour to let you know when this happens and suggest alternative computing arrangements where possible.

ARCHIE-WeSt #

The university operates a regional supercomputer which is available to academia and industry in the West of Scotland. The machine offers extremely high compute performance and parallelisation and is suitable for the most intensive tasks. You can read more about it at archie-west.ac.uk. Please note that there is usually a cost for accessing ARCHIE. All ARCHIE access enquiries should go directly to the ARCHIE team; students should do this via their project supervisor.