-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added more details in access and all new details on obtain (#99)
- Loading branch information
Showing
8 changed files
with
331 additions
and
111 deletions.
There are no files selected for viewing
18 changes: 18 additions & 0 deletions
18
docs/services/on-prem/Pantarhei/RunningJobs/computenode.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
sidebar_position: 1 | ||
title: "Accessing the Compute Nodes" | ||
description: "" | ||
tags: | ||
- HPC | ||
- On-Premises | ||
- Slurm | ||
- Pantarhei | ||
--- | ||
|
||
Pantarhei employs the [Slurm Workload Manager](https://slurm.schedmd.com/documentation.html) for the purpose of job scheduling and management. Utilizing Slurm, a user initiates a request for resources and submits a job to a designated queue. Subsequently, the system undertakes the task of extracting jobs from the queues, assigning the requisite compute nodes, and executing the submitted tasks. Although users typically access the Slurm job scheduler by SSH-ing to a Pantarhei login node, it is imperative to emphasize that the recommended practice entails utilizing Slurm to submit work as a job, as opposed to executing computationally intensive tasks directly on a login node. Given that all users share the login nodes, running anything beyond minimal test jobs can adversely affect the collective ability of users to effectively utilize Pantarhei resources. | ||
|
||
Pantarhei's framework is tailored to accommodate the moderate-scale computational and data requirements of the majority of CIROH users. Users with allocations possess the capability to submit tasks to a diverse array of queues, each featuring distinct job size and walltime constraints. Dedicated sets of queues are allocated for CPU, GPU, and FPGA nodes, with typically shorter walltime and smaller job size limits translating to expedited turnaround times. Several additional considerations regarding Pantarhei queues merit attention: | ||
|
||
1. Pantarhei facilitates shared jobs, whereby multiple tasks can be executed on a single node. This approach enhances job throughput, maximizes overall system utilization, and fosters increased user accessibility to Pantarhei resources. | ||
2. Pantarhei accommodates long-running jobs, with run times extendable up to seven days for tasks utilizing up to 6 full nodes. | ||
3. The maximum permissible job size on Pantarhei is 240 cores. For tasks exceeding this threshold, users are advised to initiate a consulting ticket to engage in further discussion with Pantarhei support personnel. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
--- | ||
sidebar_position: 4 | ||
title: "Running Jobs" | ||
tags: | ||
- HPC | ||
- On-Premises | ||
- Slurm | ||
- Pantarhei | ||
--- | ||
|
||
Proficient users acquainted with the Linux command line interface have the option to utilize standard job submission utilities for the purpose of managing and executing tasks on the computational nodes within the Pantarhei system. | ||
|
||
------------------------------------------------ | ||
|
||
### Navigational Resources | ||
|
||
import DocCardList from '@theme/DocCardList'; | ||
|
||
<DocCardList /> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
sidebar_position: 2 | ||
title: "Obtaining an Account" | ||
description: "Obtain an account on Pantarhei" | ||
tags: | ||
- HPC | ||
- On-Premises | ||
- Account | ||
- Pantarhei | ||
--- | ||
|
||
Pantarhei cluster is accessible to the research community of the Cooperative Institute for Research to Operations in Hydrology (CIROH). | ||
|
||
### General overview | ||
|
||
To obtain an account, users will need to follow these step: | ||
|
||
1. Submit [On-premises Infrastructure Request Form](/docs/services/access#on-premises) and describe full project information and resouce requirements. | ||
|
||
::::::warning | ||
This GitHub issue must be submitted by Principal Investigator (PI) of the project. | ||
|
||
:::info[Hint] | ||
In the GitHub issue PI should mention following details: | ||
1. PI's __Full Name__ | ||
2. PI's __Affiliated Institute__ | ||
3. PI's __Affiliated Email Address__ | ||
4. List of students who will need access, also please provide following details of each student | ||
* __Full Name__ of student | ||
* __GitHub User Name__ of student | ||
* __Affiliated Email Address__ of student | ||
::: | ||
:::::: | ||
2. Submit On-premise Access Request form in [CIROH Service Request](https://forms.office.com/r/CQucJqqADx). | ||
::::::tip | ||
The administration of the Pantarhei cluster falls under the purview of the CIROH IT Computing group at the University of Alabama (UA). Consequently, individuals lacking UA credentials (*MyBama ID*, *VPN User Name*, and *CWID*) are obliged to complete the __`VPN Access Request`__ form, followed by the __`On-premise Access Request`__ form within [CIROH Service Request](https://forms.office.com/r/CQucJqqADx). | ||
|
||
:::warning[Account Creation] | ||
Creation of accounts on the Pantarhei system necessitates submission of individual forms by each respective user. | ||
|
||
For instance, a Principal Investigator (PI) submits a GitHub issue pertaining to a project, and three students require access to the Pantarhei system for project-related work, three separate account creation forms must be duly submitted during this process. | ||
::: | ||
:::::: |
Oops, something went wrong.