The CATAMOUNT cluster is part of the LBNL Supercluster and shares the same Supercluster infrastructure. This includes the system management software, software module farm, scheduler, storage, and backend network management.
Please send emails to email@example.com for account requests on the CATAMOUNT cluster.
Login and Data Transfer:
- Login server: lrc-login.lbl.gov
- DATA transfer server: lrc-xfer.lbl.gov
- Globus Online endpoint: lbnl#lrc
Each compute node has dual-socket octa-core Intel Xeon E5-2670 (Sandy Bridge) @ 2.60 GHz processors (16 cores in total), 64 GB of physical memory. Compute nodes are connected with each other through multiple high performance Mellanox 56 Gbps FDR Infiniband edge switches then back to a backbone Mellanox SX6518 director switch.
|INTEL XEON E5-2670
Storage and Backup:
CATAMOUNT cluster users are entitled to access the following storage systems so please get familiar with them.
|HOME directory for permanent data
|GROUP directory for software and
data sharing with backup
|GROUP directory for data sharing
|SCRATCH directory with Lustre high
performance parallel file system
NOTE: HOME, GROUP, and GROUP-SW directories are located on a highly reliable enterprise level BlueArc storage device. Since this appliance also provides storage for many other mission critical file systems, and it is not designed for high performance applications, running large I/O dependent jobs on these file systems could greatly degrade the performance of all the file systems that are hosted on this device and affect hundreds of users, thus this behavior is explicitly prohibited. HPCS reserves the right to kill these jobs without notification once discovered. Jobs that have I/O requirement should use the SCRATCH file system which is designed specifically for that purpose.
CATAMOUNT cluster uses SLURM as the scheduler to manage jobs on the cluster. To use the CATAMOUNT resource the partition “catamount” must be used (“–partition=catamount”) along with account “catamount” (“–account=catamount”). One of the QoSs from the following table should be used as well (e.g., “–qos=cm_short”). A standard fair-share policy with a decay half life value of 14 days (2 weeks) is enforced.