Intel® DevCloud for oneAPI

Overview Get Started Documentation Forum external link

If you are running Linux or a macOS operating system you can access the cluster using the native Secure Shell (SSH) client, you will need to set up SSH tunneling as described below.

Option 1: Automated Configuration

The easiest method to set up SSH connection to is by downloading and running an automated installer. The installer will add SSH configuration entries to ~/.ssh/config and create a private SSH key file inside ~/.ssh. This method works best if you have only one account.

  1. Download and save the automatic installer script customized for your account:
  2. Execute this script in a terminal (you may need to adjust the command according to your download location and the downloaded file name):
    bash ~/Downloads/setup-devcloud-access-<user>.txt
  3. Clean up for security:
    rm ~/Downloads/setup-devcloud-access-<user>.txt

Option 2: Manual Configuration

Alternatively, if you do not want a script to modify your SSH configuration, you can proceed with manual installation instructions below.

Direct SSH Connection

  1. Download and save the SSH access key for Linux/macOS to the folder ~/Downloads/ on your computer
    * Sign In to see the download link.
  2. Create the directory ~/.ssh, unless it already exists and move the private SSH key into permanent storage in ~/.ssh:
    mkdir -p ~/.ssh
    mv ~/Downloads/devcloud-access-key-<user>.txt ~/.ssh/
    If you saved your key in a location other than ~/Downloads/, insert the correct path.
    * Sign In to see the value of <user> for your account.
  3. Add the following lines to file ~/.ssh/config (if you do not have this file, simply create one):
    Host devcloud
    User  <user>
    IdentityFile ~/.ssh/devcloud-access-key-<user>.txt
    ProxyCommand ssh -T -i ~/.ssh/devcloud-access-key-<user>.txt guest@ssh.devcloud.intel.com
    Note: if you have multiple accounts on the Intel DevCloud, you can change the hostname devcloud to any other identifier to differentiate between your accounts. This is the hostname that you will use in the ssh and scp commands.
    * Sign In to see the value of <user> for your account.
  4. Set the correct restrictive permissions on it and on the SSH client config file. To do this, run the following commands in a terminal:
    chmod 600 ~/.ssh/devcloud-access-key-<user>.txt
    chmod 600 ~/.ssh/config
    * Sign In to see the value of <user> for your account.

Direct SSH Connection

The following SSH settings are required for Visual Studio Code* remote access.

# DevCloud VSCode config
Host devcloud-vscode
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
Hostname localhost
User  <user>
Port 5022
IdentityFile ~/.ssh/devcloud-access-key-<user>.txt

# SSH Tunnel config
Host *.aidevcloud
User  <user>
IdentityFile ~/.ssh/devcloud-access-key-<user>.txt
ProxyCommand ssh -T devcloud nc %h %p
LocalForward 5022 localhost:22
LocalForward 5901 localhost:5901
* Sign In to see the value of <user> for your account.

If you Are Behind an SSH Proxy

In the interest of security, some business networks require that all outgoing connections are established via a corporate proxy. If you followed the instructions above but are getting the error "Connection timed out", you are likely on such a business network. To comply with the security rules of your company, modify ~/.ssh/config as below:

Host devcloud
User  <user>
Port 4022
IdentityFile ~/.ssh/devcloud-access-key-<user>.txt
ProxyCommand ssh -T devcloud-via-proxy

Host devcloud-via-proxy
User guest
Hostname ssh.devcloud.intel.com
IdentityFile ~/.ssh/devcloud-access-key-<user>.txt
LocalForward 4022 c009:22
ProxyCommand nc -x <proxy_name>:<port> %h %p

Here, <proxy_name> and <port> are, respectively, the hostname and port of the corporate proxy. It is usually provided to you by your IT department.

Connection

After the preparation steps above, you should be able to log in to your login node in the Intel® DevCloud without a password.

ssh devcloud

Upon the first login, you will be asked to add the host to the list of known hosts. Answer "yes":

The authenticity of host 'devcloud' (&lt;no hostip for proxy command&gt;)' can't be established.
ECDSA key fingerprint is SHA256:...
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'devcloud' (ECDSA) to the list of known hosts.
# We are in!
logout
Connection to login-2 closed.

Next time you log in, you will only need to type ssh devcloud to log in:

ssh devcloud
Last login: Tue Jan  3 11:54:11 2017 from 10.5.0.7

Transferring Files

Once your connection is set up, you can copy local files to your login node like this:

scp /path/to/local/file devcloud:/path/to/remote/directory/

And you can copy files from your login node back to your home computer like this:

scp devcloud:/path/to/remote/file /path/to/local/directory/