Overview

Landing pad systems function as the gateway to access CCI resources.

NOTE! The landing pad systems are not to be used for CPU/GPU intensive tasks

Compute intensive tasks running on landing pads may be stopped by CCI staff without warning. Please use sbatch or salloc to request compute resources.

If you require an interactive session for any reason, consider launching an interactive job through the scheduler requesting a graphical terminal instead:

salloc xterm -e 'ssh -X `srun hostname`'

Connecting to CCI

The following landing pads are available for two-factor SSH connections:

blp01.cci.rpi.edu
blp02.cci.rpi.edu
blp03.cci.rpi.edu
blp04.cci.rpi.edu

These hosts share a common SSH public key fingerprint:

3072 SHA256:+nft/TbzjyaAxzav/noyThJxclMNudxr8P5jILuyZ7M root@blp0X (RSA)
256 SHA256:NRy8oTlYAYPQh2Pem5N5U37kU+XHxFQCvGFd7xoip3E root@blp0X (ECDSA)
256 SHA256:dNAHyS4jd746ZJGShnc8GfLnLiG8wFOtybE9oZPK7yw root@blp0X (ED25519)

Data Movement

Use an SCP or Rsync client to transfer data to the landing pad systems.

Connections to external systems from the landing pads (or any other system) are not allowed, except pre-approved connections through the proxy. Submit a support ticket to apply for an exception.

Data transfers generally have to be initiated internally, whether transferring data to or from CCI.

TIP: All landing pads have a common file system shared across all clusters.

Connecting to Other Systems

To access compute resources for job submission or compilation, SSH from the landing pad to the appropriate front-end node, "FEN".

Further information on job submission and scheduling can be found here