Connecting to the Wildwood HPC cluster¶

Connecting to the Wildwood HPC cluster may take a slightly different form for each user, depending on how they were connecting to the old CQLS infrastructure, and where their local machine is that is ssh-ing in.

Note

Instead of using your old cqls password, you will be using your ONID password for validating your account.

The default port 22 is sufficient to connect to the Wildwood HPC. An alternatively defined port is uneccesary on the command-line.

Connecting from an on-campus location or through the VPN¶

If you are on campus or on a VPN connection to campus, you can directly connect to the Wildwood HPC cluster through ssh:

ssh hpc.cqls.oregonstate.edu

If you use PuTTY, you can set hpc.cqls.oregonstate.edu as the 'Host Name' and connect in that way.

Connecting to the VPN¶

Campus UIT has documentation to get the VPN working on Linux, MacOS, and Windows. This is the preferred way to connect to the updated CQLS infrastructure.

Note

Using the VPN with Windows WSL has known issues. We have found that enabling split tunnel connections and allow local (LAN) access can help alleviate those issues.

On Windows 11, enabling DNS tunneling using the dnsTunneling=true option in your .wslconfig file might help as well.

Accessing files¶

For large file transfers, please use hpc-files.cqls.oregonstate.edu.

In order to transfer to/from your local machine, use sftp or scp:

sftp hpc-files.cqls.oregonstate.edu

In order to transfer large files from the web to the infrastructure, use ssh:

ssh hpc-files.cqls.oregonstate.edu
wget https://....

Note

Please do not use hpc-files for processing data!

Connecting from an off-campus location (no VPN)¶

Note

These instructions previously explained how to connect through shell.cqls.oregonstate.edu, which will be deactivated

Currently, users can connect to Wildwood through a gateway machine called shell.hpc.oregonstate.edu. To continue on to Wildwood, you can then ssh hpc.cqls.oregonstate.edu from there. This two-step process can be reduced to a single step for advanced users by adding these lines to their ~/.ssh/config file on their local machine.

First, make the sockets directory:

mkdir -p ~/.ssh/sockets

Then, add these lines to ~/.ssh/config:

~/.ssh/config

Host shell
    HostName shell.hpc.oregonstate.edu
    User ONIDUSER
    ControlMaster auto
    ControlPath ~/.ssh/sockets/%r@%h-%p
    ControlPersist 600
    TCPKeepAlive no
    ServerAliveInterval 30

Host hpc
    HostName hpc.cqls.oregonstate.edu
    PubkeyAcceptedKeyTypes +ssh-rsa
    ProxyJump shell
    ControlMaster auto
    ControlPath ~/.ssh/sockets/%r@%h-%p
    ControlPersist 600
    TCPKeepAlive no
    ServerAliveInterval 30

Note

A Port is no longer required for this connection as the default port 22 is acceptable. Replace the ONIDUSER with your ONID username. By default, ssh uses your local username for the connection, so if your local user matches your onid, you do not need to specify a username at all. You may need to specify a User for both the shell.hpc and hpc.cqls machines.

After you add those lines to your ~/.ssh/config file, you can connect to the Wildwood HPC cluster using the ssh hpc command. If you have your ssh keys set up, then you will not have to type a password, either.

Connecting to the CQLS Gitlab using ssh¶

If you use ssh to connect to the CQLS Gitlab, you will need to edit your ~/.ssh/config file:

~/.ssh/config

Host gitlab.cqls.oregonstate.edu
Port 732

Note

We previously used Port 822 for ssh connection to Gitlab. If you are experiencing issues, please check your ~/.ssh/config file and update it accordingly.