General Documentation
- Welcome FAQ
- Secure Shell SSH
- Available Software
- Installing Software
- Guidelines and Policies
- Glossary
- Grant Support
- Sharing Data
- Containers & Singularity
- UserGroup Presentations
- Jupyter Notebook Usage
LSF Primer
Lilac Cluster Guide
Juno Cluster Guide
Cloud Resources
Backup Policy on server/node local drives
File lists
Page History
...
Juno currently has 1072 CPUs. The login node is 'Juno', and runs CentOS 7 with GPFS as the main file system.
Nodes jx01-jx10 jx20, jv01-jv04, and jw02 are running CentOS 7 with GPFS, while node
**Node ju14 is running CentOS 6 without GPFS.
All juno Juno nodes have access to the solisi Solisi Isilon file systems. CentOS 7 nodes also have access to the "new" /juno GPFS storage.
Table of Contents |
---|
...
- We reserve ~12GB of RAM per host for the operating system and GPFS on Juno CentOS 7 hosts.
- On each jx## node (CentOS 7, GPFS installed), 240GB of RAM is available for LSF jobs.
- On each ju## node (CentOS 6, no GPFS), 250GB of RAM is available for LSF jobs.
- When specifying RAM for LSF jobs, specify GB of RAM per task (slot) on Juno (unlike luna, where RAM is specified per job).
- All jobs must have -W (maximum execution Walltime) specified on Juno. Please do not use -We on Juno.
- There is no /swap on CentOS 7 nodes. Memory usage is enforced by cgroups so jobs never swap. A job will be terminated if memory usage exceeds its LSF specification.
- To check jobs which are DONE or status EXIT, use "bhist -l JobID" or "bhist -n 0 -l JobID". bacct is also available. "bjobs -l JobID" only shows RUNNING and PEND jobs.
- There is no iounits resource on Juno.
- CMOPI SLA configured on Juno. The loan policies are: 100% resources for 90 mints jobs for not SLA users, and 75% resources for 240 mints jobs for not SLA users.
...