Research Computing on the Great Lakes Cluster
2020-02-04 13:00 - 16:00 (America/Detroit) | Modern Languages Building (MLB), Room 2001A
OVERVIEW
This workshop will provide a brief overview of the components of the Great Lakes Cluster. The main body of the workshop will cover the resource manager and scheduler, creating submissions scripts to run jobs and the options available in them, and hands-on experience. By the end of the workshop, every participant should have created a submission script, submitted a job, tracked its progress, and collected its output. Participants will have several working examples from which to build their own submissions scripts in their own home directories.
PRE-REQUISITES
This course assumes familiarity with the Linux command line as might be got from the CSCAR/ARC-TS workshop Introduction to the Linux Command Line. In particular, participants should understand how files and folders work, be able to create text files using the nano editor, be able to create and remove files and folders, and understand what input and output redirection are and how to use them.
INSTRUCTORS
Dr. Charles J Antonelli
Research Computing Services
LSA Technology Services
Charles is a High Performance Computing Consultant in the Research Computing Services group of LSA TS at the University of Michigan, where he is responsible for high performance computing support and education, and was an Advocate to the Departments of History and Communications. Prior to this, he built a parallel data ingestion component of a novel earth science data assimilation system, a secure packet vault, and worked on the No. 5 ESS Switch at Bell Labs in the 80s. He has taught courses in operating systems, distributed file systems, C++ programming, security, and database application design.
John Thiels
Research Computing Services
LSA Technology Services
Mark Champe
Research Computing Services
LSA Technology Services
MATERIALS
Lecture notes
Great Lakes HPC cluster
COURSE PREPARATION
In order to participate successfully in the workshop exercises, you must have a user login, a Slurm account, and be enrolled in Duo. The user login allows you to log in to the cluster, create, compile, and test applications, and prepare jobs for submission. The Slurm account allows you to submit those jobs, executing the applications in parallel on the cluster and charging their resource use to the account. Duo is required to help authenticate you to the cluster.
USER LOGIN
If you don’t already have a Great Lakes user login, please visit the application page.
Please note that obtaining a user account requires human processing, so be sure to do this at least two business days before class begins.
SLURM ACCOUNT
We create a Slurm account for the workshop so you can run jobs on the cluster during the workshop and for one day after for those who would like additional practice. The workshop job account is quite limited and is intended only to run examples to help you cement the details of job submission and management. If you already have an existing Slurm account, you can use that, though if there are any issues with that account, we will ask you to use the workshop account.
DUO AUTHENTICATION
Duo two-factor authentication is required to log in to the cluster. When logging in, you will need to type your UMICH (AKA Level 1) password as well as authenticate through Duo in order to access Great Lakes.
If you need to enroll in Duo, follow the instructions at Enroll a Smartphone or Tablet in Duo.
Please enroll in Duo before you come to class.
LAPTOP PREPARATION
You do not need to bring your own laptop to class. The classroom will provide Windows or Mac computers, which require your uniqname and UMICH (AKA Level 1) password to login, and that have all necessary software pre-loaded.
If you want to use a laptop for the course, you are welcome to do so: please see our web page on Preparing your laptop to use Flux (those instructions apply to Great Lakes as well). However, if there are problems connecting your laptop, you will be asked to switch to the provided computer for the class. We cannot stop to debug connection issues with personal or departmental laptops during the class.
