This page includes a summary of differences to keep in mind when migrating jobs from other clusters to Ascend.
| Ascend (PER NODE) | Pitzer (PER NODE) | ||
|---|---|---|---|
| Regular compute node | n/a |
40 cores and 192GB of RAM 48 cores and 192GB of RAM | |
It is strongly suggested to consider the memory use to the available per-core memory when users request OSC resources for their jobs.
In October 2022, OSC retires the Data Direct Networks (DDN) GRIDScaler system deployed in 2016 and expands the IBM Elastic Storage System (ESS) for both Project and global Scratch services. This expands the total capacity of Project and Scratch storage at OSC to ~16 petabytes with better performance.
In December 2021 OSC updated its firewall to enhance security. As a result, SSH sessions are being closed more quickly than they used to be. It is very easy to modify your SSH options in the client you use to connect to OSC to keep your connection open.
In ~/.ssh/config (use the command touch ~/.ssh/config to create it if there is no exisitng one), you can set 3 options:
This document is obsoleted and kept as a reference to previous Owens programming environment. Please refer to here for the latest version.
As we migrate to Slurm from Torque/Moab, there will be necessary software environment changes.
Old MVAPICH2 including mvapich2/2.1, mvapich2/2.2 and its variants do not support Slurm very well due to its life span, so we will remove the following versions:
As a result, the following dependent software will not be available anymore.
OSC has entered an agreement with OSU College of Medicine (CoM) to provide dedicated compute services. Researchers from CoM will have access to Pitzer cluster, whose hardware is described below.
Pitzer node specifications for CoM dedicated compute are:
Slurm, which stands for Simple Linux Utility for Resource Management, is a widely used open-source HPC resource management and scheduling system that originated at Lawrence Livermore National Laboratory.
It is decided that OSC will be implementing Slurm for job scheduling and resource management, to replace the Torque resource manager and Moab scheduling system that it currently uses, over the course of 2020.
An ACL (access control list) is a list of permissions associated with a file or directory. These permissions allow you to restrict access to a certain file or directory by user or group.
OSC supports NFSv4 ACL on our home directory and POSIX ACL on our project and scratch file systems. Please see the how to use NFSv4 ACL for home directory ACL management and how to use POSIX ACL for managing ACLs in project and scratch file systems.
In March 2020, OSC expanded the existing project and scratch storage filesystems by 8.6 petabytes. Adding the existing storage capacity at OSC, this brings the total storage capacity of OSC to ~14 petabytes.