Owens Programming Environment (PBS)
This document is obsoleted and kept as a reference to previous Owens programming environment. Please refer to here for the latest version.
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.
checkgpu
is a command developed at OSC for use on OSC’s systems to report information regarding the usage of OSC’s GPU nodes. It reports various information on the usage and availability of the GPU nodes.
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.
OSCprojects is a command developed at OSC for use on OSC's systems and is used to view your logged in accounts project information.
OSCgetent is a command developed at OSC for use on OSC's systems and is similar to the standard getent command. It lets one view group information.
OSCusage is command developed at OSC for use on OSC's systems. It allows for a user to see information on their project's usage, including different users and their jobs.